Red Hat Bugzilla – Bug 841843
TCMS webUI does not propagate test run global properties to caseruns properly (at least Build property)
Last modified: 2016-06-23 00:21:23 EDT
Description of problem:
TCMS webUI does not propagate test run global properties to caseruns properly.
When you create test run containing at least one caserun selected global test-run properties are copied into case-runs (for instance Build).
In case you decide to pick another build for current test run (by editing test run) no caserun is updated with that change.
There might be discussion why to do that (in our case we wanted to differentiate between parts of the product - for TCMS reporting purpose where you cannot select one by one test runs for your custom report) but fact is that single test-run has to have common build, so ability to enter state when
test-run build ID does not match with corresponding caseruns builds is evidently WRONG.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Let's have test-plan with at least 2 test cass
2. Create run R (using build B1)
3. Change R's build to B2
4. Check R's caseruns build properties
Test run and corresponding case run builds may not match.
Test run and corresponding case run builds have to match.
This bug is related to db schema, so will fix it in TCMS4.0