You write tests for functionality before you write the functionality.

You code the functionality so the tests pass.

Then, and only then, the test becomes a regression test and is enabled in your CI automation.

If the test ever breaks again the merge is blocked.

I disagree. Merging should be blocked on any failing test. No commit should be merged to master with a failing test. If you want to write tests first, then do that on a feature branch, but squash the commits properly before merging. Or add them as disabled first and enable after the feature is implemented. The enabled tests must always pass on every commit on master.

[–] wewbull@feddit.uk -1 points 6 days ago (1 children)

So I can never commit a test without also implementing the functionality?

That's madness.

[–] balsoft@lemmy.ml 2 points 6 days ago

You can, but not on master.