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
This is just a suggestion... in some coding work-flows, one writes the tests first, expecting them to fail. Then as you begin the implementation, fewer and fewer tests fail until they all pass and you're done.
The watcher only watches the spec folders right now. This means it isn't very useful for the above scenario because it only re-runs the tests when the spec changes, not when the code changes.
Would it be possible to add other source directories (recursively) to the watcher that trigger the tests?
Thanks
The text was updated successfully, but these errors were encountered:
This is just a suggestion... in some coding work-flows, one writes the tests first, expecting them to fail. Then as you begin the implementation, fewer and fewer tests fail until they all pass and you're done.
The watcher only watches the spec folders right now. This means it isn't very useful for the above scenario because it only re-runs the tests when the spec changes, not when the code changes.
Would it be possible to add other source directories (recursively) to the watcher that trigger the tests?
Thanks
The text was updated successfully, but these errors were encountered: