Use a more human-friendly reporter for travis

RESOLVED FIXED

Status

RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: gaye, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
The gaia-ui-tests use the same tbpl reporter they use on TBPL on travis. It's very spammy and difficult for me to parse. Would you all mind turning on something like mocha's dot or spec reporters for when the tests run on travis?
I have no idea if there even are other reports for the runner?
Can you give an example of what's difficult to parse and how you would suggest presenting it? We do have a --html-output option but that would require us to set up artifacts (http://about.travis-ci.org/blog/2012-12-18-travis-artifacts/) to see the ones generated by Travis. Here's an example of a HTML report: http://people.mozilla.org/~dhunt/gaiatest_results.html

Comment 3

5 years ago
Yes I thought the Travis reporting was very readable myself:

TEST-START test_settings_app_permissions.py
test_open_app_permissions (test_settings_app_permissions.TestAppPermissions) ... ok
----------------------------------------------------------------------
Ran 1 test in 12.372s


TBPL on the other hand is definitely an explosion of mostly useless noise!
(Reporter)

Comment 4

5 years ago
Wow the html output one is beautiful! I was looking for something more like the one we currently have turned on for test-agent or marionette js on travis.
Flags: needinfo?(dave.hunt)
(Reporter)

Comment 5

5 years ago
I would be overjoyed though if you set up a way for me to look at the html ones on every travis build though!
Depends on: 925266
Raised bug 925266 for Travis CI artifacts.
Flags: needinfo?(dave.hunt)
Dependent bug was implemented so closing this one
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.