Version Collection Mockups revised

[isaacdurazo]

Revisions based on plans and discussion in #406.

General updates

• All scenarios should include a Close icon (X) in the upper right corner, which will display an exit dialog (see design below). After confirming they want to exit they should be taken back to the Test Queue.
• If no changes have been made in the AT or Browser versions we should display only a "Continue" button
• If there has been a change, we should display a "Save and Continue" button and a "Cancel" button
• When a change has been made and the user saves and continues, we should display a Success toast message on the Test Run page (see design below).

Tester Scenarios

Opening a Test Run for the very first time.

• The Browser and AT names are predefined because this information comes from the Test Queue.
• The Browser Version is automatically detected but can be modified.
• The AT Version needs to be provided by the Tester.
• If the user clicks Save and Continue without providing an AT Version, we should display a validation error.

Coming back to continue testing and my AT/Browser version hasn’t changed

• The only available action is “Continue”
• If the user modifies any of the selections in the form, the “Continue” button changes to “Save and Continue” and a “Cancel” button appears in the modal. (see next mockup)

• This is how the modal actions should change if the user makes a change
• The Cancel button lets the user proceed to the Test Run page, but without saving the changes

Coming back to continue testing with a different browser.

• In this scenario, we can’t automatically pre-fill the form with the new Browser details because this information is predefined in the Test Queue.
• A Continue button is the only button available.
• If for whatever reason the user modifies anything in the form, the Continue button should change to Save and Continue and a Cancel button should be displayed

Opening a Test plan for the first time with the wrong Browser

• In this scenario, the tester opens a test plan for the first time with a browser that's different from the required one.

Coming back to continue testing with a different browser version.

• The Browser version input field gets focused automatically to make it clear it’s been updated.
• Since there has been a chance, there’s a Cancel button, which would take the user to the Test run but with the previous Browser version used.

Coming back to continue testing and a different Browser version from the one detected has been selected.

• Since there has been a chance, there’s a Cancel button, which would take the user to the Test run but with the previous Browser version used.

Coming back to continue testing and a different AT version from the one previously used has been selected.

• Since there has been a chance, there’s a Cancel button, which would take the user to the Test run but with the previous Browser version used.

Opening a Test Run and the browser version couldn’t be detected

• Focus goes to the Browser version input field

Exit Dialog

Success Toast Message

• If the user makes changes with regard to versions and the save and continue, we should display the following success toast message.
• There are 3 variations
  • Saving their AT and Browser version for the first time:
    • Your AT and Browser versions have been successfully saved.
  • Updating their AT version
    • Your version of [AT name] has been updated to [version X]. Your previous version was [version Y].
  • Updating their Browser version
    • Your version of [Browser Name] has been updated to [version X]. Your previous version was 98.0.4758.109.

Admin scenario

• The main thing that changes in this scenario is the "Continue" button.
• If the Admin makes a change, we should change it to "Save and Continue" and add a "Cancel" button