I have a few UnitTests across different libraries that perform some long running testing tasks. Let's assume that these test should run only in a "Smoke Test" and "All Tests" szenarios. Second, I have UnitTests across these libraries that should run after at the "Post Build" step of the library itself (or of the complete application). These tests should also run within the "All Tests". But how do I best group the UnitTests to be able to run the same tests within different szenarios?
I know I can add the same test into different registries and I can add registries into each other to perform some hierarchy grouping. But there are at least two basic solutions:
1.) I could build the hierarchy like the following:
Hi,
I have a few UnitTests across different libraries that perform some long running testing tasks. Let's assume that these test should run only in a "Smoke Test" and "All Tests" szenarios. Second, I have UnitTests across these libraries that should run after at the "Post Build" step of the library itself (or of the complete application). These tests should also run within the "All Tests". But how do I best group the UnitTests to be able to run the same tests within different szenarios?
I know I can add the same test into different registries and I can add registries into each other to perform some hierarchy grouping. But there are at least two basic solutions:
1.) I could build the hierarchy like the following:
\Build Tests\LibraryA
\Build Tests\LibraryB
\Build Tests\LibraryC
\Smoke Tests\LibraryA
\Smoke Tests\LibraryB
\Smoke Tests\LibraryC
In this situation I can run all "Smoke Tests" of all Libraries at once, but not all LibrarayA tests.
I expect also, that the Libray names (e.g. LibraryA) must be unique since otherwise the two named registries LibrarayA are identical
2.) I could order the tests like
\LibraryA\Smoke Tests
\LibraryA\Build Tests
\LibraryB\Smoke Tests
\LibraryB\Build Tests
Now I have the opposite problem. I can run all Library tests, but not all Smoke Tests at once.
If I even want to further divide in modules things get even more complicated.
Does anybody have an advice how to best choose the grouping of UnitTests?
Thanks in advance
Dirk