test(azure-client, tinylicious-client): Ensure test results are correctly published for CI - #27863
Conversation
|
Hi! Thank you for opening this PR. Want me to review it? Based on the diff (35 lines, 6 files), I've queued these reviewers:
How this works
|
|
[Microsoft only] Here is a sample run with an intentionally failing test that demonstrates tests correctly appearing in the test browser: https://dev.azure.com/fluidframework/public/_build/results?buildId=414628&view=ms.vss-test-web.build-test-results-tab |
68afc0e to
0e63e8c
Compare
This reverts commit 3f8dc4e.
Bundle size comparisonBase commit: Pending — |
Bundle size comparisonBase commit: Notable changesNo bundles changed by ≥ 500 bytes parsed. Per-bundle deltas
|
Test results for the
ci:test:realsvc:tinylicioustest script were not being correctly generated and published in CI forazure-clientandtinylicious-client.There were 2 issues preventing these results from correctly showing up in the test viewer in the Azure DevOps pipeline views:
mocha-test-setup/mocharc-common.npm run test:copyresultsstep of the build pipeline was not configured to run when the test step(s) failed, which caused the failed test reports to not be in the expected place when the subsequent publish step ran. The conditions for this step have been updated to run so long as the test runs were started.AB#74374