Solved
how to create and use test library
hello, we are testing out Zephyr Scale in the trial period, specifically testing out how test cases can be stored in a library and reused for across projects. But we can't figure out the way to reus...
Forum Discussion
MisterB
Champion Level 3
Champion Level 3Hi,
What you're trying to achieve is possible. For example, in your project(s), create a new Test Cycle, entering basic info in the Details tab, then go to the Test Cases tab (1 over to the right), click on the Add Test Cases button, in the top left-hand corner, navigate to your project (the library will change) and then go to the folder and start selecting the test cases you want to add - clicking Close and then Save to save your changes.
And points 1 and 2 are possible. In the test case, it's possible to see the execution history in the Execution tab, showing which test cycles in which it was executed.
Does that help?
Andy
hi， thanks for your kindly reply.
but I wonder that if "navigate to your project (the library will change) " means there is no common library that contains different projects test cases. or we call it a baselined summarized test cases with all the product features now?
- MisterB
Hi,
Hopefully I'm understanding what it is you're aiming to achieve. I'll map it out below and how it's done. Let's say we have 3 projects: a project called Library that contains all baseline test cases, and other projects called Execution1 and Execution2 that will use subsets of the test cases from the Library. You can do this as follows:
Project Library
- has a folder structure in the Tests section (where test cases are stored)
- let's say you create a folder structure like this:
All Products
Product A
Test case 1
Test case 2
Test case 3
Product B
Test case 4
Test case 5
Test case 6
Product C
Test case 7
Test case 8
Test case 9
Now, you navigate to Project Execution1. And create a Cycle called Product A Test1. In there, you follow my previous advice and navigate to the Library project to find and add the selection of tests that you want to be executed. And you can repeat this process in another projects as needed. I would say that to make this easier for you, it's important to get the Library project in a very good structure.
When it comes to seeing the results of, say, Test case 1, you can click on that test case anywhere it has been executed, and using the traceability tab, see at glance the full execution history across multiple projects.
Hope that helps but if you need a bit more help let me know.
Best, Andy