You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2022. It is now read-only.
I was wondering how the team might be thinking about approaching the testing of modules (and I guess themes, too).
I poked and played around with testing contentTypes and so far the awkwardness of trying to load modules in the mocha tests has gotten in my way.
I know that for now, lib.core.module is just a stub -- and I suspect the goals of that file would be to test the Module.js file -- not individual modules.
So I guess my question is two-fold -- what to test in Module.js, and how to test modules (be they core or otherwise).
I realize this is a really open ended question, which is in fact why I'm asking it. I'm hoping to start a discussion about testability in general and what could be done to move the ball forward!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was wondering how the team might be thinking about approaching the testing of modules (and I guess themes, too).
I poked and played around with testing contentTypes and so far the awkwardness of trying to load modules in the mocha tests has gotten in my way.
I know that for now, lib.core.module is just a stub -- and I suspect the goals of that file would be to test the Module.js file -- not individual modules.
So I guess my question is two-fold -- what to test in Module.js, and how to test modules (be they core or otherwise).
I realize this is a really open ended question, which is in fact why I'm asking it. I'm hoping to start a discussion about testability in general and what could be done to move the ball forward!
The text was updated successfully, but these errors were encountered: