Contributions
Re: Test execution results by coverage - limit?
Hi Andy Yes, I have tried last execution, custom query, etc - but while I can limit what tests are hit, once a test is found, it always shows me ALL the places it has been linked to - so I see issues from previous releases. I think that is just the nature of this report.1KViews0likes3CommentsTest execution results by coverage - limit?
I use modular tests that can be run for regression on mulitple releases. When I run the Test Execution Results by Coverage report for the latest release Test Plan - I get hits from all the previous releases where the test was also ran. Is there a way to limit the hits to something that would only show this release? I know it is accurate to show ALL the coverage, but I don't need to see the coverage for previous releases. The test cases are in multiple different directories (different releases). The only method I can see is to clone the test case and assign it to the test cycle for the current release (so it would be a new test with no history). Is there another report that will show the list of test case individual progress for each requirement/userstory/issue only for the current release?Solved1.1KViews0likes5CommentsRe: Best Practice - Enviroments coverage in Reports
Thanks Andy We have multiple test cases to run, but looking at just one: Currently, we are running a test case with OS/http/Browser settings (from the Enviroment pick list) for each permutation. We pick the environment each time we run the test case. The tester could pick the wrong one, but they have to pick something. So we would run the test case and pick Windows2019-http-Edge as environment. Then we would run the test case and pickWindows2019-http-Chrome as the environment. Then we would pick Windows2019-HTTPS-Edge for the next test run, etc. This allows me to see how many, or when the test case was run against all the envirionment combinations of OS/http/Browser. This requires that all the permutations are listed in the environment pick list - and if another option needs to be covered - like another OS, another Browser, certification type, etc - then the list grows dramatically. This does not seem to be the best approach... In this case, I am interested in knowing that the test case has been run against all OS's, both http and HTTPS, and both Edge and Chrome - not in the number of runs, or time estimates. One tester would usually run thru all the tests for one environment group (OS/http/browser) and then switch to another run for different environment. I could create a test cycle, but the cycle does not let us pick an environment, so I would name the cycle to show theOS/http/Browser combo and include the full set of test cases. I don't know how that would work with reports having to track by test cycle names? For this, I would need a test cycle for each permutation (similar to the enviroment pick list). I can have the execution options to fill in for OS/http/Browser on the test case, but that is more work for the tester to keep up with - and may not be needed if the test case name covers it. Maybe there is a better approach that I have not realized yet. 🙂1.1KViews0likes2Comments