| Summary: | Bugs associated with test case get lost when cloning test plan | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Other] TCMS | Reporter: | Jiri Koten <jkoten> | ||||
| Component: | Application | Assignee: | Yuguang Wang <yuwang> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | tools-bugs <tools-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.6 | CC: | ctang, freznice, jianchen, junzhang, llim, nli, vchen, yawli | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-05-28 08:11:14 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Jiri Koten
2011-10-21 11:37:21 UTC
(In reply to comment #0) > Description of problem: > When cloning test plan, bugs associated with test cases get lost. > > We are currently cloning test plans for every new product minor release and I > think that having bugs associated with test cases is vital information in > regards to regression testing and should be retained through all test plans for > our product minor releases. > > Version-Release number of selected component (if applicable): > Nitrate 3.6.0 For minor release, TCMS suggest you clone the test run ,but not clone the test plan. The bug information about test case could be reserved in cloned test run. recommended solution in TCMS is : use test plan for organize test cases of different products or different versions of product. use test run to execute test case in different release/build. Hope this can help. (In reply to comment #1) > For minor release, TCMS suggest you clone the test run ,but not clone the test > plan. > The bug information about test case could be reserved in cloned test run. > > recommended solution in TCMS is : > use test plan for organize test cases of different products or different > versions of product. > use test run to execute test case in different release/build. > > Hope this can help. That was just an example of use case. Simply put, I don't want to loose the bug associated with test case when I clone it. TCMS should be flexible to suite our workflow, not the other way around. (In reply to comment #2) > (In reply to comment #1) > > For minor release, TCMS suggest you clone the test run ,but not clone the test > > plan. > > The bug information about test case could be reserved in cloned test run. > > > > recommended solution in TCMS is : > > use test plan for organize test cases of different products or different > > versions of product. > > use test run to execute test case in different release/build. > > > > Hope this can help. > > That was just an example of use case. Simply put, I don't want to loose the bug > associated with test case when I clone it. > When clone test plan, in copy settings, uncheck the option:Create a copy (Unchecking will create a link to selected plans) then the cases in the new plan will link to the origin , the bug information wouldn't be lost. as attachment. > TCMS should be flexible to suite our workflow, not the other way around. Created attachment 532210 [details]
clone settings in clone test plan
*** Bug 760577 has been marked as a duplicate of this bug. *** |