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
I'd love to have a checkbox (in the GUI) called "Debug mode (Stop on first error and skip successful tests on hot-reload)".
When I check it and run my tests, it should stop at the first failing test. (stating clearly which test was causing the error)
So I can go ahead and fix it. Once I save my file, it should notice it (as usual), but instead of running every test again from the start it should start from the failing test. If it's running green, continue... until the very last test.
If all tests after the fixed test are green, continue with the ones above (becaue they could theoretically be broken now due to the latest changes).
Why is this needed?
When I change code and have some failing tests I usually start the according test file, let it run completely, look at the first failing problem, fix this, let everything run again... and if it isn't easily fixed I start adding ".only" to the failing request until it is fixed and then remove it and let everything run again... which results in running all the tests above the fixed one over and over again, even though I don't really want to test them again.
And I am to lazy to add (and later remove) ".skip" on such tests.
This checkbox would make my life a lot easier and would be a charm fixing tests in the future. :)
Other
No response
The text was updated successfully, but these errors were encountered:
What would you like?
I'd love to have a checkbox (in the GUI) called "Debug mode (Stop on first error and skip successful tests on hot-reload)".
When I check it and run my tests, it should stop at the first failing test. (stating clearly which test was causing the error)
So I can go ahead and fix it. Once I save my file, it should notice it (as usual), but instead of running every test again from the start it should start from the failing test. If it's running green, continue... until the very last test.
If all tests after the fixed test are green, continue with the ones above (becaue they could theoretically be broken now due to the latest changes).
Why is this needed?
When I change code and have some failing tests I usually start the according test file, let it run completely, look at the first failing problem, fix this, let everything run again... and if it isn't easily fixed I start adding ".only" to the failing request until it is fixed and then remove it and let everything run again... which results in running all the tests above the fixed one over and over again, even though I don't really want to test them again.
And I am to lazy to add (and later remove) ".skip" on such tests.
This checkbox would make my life a lot easier and would be a charm fixing tests in the future. :)
Other
No response
The text was updated successfully, but these errors were encountered: