865
edits
QA/TDAI/QAC Design Lunch Notes 2009-07-23: Difference between revisions
QA/TDAI/QAC Design Lunch Notes 2009-07-23 (view source)
Revision as of 01:34, 12 August 2009
, 12 August 2009→Statistics Tab
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Notes from Design Lunch = | = Notes from Design Lunch = | ||
* '''now''' It ought to choose the platform etc when you submit the bug | * '''now''' <strike>It ought to choose the platform etc when you submit the bug</strike> | ||
* '''now''' <strike>Use "pass" in green, and "fail" in red</strike> | * '''now''' <strike>Use "pass" in green, and "fail" in red</strike> | ||
* '''now'''add a spinner in the background when you're typing for the duplicates search so the user knows that something is happening in the background | * '''now'''<strike>add a spinner in the background when you're typing for the duplicates search so the user knows that something is happening in the background</strike> | ||
* '''now''' <strike>Instead of a dialog of dupes have the list appear between the bug summary and the bug description, have a spinner there while the bug list is being acquired</strike> | * '''now''' <strike>Instead of a dialog of dupes have the list appear between the bug summary and the bug description, have a spinner there while the bug list is being acquired</strike> | ||
* '''later''' Could you pull out the first comment of the bug? | * '''later''' Could you pull out the first comment of the bug? | ||
| Line 17: | Line 17: | ||
= Login Tabs = | = Login Tabs = | ||
''' For all the login items look what weave does and decide''' | ''' For all the login items look what weave does and decide''' | ||
* Look in the login manager and see if they have a litmus entry - if so then just present them with an option to login | * <strike>Look in the login manager and see if they have a litmus entry - if so then just present them with an option to login</strike> | ||
* Make it more prominent and have a button first that says "if you have a account, click here, if not, click here" (create an account or use an existing account). | * <strike>Make it more prominent and have a button first that says "if you have a account, click here, if not, click here" (create an account or use an existing account)</strike>. | ||
* If you detect that they already have a litmus login on the computer then go ahead and log that person in without prompting them at all. | * <strike>If you detect that they already have a litmus login on the computer then go ahead and log that person in without prompting them at all.</strike> - we set their credentials in field ready for them to see that | ||
* For the multiple account login stuff, do a wizard approach and ask which accounts thye have and which need to be created (future, gated on once we can create bugzilla logins) | * For the multiple account login stuff, do a wizard approach and ask which accounts thye have and which need to be created (future, gated on once we can create bugzilla logins) | ||
| Line 34: | Line 34: | ||
* '''now''' Add in the help link that takes people to a page on QMO for help | * '''now''' Add in the help link that takes people to a page on QMO for help | ||
* '''later, litmus v2''' Litmus v2 should also gate tests on a per OS approach | * '''later, litmus v2''' Litmus v2 should also gate tests on a per OS approach | ||
* '''now''' As soon as you click submit on the bugzilla tab disable it and replace it with a spinner to show that it is working. | * '''now''' <strike>As soon as you click submit on the bugzilla tab disable it and replace it with a spinner to show that it is working.</strike> | ||
* '''now''' When clicking on the bug in the "you submitted a bug" window the little window should close. | * '''now''' <strike>When clicking on the bug in the "you submitted a bug" window the little window should close.</strike> | ||
* '''now''' Could populate the buildID in the bug, and the litmus test id of the failing test. | * '''now''' Could populate the buildID in the bug, and the litmus test id of the failing test. | ||
* '''later''' If the bug number is known it should be displayed? Maybe if we detect that there is a regression bug ID then we could prepopulate the comment field with that bug id and linkify it so that the person running the test can go check out that bug. | * '''later''' If the bug number is known it should be displayed? Maybe if we detect that there is a regression bug ID then we could prepopulate the comment field with that bug id and linkify it so that the person running the test can go check out that bug. | ||