Hi Tobias -
As a bit of context, I initially created 1 project in TestRail, then 2 test suites:
- Major product A
- Major product B
Engineering (our developers) consider the “project” to be the overall version of the code base (XXXXX 4.1) - so I made that our “Project”.
During test run creation, I found that the section/sub-section are not retained when you drill down into a test case itself (when you “view” a test case within a test run).
So I asked… “Well wait… what if a test run has multiple instances of test case ‘Settings: Ensure settings save when edited’ ?”
Right now, it becomes difficult to tell where each test case lives in a suite, because section/sub-section are not displayed. So if we have one section called “Triggers”, then a sub-section named under “Triggers” named after each trigger, then identically named test cases within those sun-sections… none of that is displayed if those are added in a test run (if you click into the case itself to “run” the case).
But you do see the project/test suite it is in.
So I figured to create multiple Projects for each major component of our product:
- Project A = Triggers; suite 1 “name_of_trigger”, suite 2 “another_trigger”
- Project B = Product B; suite 1 “name_of_component” etc.
I still think adding test cases (from at least multiple suites) to a test run (if not projects). This is absolutely something that competing products do (see Contour and Testuff).
And really, I suppose printing the section/sub-section to the breadcrumb while viewing a test case is the root cause here