I would call it "CI check" not a test - as tests should IMO be related to the application logic only, not all the supporting infrastructure. But the idea is not bad at all.
Makes me think about more checks like that. For example, if you keep docs in separate files than the code, you can check if when the files are updated with a lot of added code recently, did the doc files changes as well.
I agree, that this test/check is a bit different. However, technically, where would that check be "implemented"? Still in the same repo? Would it run also locally on dev machines?
I'd opt for the same repo and run on dev machines.
Good question. I'm used to keep these kind of checks in the repo, but separated from the app (for example in a .ci directory in repo root). I rather don't expect them to be regularily run on dev machines, unless someone needs to debug why the check is not working as expected. This is probably why it's easy for me to draw the line between "tests" and "checks".
I would call it "CI check" not a test - as tests should IMO be related to the application logic only, not all the supporting infrastructure. But the idea is not bad at all.
Makes me think about more checks like that. For example, if you keep docs in separate files than the code, you can check if when the files are updated with a lot of added code recently, did the doc files changes as well.
An interesting perspective with the CI check.
I agree, that this test/check is a bit different. However, technically, where would that check be "implemented"? Still in the same repo? Would it run also locally on dev machines?
I'd opt for the same repo and run on dev machines.
Good question. I'm used to keep these kind of checks in the repo, but separated from the app (for example in a
.cidirectory in repo root). I rather don't expect them to be regularily run on dev machines, unless someone needs to debug why the check is not working as expected. This is probably why it's easy for me to draw the line between "tests" and "checks".This is an interesting distinction - to keep some checks/tests in .ci.
I usually prefer to have everything run on local machines. Maybe the .ci concept doesn't discourage this.
Thanks for this idea, it's new for me.