What steps will reproduce the problem?
1. create a new build and include copy tester assignments
2. open new build to continue test run (execute tests)
3.
What is the expected output? What do you see instead?
In order to slipstream builds during quick development cycles, the ability to
have the new build only show and copy forward tests that are NOT run OR have
the previous build results copied to the new build so testers dont have to
rerun all tests in the new build would be helpful. Currently every new build
resets all the tests and only shows that it was passed in a previous build. We
would like to see those tests already run and set so that the overall testing
progress can continue on a new build instead of resetting all the tests in the
new build to not run.
What version of the product are you using? On what operating system?
testlink 1.9.6
windows 7
IE 9/10 Chrome
Please provide any additional information below.
Original issue reported on code.google.com by mike.wel...@gmail.com on 17 Apr 2013 at 3:30
Original issue reported on code.google.com by
mike.wel...@gmail.com
on 17 Apr 2013 at 3:30