No, I mean links between test case 1 and test case 2 or link between test case 1 and test suit 1.
Why I need it:
For example I have a mobile app and there is the standard Top navigation bar. I used the following structure - one screen = one test suit. Now I should make the same test cases for the standard Top nav bar in each screen. To avoid that I use the following: I create one test suite for Top bar and use only links to this suite from other test suites. So If my nav bar changes I need change only one test suite.
Current system does not allow work properly with such structure. I should create something like table of contents in such test suite (for Nav bar in current example) to track all dependencies. And I can not summarize total estimation for the whole run, because I use only one test suite as a link in many other test suites.
My mobile app has 3 screens. Each screen has standard top nav bar.
I create three test suites - S1, S2, S3. I create one additional test suite for Top nav bar (S4) and use links to this suit in S1, S2 and S3. I know that S1 takes 5 minutes to run, S2 takes 5 minutes to run, S3 takes 5 minutes to run and S4 takes 10 minutes to run.
I can manually count how much time do I need to run tests for each screen: (5(S1) + 10 (S4)) + (5(S2) + 10 (S4)) + (5(S3) + 10 (S4)) = 45 minutes. BUT! now current system “does not know my needs” and say that whole run takes only 5 + 5 + 5 + 10 = 25 minutes. Maybe there are some workaround?
So It would be great:
- Add linking between cases and suites and ability to see all “related” cases / suites.
- Maybe add some new type of suite / case, something like “class” and use something like instances of this class where needed.