Litmus:Design: Difference between revisions
ChrisCooper (talk | contribs) No edit summary |
ChrisCooper (talk | contribs) |
||
| Line 35: | Line 35: | ||
== Sorting and limiting search results == | == Sorting and limiting search results == | ||
In the results display above each column heading would be clickable. Clicking the link would cause the results to be sorted by the relevant column. Clicking the link again would cause the results to sorted in reverse order by the same column. | |||
At the bottom of the results display will be query form that the user can use to limit their search results by all the fields in the display. Each field will have a drop-down selection list that will either be prepopulated from the database, or or a static list for infrequently changing fields. | |||
Infrequently changing fields, and the values associated with them: | |||
* Product: Firefox, Thunderbird, Seamonkey | |||
* Platform: Windows, MacOS, Linux | |||
* Status: PASS/FAIL/UNTESTED | |||
* State: DISABLED/? | |||
* Date: (Results in the) Last Day, Last 2 Days, Last Week, Last 2 Weeks | |||
Dynamic lists: | |||
* Test#/Name | |||
* Branch | |||
The query form will contain sort controls, with the ability to toggle the sort between ascending and descending. | |||
A text comparison field will allow the user to limit their query by a text-based matched. An associated comparison type list will allow the user to select whether they want an exact or a partial match. | |||
All of the above query form elements will be usable together, i.e. a user can select limiting criteria based on field, can sort their results, and can also perform tet-based matching in the same query. | |||
== Displaying a single result == | == Displaying a single result == | ||
Revision as of 16:38, 15 August 2005
Replicate Testrunner Functionality
Test Case Management
Automated Testing
Reporting (Result Querying)
High-Level Design
Access to reporting/querying
The Litmus start page will display a small table of recent test results. There will be links from this display that will take the user to a full reporting interface. There will also be links from the full reporting interface to access other parts of Litmus, including an option to return to the start page.
Tabular display
Much like Bugzilla, we are trying to display as much useful information as possible in a small space, hopefully without overwhelming the user.
The basic results display for querying will be a tabular display of all the relevant results that match the user's query. The tabular display will have the following basic layout:
| Date | Product | Platform | Test #/Name | Status | State | Branch |
The Test #/Name field will contain the shortest meaningful descriptor for a given test. To borrow some useful functionality from Tinderbox, the test name will be clickable, and when clicked, a floating popup will appear that will contain a longer description of the test, as well as any notes associated with the test. A link from this popup will the take user the full result display for that single test.
Sorting and limiting search results
In the results display above each column heading would be clickable. Clicking the link would cause the results to be sorted by the relevant column. Clicking the link again would cause the results to sorted in reverse order by the same column.
At the bottom of the results display will be query form that the user can use to limit their search results by all the fields in the display. Each field will have a drop-down selection list that will either be prepopulated from the database, or or a static list for infrequently changing fields.
Infrequently changing fields, and the values associated with them:
- Product: Firefox, Thunderbird, Seamonkey
- Platform: Windows, MacOS, Linux
- Status: PASS/FAIL/UNTESTED
- State: DISABLED/?
- Date: (Results in the) Last Day, Last 2 Days, Last Week, Last 2 Weeks
Dynamic lists:
- Test#/Name
- Branch
The query form will contain sort controls, with the ability to toggle the sort between ascending and descending.
A text comparison field will allow the user to limit their query by a text-based matched. An associated comparison type list will allow the user to select whether they want an exact or a partial match.
All of the above query form elements will be usable together, i.e. a user can select limiting criteria based on field, can sort their results, and can also perform tet-based matching in the same query.
Displaying a single result
Clicking on