Update documentation of JSON test results format to include artifacts |
|||
Issue descriptionWe have agreement from John/Dirk on extending JSON test results format to include artifacts (bit.ly/chromium-test-artifacts). We should update the documentation to reflect the new standard. I think we should first start with porting https://www.chromium.org/developers/the-json-test-results-format to a markdown doc in https://chromium.googlesource.com/chromium/src/+/master/docs/testing/ first. This will allow updates to the doc to be code-review-able & enables history tracking.
,
Oct 20 2017
,
Dec 4 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e1e5bf9144cbdbeba1f5033a3c2303849d63cdad commit e1e5bf9144cbdbeba1f5033a3c2303849d63cdad Author: Stephen Martinis <martiniss@chromium.org> Date: Mon Dec 04 23:44:33 2017 Clarify artifact documentation for test results This clarifies the meaning of forward slashes in artifact file paths, and also clarifies the directory these paths are relative to, when no artifact permanent location is set. Bug: 775619 Change-Id: I1f41d86273455123823350a39b239cc04b6a0216 Reviewed-on: https://chromium-review.googlesource.com/802092 Commit-Queue: Stephen Martinis <martiniss@chromium.org> Reviewed-by: Ned Nguyen <nednguyen@google.com> Reviewed-by: Dirk Pranke <dpranke@chromium.org> Cr-Commit-Position: refs/heads/master@{#521525} [modify] https://crrev.com/e1e5bf9144cbdbeba1f5033a3c2303849d63cdad/docs/testing/json_test_results_format.md
,
Jan 5 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Oct 18 2017