Closed Bug 854432 Opened 11 years ago Closed 11 years ago

[dev] Reordering cases in existing suite

Categories

(Mozilla QA Graveyard :: MozTrap, defect)

x86_64
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: AndreiH, Assigned: camd)

References

()

Details

(Whiteboard: [fromAutomation])

Steps to reproduce:
1.go to https://moztrap-dev.allizom.org and sign in
2.navigate to manage/suites
3.click the edit icon next to a suite with cases
4.once ajax is done loading, reorder the suite's cases using drag and drop
5.click "save suite" button
6.go back to the edited suite and see the list of cases in the right order

Expected results:
The cases should be ordered as we saved them.

Actual results:
The cases are still in the same order.

Here is a video:
http://screencast.com/t/hQ74ILSLA
Whiteboard: [fromAutomation]
Thanks for catching this!  Yep, this happens on staging, too (which has the same code)
Working on it now.
Assignee: nobody → cdawson
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/46841043
Cameron Dawson changed story state to started in Pivotal Tracker
ok, this is fixed in branch 1.4.5.  My code wasn't detecting when a change in order only was happening.  Pushed to Stage and dev.
Cameron Dawson changed story state to finished in Pivotal Tracker
Cameron Dawson changed story state to accepted in Pivotal Tracker
Cameron Dawson changed story state to accepted in Pivotal Tracker
fixed and pushed to staging
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
thanks Cameron for the response.
this is verified and fixed on stage, but I can still reproduce it on dev
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I am unable to repro the issue on moztrap-dev, my re-arranged tests within a suite stay in order. Staging and prod look good also [had to double check!].
the dev update script was borked for a bit.  but fixed by IT now, so glad things are working there, too.  So I'm going to close fixed for now.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Verified both on stage and dev. This is fixed. Thanks !
Status: RESOLVED → VERIFIED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.