Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test(core): Log amazonq/toolkit tests at the bottom of the logs #6288

Draft
wants to merge 17 commits into
base: master
Choose a base branch
from

Conversation

jpinkney-aws
Copy link
Contributor

Problem

  • It's really annoying to have to scroll up the logs whenever amazon q tests fails

Solution

  • Print out everything at the bottom of the logs

Based off of: #6261


  • 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.

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
Copy link

  • 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
Copy link
Contributor Author

/runIntegrationTests

@jpinkney-aws jpinkney-aws changed the title Joined log test(core): Log amazonq/toolkit tests at the bottom of the logs Dec 23, 2024
@jpinkney-aws jpinkney-aws reopened this Dec 23, 2024
@jpinkney-aws
Copy link
Contributor Author

/runIntegrationTests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant