Merge lp:~canonical-platform-qa/ubuntu-community-testing/improved-reporting into lp:ubuntu-community-testing
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Christopher Lee on 2015-10-16 | ||||
Approved revision: | 50 | ||||
Merged at revision: | 35 | ||||
Proposed branch: | lp:~canonical-platform-qa/ubuntu-community-testing/improved-reporting | ||||
Merge into: | lp:ubuntu-community-testing | ||||
Diff against target: |
704 lines (+466/-124) 9 files modified
ubuntu_pt_community/pages/pages.py (+40/-9) ubuntu_pt_community/pages/reports.py (+235/-91) ubuntu_pt_community/templates/base.html (+1/-0) ubuntu_pt_community/templates/results/all_testsuite_overview.html (+45/-0) ubuntu_pt_community/templates/results/all_testsuites.html (+0/-23) ubuntu_pt_community/templates/results/index.html (+1/-1) ubuntu_pt_community/templates/results/overview_base.html (+33/-0) ubuntu_pt_community/templates/results/test_drilldown_details.html (+69/-0) ubuntu_pt_community/templates/results/testsuite_drilldown.html (+42/-0) |
||||
To merge this branch: | bzr merge lp:~canonical-platform-qa/ubuntu-community-testing/improved-reporting | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Brendan Donegan (community) | 2015-10-12 | Needs Fixing on 2015-10-15 | |
Review via email:
|
Commit message
Improved reporting for uploaded test results.
Description of the change
Better reporting for the uploaded results.
Reporting types included (incl. reference to the image lines in the follow up branch.)
- [1] All application testsuite review
-> Shows breakdown of all application and their tests (pass/skip/fail
- [2] Singular application testsuite (same as above but shows single application (i.e. 2015.com.
- [3] Testsuite overview (click on an apps testsuite name to get to.)
-> Drilldown of the testsuite incl P/S/F
- [4] Test Drilldown (click on test name to get to this report)
-> Lowest level to go, shows P/S/F, comments. W/ plans to linkify comments referencing bugs.
Christopher Lee (veebers) wrote : | # |
I Ahmad (iahmad) wrote : | # |
I think there should be someway to see the latest test results at both testsuite and test case level.
- 50. By Christopher Lee on 2015-10-13
-
Added latest outcome to report.
Christopher Lee (veebers) wrote : | # |
> I think there should be someway to see the latest test results at both
> testsuite and test case level.
Added this at revno 50. Images showing this:
- testsuite details: http://
- test drilldown: http://
I Ahmad (iahmad) wrote : | # |
ok reporting looks good for now but it would be nice to see the date for last run, device it ran on, related bug links etc
I Ahmad (iahmad) wrote : | # |
and of course the information about the image/build and a graph/chart too.
Christopher Lee (veebers) wrote : | # |
@iahmad, sounds good all do-able. I would suggest getting this landed as is (well, within it's current scope) and iterate to add those additional things (with a defined scope, i.e. what does the graph/chart need to show.)
Brendan Donegan (brendan-donegan) wrote : | # |
Technically speaking the part of a provider name before the : is just an FQDN, so it doesn't really make much sense on its own. Therefore I'd have the top level of reporting be the full name of the provider, breaking down into individual testplans/
2014.com.
-> clock-app-alarm
-> clock-app-setting
-> clock-app-stopwatch
-> clock-app-worldcity
Also the testsuite overview seems to be mixing job plainbox execution unit (pxu) file names with test plan or whitelist file names. I'd have to look at the raw data to see what the reason for this is though.
Christopher Lee (veebers) wrote : | # |
> Technically speaking the part of a provider name before the : is just an FQDN,
> so it doesn't really make much sense on its own. Therefore I'd have the top
> level of reporting be the full name of the provider, breaking down into
> individual testplans/
>
> 2014.com.
> -> clock-app-alarm
> -> clock-app-setting
> -> clock-app-stopwatch
> -> clock-app-worldcity
I understand that the FQDN doesn't really make much sense in itself, but it's used here to collect the tests under a related header. For instance in your example there is no definition of 'clock-tests' (as the results come in named '2015.com.
Otherwise for the main overview there would be a _lot_ of tables (e.g. one for 2015.com.
As balloons has acked the existing reports and is really eager to see something I'm going to do the potentially rude thing and deploy this as is so we have something now and we can iterate on the specifics and improve it from there.
> Also the testsuite overview seems to be mixing job plainbox execution unit
> (pxu) file names with test plan or whitelist file names. I'd have to look at
> the raw data to see what the reason for this is though.
This is more than likely due to the example results that I've uploaded during my testing. I have a task to clear this out of the database and it should resolve the issue you're seeing. (You mention this due to the appearance of '2015.com.
These are images of the reports mentioned in the desc. of change.
[1] http:// people. canonical. com/~leecj2/ reporting/ reporting- overview. png people. canonical. com/~leecj2/ reporting/ reporting- suite-overview. png people. canonical. com/~leecj2/ reporting/ reporting- suite-drilldown .png people. canonical. com/~leecj2/ reporting/ reporting- test-details. png
[2] http://
[3] http://
[4] http://