Big project for multiple devices
We are working on a big integration project which has to implement a test case management strategy for multiple devices . What would be your advice to keep track of the results, in a single project, for the tests results on every device? Until now, we had a single run and if a test fails on a device, we can see only this result and not the results for running on other devices which have the status as passed, This can be a little confusing if you have, for example, 2 devices on which a test have passed and 3 device on which the tests have failed. Since the results are in the same file, we get the final result which is FAILED but we cannot see the devices.
As a second note, how do you recommend to keep track of new added tests in a project? We write a test for device X from project release_X, but we would want this test also in the others projects. We cannot do this automatically, or we do not know how to do it. We want to keep the tests synchronized between all the SILK projects. The requirements will change for each project, but at least we will have a large tests database to see what was tested on every project for a specific requirement.
Q: What would be your advice to keep track of the results, in a single project, for the tests results on every device?
A: Configuration Testing would be some approach. You can do that by creating a Configuration Suite and have each device represented by one Configuration.
You can then use the Document View in Execution Planning to see how the tests are doing for each device (= Configuration). Or on requirements side you would see it when you enable the "Execution Context" on the Assigned Tests tab.
Q: How do you recommend to keep track of new added tests in a project?
A: Since Silk Central 18.5 you can configure a project to be a "Sharing" project and you can configure other projects to be "Consuming" projects. Look for "Shared Tests" in the Documentation.
This allows you to have one set of tests that is then distributed across other projects. Any changes in the sharing project will be "offered" to the consuming projects - you can accept them or skip them.
You can also push changes from the consuming project to the sharing project. to make them available to other projects.
You can also add tests from the consuming to the sharing project to make them available to other projects.
If requirements are the same in the sharing and the consuming project it is possible to replicate the assignment in the consuming project when adding tests.
Thank you for your answer. For the second question, is it possible that a new test added in the "Consuming" project to be automatically added in the "Sharing" one? As I can see, the "accept changes" functionality" only works for already existing tests that you are versioning.
Thanks a lot,