This is the Go module for the test-results server (https://test-results.appspot.com). Remaining parts are in the default Python module located at
infra/appengine/test_results. Each handler will eventually be migrated from the Python application to Go.
For the list of paths handled by the Go module, see
For more details, see the README at
apt-get install nodejs apt-get install npm npm install -g bower npm install -g vulcanize
Google employees should follow instructions at http://go/nodejs to install NodeJS 4.x or later.
To set up the go environment, run:
To run test-results locally:
You can use the -F flag with curl to send multipart/form data. For example, to send request to test
curl -v -F master='tryserver.chromium.mac' -F builder='linux_chromium_rel_ng' -F file=@<local-path-to-test-results-file> -F testtype='browser_tests (with patch)' http://localhost:8080/testfile/upload
This can be useful if you want to debug a vulcanized file containing combined and compressed source of all used components. This is actual code used in production. Note that this should not be used for normal development on a local devserver since changes to source code of the components will not be result in changes in the tested app. To go back to normal development, please run
Use the migrate traffic button on the appengine console to move traffic to the new service. Then monitor viceroy for 10-20 minutes.
A few services use test results from test launchers running on Chromium Infrastructure to provide useful data for developers:
You can start uploading your test results in 3 steps:
tryserver.chromium.linux(note the missing
browser_tests (with patch), and
Recommended way to implement this is to use test_results.upload function in the recipe that is running your test, e.g. see example. However, if for some reasons you can not do that, you can also use this example in Python.
If something is unclear, please let us know at firstname.lastname@example.org and we’ll use your feedback to improve this doc.