618164 - Add a Run Tests page after a user has selected a set of test cycles to run

Status: VERIFIED FIXED

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

Description

[Aakash Desai [:aakashd]]

Attachment: mock-up

After a user select a list of test cycles to choose from, they should be directed to a list of test cases within the select test cycles to run through. 10 testcases should be shown on each page, at maximum, with the ability to do the following:

* Set a result: Not Started, Passed, Failed and Invalid
* Stop and Save edits within each page
* Continue to the next set of tests and save the results already made
* Reset all results on the page that has not been submitted

Also, each test case should have the following of its elements viewable in a read-only format:

* ID, Title
* Testcase, Test Suite
* Execution Steps, Expected Results

Comment 1

[Carl Meyer (:carljm)]

I recall that we discussed (in December) having changes take effect immediately (via Ajax) rather than bothering with the whole save-and-continue, reset thing, which is more confusing UI. And having one test case at a time displayed in full, with surrounding ones by default showing just title, but expandable.

Is that approach still OK?

Comment 2

[Aakash Desai [:aakashd]]

Yeah, that approach is fine

Comment 3

[Carl Meyer (:carljm)]

HTML wireframe at http://tcm.oddsites.net/test/product/1/cycles/1/

One thing we just noted that should probably also be included here at this stage is a link to view (and possibly change) your current testing environment.

There are some additional features ("make it better", related bugs, attachments) which are out of scope for release .1 and/or not yet present in the API, so they've been left out of the wireframe for now.

Comment 4

[Carl Meyer (:carljm)]

Added the link to view/change environment to this wireframe.

Comment 5

[Carl Meyer (:carljm)]

Additional note on the wireframe: the "pass/fail/invalid" button set is intended to appear after you click Start on a given test; the code isn't there to actually make that happen yet, but that's what the wireframe is intended to be showing.

The Start button is only needed due to the uTest requirement (as I understood it, at least) for the backend to be able to record "elapsed time" for a test.

Comment 7

[Aakash Desai [:aakashd]]

Attachment: mockup

Comment 8

[Matt Brandt [:mbrandt]]

Bumping to verified, shipped.