Further Reporting Enhancements

Bug #1509015 reported by Nicholas Skaggs on 2015-10-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Community Testing
High
Unassigned

Bug Description

This bug represents the collated feedback from the various consumers of the reporting found on the https://ubuntu-community-testing.staging.ubuntu.com/reports/.

For the next iteration of reporting, we'd like the following data fields to be present:

device info (this should be captured by the automated job)
build info (this should be captured by the automated job)
data submitted
lp id on comments

These next two fields probably don't exist in the original data stream, but would be useful to have:
pilot version
application version (at least for when we test apps directly)

In addition, it would be useful to make some changes to how the information is displayed. These may warrant further discussion.

Can you add an overal success / failure rate for a testsuite (ie, 2014.com.ubuntu.clock)
Can we support sorting by project and date / run? So we can see all tests for clock by date?
Can we define / update the color scheme for success rate? Having the color coding on the Pass/Skip/Fail sections makes it harder to understand which app / testsuite is doing well and which are having tons of failures.
Can we introduce filters for things like date, success / failure, comments, specific lp id, application versions, pilot versions ?

Anastasia (anastasia-macmood) wrote :

I am pretty sure that veebers is not working on this bug.

Changed in ubuntu-community-testing:
assignee: Christopher Lee (veebers) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers