Skip to content

Commit

Permalink
Add page for Test Results in Treeherder
Browse files Browse the repository at this point in the history
  • Loading branch information
davehunt committed Apr 4, 2017
1 parent 999cad4 commit 971bb87
Show file tree
Hide file tree
Showing 2 changed files with 26 additions and 0 deletions.
1 change: 1 addition & 0 deletions reference/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ This is where all the useful information goes that doesn't fit into the
python-style
testing
activedata
treeherder
pypom
ci
irc-bot
Expand Down
25 changes: 25 additions & 0 deletions reference/treeherder.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
Test Results in Treeherder
==========================
`Treeherder <https://wiki.mozilla.org/EngineeringProductivity/Projects/Treeherder>`_
is Mozilla's reporting dashboard for checkins, builds, and test results. Our
automated test results are published to Treeherder via
`Pulse <https://wiki.mozilla.org/Auto-tools/Projects/Pulse>`_.

Submitting from Jenkins
~~~~~~~~~~~~~~~~~~~~~~~
To submit results from Jenkins you will need to write your job as a
`declarative pipeline <https://jenkins.io/doc/book/pipeline/>`_ using our
fxtest `shared library <https://github.com/mozilla/fxtest-jenkins-pipeline>`_.
See `the documentation <https://github.com/mozilla/fxtest-jenkins-pipeline#submittotreeherder>`_
for more information.

Viewing results in Treeherder
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To view the results for a particular project, open
`Treeherder <https://treeherder.mozilla.org/>`_ and select the appropriate
repository from the menu. Most of our projects will be found within the
'qa automation tests' group. You will then see a resultset for each commit to
that repository, and any associated test jobs will be displayed. Click a job to
find the test logs and report. The
`Treeherder User Guide <https://treeherder.mozilla.org/userguide.html>`_ may
also be useful.

0 comments on commit 971bb87

Please sign in to comment.