-
Notifications
You must be signed in to change notification settings - Fork 0
User guide
- Importing Test Results
- Moving a Test Report
- Deleting a Test Report
- Editing Test Results
- Emailing and Printing Test Results
- Reading Test Reports
- Comparing Main and Test Branches
- Viewing Detailed Test Results
In order to import new test results, you will need a user account on the MeeGo QA Reports service. After you have logged in, the "Add report" button can be found in the upper right corner.
You can input the test execution date in YYYY-MM-DD format, or click the calendar icon to choose the date from a calendar view.
Test type and hardware can be freely typed in, or you can click on the commonly used options on the right.
If you are using a modern version of Google Chrome or Mozilla Firefox, you can drag and drop one or multiple files on the upload box. You can also click the button titled "Choose File" to browse and select files from your local folders.
The QA Reports tool expects the uploaded files to be in XML format. There is also legacy support for CSV files with a specific format (see QA Reports CSV Format) but this should not be used for other than legacy reasons.
If you upload more than one test result file, they merged into a single test report.
Clicking the button labeled "Next" below the upload form takes you to the Finalize-view, which lets you review and edit the report. At this point, the report is not yet visible on the server, and you must click the Finalize button at the end of the report in order to save the report and make it publicly visible.
Click "Edit" -> "Test execution date and category" and make the changes as needed as shown in the screenshots below
If you are logged in, you can delete a test report by viewing it and clicking the Delete button next to the test report title. Deleting a report is irreversible. The report and all changes made to it are permanently removed.
Majority of the data comes from the uploaded test result file, and cannot be modified afterwards, but you can make limited adjustments to some of the data and add explanatory text sections.
In order to make any of the following changes, you need to be in edit mode. To enter the editing mode, you must be logged in and viewing a report. You can then click the button labeled "Edit" next to the test report title. The edit mode is also automatically enabled when you are finalizing a newly uploaded report.
In edit mode, you can click the test report title in order to modify it. After making your changes, click the Save-button to commit them or Cancel to restore the original title.
All the text sections such as Test Objective, Test Environment and Quality Summary can be edited by clicking them. The content uses a slightly modified sub-set of the MediaWiki format for formatting text. The syntax reference is also available next to text area.
Headers and sub-headers can be added by using lines beginning with == and ===. E.g.
== Some Header ==
=== Some Sub-header ===
You can italicize a section of text by enclosing it in a pair of single quotes or bold it by using three single quotes. Example:
''This is italic''
'''This is bold'''
You can create bulleted lists by starting your lines with an asterisk. Example:
* Item 1
* Item 2
* Item 3
You can link to external pages by using the syntax [[url Title]], for example:
[[http://meego.com MeeGo]]
As a shorthand, you can directly link to the MeeGo bug tracker by entering the bug id, e.g.
[[11780]]
The title and current status of the bug will be automatically fetched and updated to the test report.
You can change the test result (pass/fail/na) of an individual test case by clicking on the result and selecting a new one from the drop down. Any change you make is committed immediately to the server.
You can edit the notes of an individual test case by clicking the note field of that test case (i.e. the rightmost column in the table). The note field supports the same formatting options as all the regular text fields, with one difference: bugzilla links do not render the full bug title, but only the bug id. The title can been seen by hovering the mouse cursor over the bug id.
You can add or remove file attachments to a test report from the attachments area at the end of the report. Just click the "Add attachment" button and browse to the local file you want to attach.
If you need to delete an attachment, click the X-icon next to the attachment when in edit mode.
When viewing a test report, you can click the Print-button to access a simplified layout that is optimized for priting and emailing.
You can subscribe to RSS feeds of newly created reports with any RSS reader. To access a specific RSS feed, follow the category links from the front page and click on the RSS icon in the main header.
- To subscribe profile specific reports, click e.g "Core" on the front page
- To subscribe test type specific reports, click e.g. "Core > Sanity" on the front page
- To subscribe hardware specific reports, click e.g. "Core > Sanity > N900" on the front page
On the group report page, click RSS icon as shown below.
When uploading a new test report, the report can be marked as belonging to the testing branch, by postfixing the test type field with the special marker: :testing as shown in the picture below
This enables viewing a comparison between a test type such as "Sanity" and its test branch "Sanity:testing". If the comparison view is available, a "compare"-link will appear on the front page next to the test type title.
When viewing detailed test results, one can choose to view only failed test cases, all test cases, or the history of all test cases (five last test runs) as shown in the screenshot below



















