Idea: Extend test detection conventions

tipi-build / community-support

Support repo for tipi.build

0 stars 0 forks source link

Open arBmind opened 2 years ago

arBmind commented 2 years ago

I like to keep my tests next to the source files. I know others do this too.

To distinguish tests from regular code I would recommend the following:

file name patterns: *.test.cpp, test_*.cpp, test-*.cpp, *_test.cpp, *-test.cpp
Some alternative keys: test, tst, check, unittest
Plural versions of the keys: tests, checks, unittests

What do you think?

daminetreg commented 1 year ago

Hi @arBmind it was a pleasure talking to you about all the build systems and learning aobut Qbs the other day.

Please apologies for the longer response time than usual.

Totally agree and we have it as PR implemented but missing some polishing for release, we had a similar request very early on.

Also we are about to release the plugin system that will allow devs to code their generic conventions in tipi easily.

We will keep you informed here as we roll out the supports.