868471 - Would be nice if Report document url was the dashboard report rather than raw data

Status: RESOLVED INVALID

(Mozilla QA Graveyard :: Mozmill Automation, enhancement)

Description

[Jonathan French (:jfrench)]

Maybe just me, but at the end of a manual testrun in mozmill-automation, the url produced would be nicer if it was the actual report in the dashboard, rather than the raw data file.

eg. testrun_addons.py
Report document created at 'http://mozmill-crowd.blargon7.com/db/452ec32f8deec0960aea87aa06861de1'

would be:
Report document created at 'http://mozmill-crowd.blargon7.com/#/addons/report/452ec32f8deec0960aea87aa06861de1'

This way if the user pasted it into a browser, they'd see a human readable result. I was digging around this morning in the repo (eg. testrun.py) trying to find where 'Report document created at' was being constructed, but haven't found it yet. 

This is a low priority marker bug, for that potential improvement, if it makes sense.

One could even go one step further, and add an additional command line arg which would spawn the user's default browser at the end of the testrun, so they'd be immediately taken to the report (rather than cut and paste). But I am guessing viewing reports that are manually fired, is a low frequency activity.

If none of this is the case, feel free to mark the bug invalid.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2] (away July 24th - August 16th)]

Sending the report is happening here:
http://hg.mozilla.org/qa/mozmill-automation/file/3a22993b9996/libs/testrun.py#l396

The code involved here is completely inside of Mozmill. We don't have a way to change the output. We could only add another line to our own code which tries to magically construct the correct URL given the specified remote site, report id, and currently active testrun id.

Should be a fine mentored bug.

Comment 2

[MikeLing]

Hi I am interested in working on this bug,but it's my first time to work on with debug,can anybody guide me on how to get started with it?Thanks a lot.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+2] (away July 24th - August 16th)]

The repository which has to be cloned can be found in the URL field. Then have a look into lib/testrun.py and search for send_report. The command you will have to execute as of now to send a report will contain the option '--report http://mozmill-crowd.blargon7.com/db/'.

Comment 4

[Santosh Kumar]

Hi Henrik,
I am willing to work on this bug.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2] (away July 24th - August 16th)]

That's great Santhosh. I will assign this bug to you. Remaining questions we can most likely solve on IRC.

Comment 6

[Dave Hunt [:davehunt] [he/him] ⌚BST]

Note that with this changed we would also need to update our email notifications for Mozmill CI. I have raised this here: https://github.com/mozilla/mozmill-ci/issues/271

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+2] (away July 24th - August 16th)]

Looks like  Santash is not working on this bug.

Comment 8

[Henrik Skupin [:whimboo][⌚️UTC+2] (away July 24th - August 16th)]

This is https://github.com/mozilla/mozmill-automation/issues/143 now.