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?
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.
-
-
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.
-
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.
End of conversation
New conversation -
-
-
Or just write code that never fails. Or else.https://github.com/munificent/vigil …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.