test(core): merge all package test reports

[jpinkney-aws]

Problem

• CI test reporting only captures the last package's results
• Running npm run testE2E only preserves toolkit's report.xml, losing other package results

Solution

• Generate individual report.xml files per subproject
• Consolidate all existing package reports into root .test-reports/report.xml
• This is done in the buildspecs themselves rather than directly in the package.json (the original approach to solve this problem) because mac/linux and windows have two different ways of getting the last error code, resulting in a complicated package.json for something thats only needed in our codebuilds

---

• Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
• Your code changes must meet the guidelines in CONTRIBUTING.md.

License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

[jpinkney-aws]

/runIntegrationTests

[github-actions]

• This pull request modifies code in src/* but no tests were added/updated.
  • Confirm whether tests should be added or ensure the PR description explains why tests are not required.

[jpinkney-aws]

/runIntegrationTests

[Hweinstock]

What are the tradeoffs for merging the report versus having one per extension? Curious because for code coverage we have separate ones.

[jpinkney-aws]

If you don't merge them you can't see them in the ui here: https://d1ihu6zq92vp9p.cloudfront.net/487310e6-ebfc-4fef-a0b1-b441147b3c23/report.html. That's really the issue i'm trying to solve. It's pretty annoying when an amazon q test fails and then you have to manually look through the logs to find the problem

I don't think that restriction applies to codecov since you can upload multiple different reports at the same time

[jpinkney-aws]

/runIntegrationTests

[jpinkney-aws]

/runIntegrationTests

[jpinkney-aws]

/runIntegrationTests

[jpinkney-aws]

/runIntegrationTests

[justinmk3]

Based on a local test of this command:

2>&1 echo aaa; echo bbb | grep x

I suspect the above ; may not correctly pipe all the output from npm test to run_and_report as intended.

To confirm that the piping to run_and_report is still working correctly, can you try temporarily changing this search patter to something that always outputs, like:

Suggested change

	'rejected promise not handled' \
	'deleteTestTempDirs' \

then CI should fail.

If it doesn't, we can fix the issue by changing the pipeline to something like (note: whitespace near the braces is required):

 { 2>&1 xvfb-run npm test --silent; npm run mergeReports -- "$?"; } | run_and_report 2 \