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 reuse the test cases in the library(the library is a specific jira project that contains all the approved test cases, is that right?)，could you kindly show us how to reuse test cases in different projects.
1. we would establish and maintain a test library with all the products modules, all the test cases in other projects generated from the library.
2. In different projects, the testers could call(reuse) the test cases in the library and execute the test in the project, and then the library would record all the reuse records of this test case
is that possible for us?
Solved! Go to Solution.
Thanks a lot. We will have a try for more functions and apply it to our work, thanks again.
We have separate src and tests directories at the top level in our libraries. Our applications are very thin wrappers around library projects, so they don't need any tests. We also have a FlexUnit application project, to run the tests from FlexBuilder.
We use maven for our main build system, and the Sonatype Flex plugin runs all our unit tests during the build, even on our linux-based Continuum server. Maven defaults to looking for tests in a 'tests' directory, which was a good justification for picking that location.
when we actually apply it to our work, we found that we want to modify or customize some of the default configurations, such as priorities from the default "HIGH" "MIDDLE" "LOW" to "P0/P1/P2"; and also the "component", we could not find a way to add any options to this component , could you kindly guide us to customize these detail informations?
There's no real good way to have a master test run copied across multiple projects within Zephyr Scale. I wrote an app to copy test runs using the API. Can't share the source, but here's an idea of what it looks like.
In my system, it create a Jira issue. The Jira issue has a link to the test run in the Description field. The issue is assigned to someone with a duedate and we use that for tracking purposes.
Using this method we have one, protected, master set of tests in a master test run, that gets copied to individual projects. The individual projects can have additional tests added and are filtered based on the project requirements.