Bug 685067
Summary: | Missing options for preserving test statuses/assignees when cloning the run. | ||
---|---|---|---|
Product: | [Other] TCMS | Reporter: | Martin Banas <mbanas> |
Component: | Web UI | Assignee: | June Zhang <junzhang> |
Status: | VERIFIED --- | QA Contact: | Nobody <nobody> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.3 | CC: | azelinka, GFENG, jcai, junzhang, ryang, vchen, xkuang, yuwang |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | --- | Flags: | xgao:
needinfo-
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | tcms 3.7.0-2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 593666 |
Description
Martin Banas
2011-03-15 08:10:38 UTC
(In reply to comment #0) > Description of problem: > In older TCMS or maybe testopia we were able to preserve test case assignees or > statuses when cloning the run. It would be great if the functionality is back. > Older TCMS doesn't this functionality. The functional is good, we will enhance cloning setting in the further version. Thanks for your advice. (In reply to comment #1) > Older TCMS doesn't this functionality. > The functional is good, we will enhance cloning setting in the further version. > Thanks for your advice. As far as I remember, this was available in Testopia. I thought it was available in nitrate at least partially as well (assignee field). Anyway it's great to see this on feature future list. :) Thank you! Verify version 3.6.0-1 on englab - FAIL Steps: 1. Find a run with one more case-run, and open it. Such as: https://tcms.englab.nay.redhat.com/run/26465/ 2. Select some cases. Such as case 109425, 109877, 109673, 109647 3. Click "Clone". 4. Do not check "Reserve Assignee". 5. Click Save. Actual result: case-run in new run has same assignee with the origin one. refer to following link. https://tcms.englab.nay.redhat.com/run/26882/. When do not check "Reserve Assignee", I thought that new assignee should be same with run's default tester. Actually, through talking with pm, got that new assignee should be same with case's default tester. It's my fault. So pls ignore comment 3. and new verification info is as follows. Verify version 3.6.0-1 on englab - PASS Steps: 1. Find a run with one more case-run, and open it. Such as: https://tcms.englab.nay.redhat.com/run/26465/ 2. Select some cases. Such as case 109425, 109877, 109673, 109647 3. Click "Clone". 4. Do not check "Reserve Assignee". 5. Click Save. Actual result: New assignee are same with case's default tester. It seems in tcms-stage - 3.7.0-1, the "Reserve Assignee" can't work. When cloning a single run, uncheck the "Reserve Assignee", and input a new default tester which is different from any of the assignees of the cases in the run, then "Save". Actual result: In the new cloned run, the assignees are still original ones. This bug was fixed in tcms 3.7.0-2. When cloning a single run, uncheck the "Reserve Assignee",input a new default tester which is different from any of the assignees of the cases in the run, the new testruns assignees will be the default tester. verify result --> pass verify version tcms-3.7.0-2 on stage verify step 1. Find a run with one more case-run, and open it. Such as: https://tcms.englab.nay.redhat.com/run/26465/ 2. Select some cases. Such as case 109425, 109877, 109673, 109647 3. Click "Clone". 4. Do not check "Reserve Assignee". 5. input a new default tester. 6. Click Save result work well. The new testruns assignees is the default tester. |