626917 - Need a way to manage test cycles

Status: VERIFIED FIXED

(Mozilla QA Graveyard :: MozTrap, enhancement, P1)

Description

[Aakash Desai [:aakashd]]

Attachment: mock-up

The TCM will need a pane for test cycle management. In this pane, the
following will be needed:

* A table of results entries with values shown for creation date, id, title, state.
* Default list of 20 results shown.
* A combobox to set the number of results per page going from 10,20,50 and 100.
When selected, the page should AJAX-ily update the listings area rather than
require a new page load.
* A checkbox per row entry when a logged in user is an admin
* Pagination that allows users to go to a certain page and to the beginning and
end of the set of results AJAX-ily.
* Edit (goes to individual test cycle create/edit page) and Remove (offers a dialog
to confirm whether to remove the test cycle or not...then deletes that cycle if
confirmed) hyperlinks are available per test cycle entry.

Comment 1

[Aakash Desai [:aakashd]]

Attachment: mock-up

Remove "State" as its not in the data model. It only applies to Test Runs; not test cycles.

Comment 2

[Aakash Desai [:aakashd]]

Attachment: mock-up

sigh the previous one was a bmml file

Comment 3

[Carl Meyer (:carljm)]

* Add "start date" and "end date" to displayed columns, perhaps remove "creation date" and "id"?
* We need an API call for the "clone" action.

Comment 4

[Aakash Desai [:aakashd]]

> Add "start date" and "end date" to displayed columns, perhaps remove
"creation date" and "id"?

Replacing creation date with start/end date works; I'd like to keep id though. 

> We need an API call for the "clone" action

Will do on the PRD

Comment 5

[Aakash Desai [:aakashd]]

Actually, removing id is fine too.

Comment 6

[Matt Evans [:mevans]]

>Remove "State" as its not in the data model. It only applies to Test Runs; not
>test cycles.

Hmm. I would think it has a state of at least active and completed. Or will the test cycle state be derived from it's test runs.

Comment 7

[Carl Meyer (:carljm)]

Test cycles do have their own state; the same set of possible states as a test run, actually.

Comment 8

[Matt Evans [:mevans]]

then we should display the value.

Comment 9

[Carl Meyer (:carljm)]

Since it looks like the bulk actions are not part of .2, we're going to leave the checkbox-per-row out for now as well since it would have no purpose yet.

Comment 10

[Carl Meyer (:carljm)]

(In reply to comment #9)
> Since it looks like the bulk actions are not part of .2, we're going to leave
> the checkbox-per-row out for now as well since it would have no purpose yet.

Uh, not sure what I was smoking there. Yes, these bulk actions are in .2, see https://bugzilla.mozilla.org/show_bug.cgi?id=627163

Comment 11

[Carl Meyer (:carljm)]

(In reply to comment #0)
> * Edit (goes to individual test cycle create/edit page) and Remove (offers a
> dialog
> to confirm whether to remove the test cycle or not...then deletes that cycle if
> confirmed) hyperlinks are available per test cycle entry.

In general, we'd opt for undoable deletes (see https://bugzilla.mozilla.org/show_bug.cgi?id=635031) rather than confirmation popups. UX research is pretty clear that undo is preferable to confirm; confirm just gets in your way all the time, and so you train yourself to mentally ignore it and confirm automatically, so it ends up not serving any purpose at all.

Comment 12

[Aakash Desai [:aakashd]]

> UX research is pretty clear that undo is preferable to confirm; confirm
> just gets in your way all the time, and so you train yourself to mentally
> ignore it and confirm automatically, so it ends up not serving any purpose at
> all.

Works for me!

Comment 13

[Carl Meyer (:carljm)]

Removing [API?] marker here, clone is moved out of 0.2 scope (but still in 1.0 scope).

Comment 14

[Carl Meyer (:carljm)]

Just noting that all list views will also include a filtering / faceting interface for narrowing the viewed list by e.g. product, state, ....

Comment 15

[Aakash Desai [:aakashd]]

For Carl: We won't need bulk actions on this panel anymore with the new mock-up.

Comment 16

[Aakash Desai [:aakashd]]

Now that we're going to include a drop down, we'll need to re-organize the data a bit. So, here's the details for it for a test cycle:

top-level: title, status (icon/image), start date, end date
pop-down level: id, description, creation date, created by, environment, testers

Comment 17

[Cameron Dawson [:camd]]

Looks great!  Tastes even better.