a user should be able to edit a test case, even when it's active

RESOLVED FIXED

Status

Mozilla QA
MozTrap
--
enhancement
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: camd, Unassigned)

Tracking

Details

(Reporter)

Description

6 years ago
need to be able to create new versions of active test cases for ongoing testing.
(Reporter)

Comment 1

6 years ago
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/20218265
(Reporter)

Comment 2

6 years ago
Cameron Dawson changed story state to started in Pivotal Tracker
(Reporter)

Comment 3

6 years ago
Carl Meyer added a comment in Pivotal Tracker:   
   
I think this is blocked by platform behavior regarding test case steps; need to look into it a bit more tomorrow to be sure and file platform bug.
(Reporter)

Comment 4

6 years ago
Carl Meyer changed story state to finished in Pivotal Tracker
(Reporter)

Comment 5

6 years ago
Carl Meyer changed story state to delivered in Pivotal Tracker
(Reporter)

Comment 6

6 years ago
Carl Meyer added a comment in Pivotal Tracker:   
   
I was wrong about the platform blocker here - was getting fooled by the way it automatically duplicates the previous testcase version's steps for the new version. I think this is working, could probably use more testing to catch any broken edge cases I may have missed.
(Reporter)

Comment 7

6 years ago
Cameron Dawson added a comment in Pivotal Tracker:   
   
that's good news!  I was trying it out on cc-dev and am hitting something odd.  I tried to add a step to this case: https://cc-dev.oddsites.net/manage/testcase/3/ and when I go to save, I don't get any indication that it DID save it.
(Reporter)

Comment 8

6 years ago
Carl Meyer added a comment in Pivotal Tracker:   
   
Oops. Made a last-minute change to remove the "in-place/new-version" dropdown, since "new version" is the only choice for an active case, and didn't test that adequately. I just put the dropdown back - probably better to be explicit anyway. Should be fixed now.
(Reporter)

Comment 9

6 years ago
Cameron Dawson added a comment in Pivotal Tracker:   
   
cool, that looks like it works!  a good thing, too.  because I just noticed that you can't clone an active test case either.  Is cloning and env narrowing a totally separate issue?
(Reporter)

Comment 10

6 years ago
Carl Meyer added a comment in Pivotal Tracker:   
   
I'm able to clone an active test case. Where are you seeing that you're not able to?

Environment narrowing of active cases is separate. I think the platform might allow it for active cases, but once a case-version is included in a run it won't let you anymore. Can you make a separate story for that?
(Reporter)

Comment 11

6 years ago
Carl Meyer added a comment in Pivotal Tracker:   
   
Platform won't allow deletion of an active case, if you meant that, not cloning. And I was wrong - it won't allow any env narrowing of an active case, either, regardless of inclusion in a test run.

Fortunately the work around for both of these is pretty simple now - edit the active case, create a new version of it, the new version will be draft and you can do whatever you like to it.
(Reporter)

Comment 12

6 years ago
Cameron Dawson added a comment in Pivotal Tracker:   
   
argh... you're right.  Sorry, it was delete and env that aren't available for active.  
as a work-around, if you edit a case, it becomes draft mode, then you can do those things...  :)
(Reporter)

Comment 13

6 years ago
Carl Meyer added a comment in Pivotal Tracker:   
   
Hmm, just noticed that cloned cases aren't auto-approved. Fixing that now...
(Reporter)

Comment 14

6 years ago
Cameron Dawson added a comment in Pivotal Tracker:   
   
Awesome, thanks.  But this looks good!
(Reporter)

Comment 15

6 years ago
Cameron Dawson changed story state to accepted in Pivotal Tracker
(Reporter)

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.