Second time this week where I find out my unit tests aren't being run. Does anyone have any tips on how to safeguard against such issues? How do I set up an automated test to check my automated test setup is right?
-
-
Replying to @dwijnand
Write a unit test which always passes, but which—as a side-effect—deletes a line which would fail the build in a later, obvious step.
2 replies 0 retweets 3 likes -
Replying to @propensive
So assuming the setup step passed (writing the line) then I can assert the unit test ran because my smoke test deleted the line. Interesting, thanks.
1 reply 0 retweets 2 likes
Replying to @dwijnand
I'm not sure there would need to be any setup: The build would be hardwired to fail by default, e.g. with `exit 1` somewhere close to the end, e.g. `tar cf final.tar && exit 1`. There would be a unit test which would remove the `&& exit 1`. Certainly not infallible, of course.
5:14 AM - 5 Oct 2019
0 replies
0 retweets
3 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.