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

✨ Add properties to XML reporting based on status. #1125

Merged

Conversation

jwir3
Copy link
Contributor

@jwir3 jwir3 commented Nov 18, 2024

The status of particular test cases is now reported in the JUnit-formatted XML report. It is given as a <property> child element on the <testcase> element.

Refs CAP-2408.

📦 Published PR as canary version: 11.20.0--canary.1125.12016128389.0

✨ Test out this PR locally via:

npm install chromatic@11.20.0--canary.1125.12016128389.0
# or 
yarn add chromatic@11.20.0--canary.1125.12016128389.0

@jwir3 jwir3 added release Auto: Create a `latest` release when merged minor Auto: Increment the minor version when merged labels Nov 18, 2024
@jwir3 jwir3 requested a review from a team November 18, 2024 23:16
Copy link
Contributor

github-actions bot commented Nov 18, 2024

📦 Package Size: 5444 KB

@codykaup
Copy link
Contributor

@jwir3 I forget, is this one ready to be reviewed?

@jwir3 jwir3 force-pushed the jwir3/cap-2408-add-in-type-for-accepted-tests-in-a-junit-report branch 2 times, most recently from 42e1b46 to f439945 Compare November 19, 2024 22:33
@jwir3
Copy link
Contributor Author

jwir3 commented Nov 19, 2024

@jwir3 I forget, is this one ready to be reviewed?

Should be ready now. Thanks!

@codykaup
Copy link
Contributor

@jwir3 I forget, is this one ready to be reviewed?

Should be ready now. Thanks!

@jwir3 lint-and-test is still failing 🤔

Copy link
Contributor

@jmhobbs jmhobbs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lockfile change is huge. Need to re-run yarn maybe?

Screenshot 2024-11-19 at 4 40 51 PM

@jwir3 jwir3 force-pushed the jwir3/cap-2408-add-in-type-for-accepted-tests-in-a-junit-report branch 2 times, most recently from 3e31604 to 1ec939f Compare November 20, 2024 15:19
Copy link

codacy-production bot commented Nov 20, 2024

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
Report missing for 691ad521 93.33% (target: 80.00%)
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (691ad52) Report Missing Report Missing Report Missing
Head commit (06aeb09) 7140 4863 68.11%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#1125) 30 28 93.33%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more

Footnotes

  1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.

@jwir3 jwir3 requested a review from jmhobbs November 20, 2024 15:26
@jwir3
Copy link
Contributor Author

jwir3 commented Nov 20, 2024

@jmhobbs I had to checkout yarn.lock from main and then re-commit it after running yarn install. I think it's right now. Something was weird with it, though, because I also added back in TS error comments that I removed. Perhaps the original PR updated the typescript version? I'm not quite sure, but it should be fixed now.

Copy link
Contributor

@codykaup codykaup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works great over here! Just some questions about the refactoring bit!

node-src/tasks/report.ts Show resolved Hide resolved
node-src/tasks/report.ts Outdated Show resolved Hide resolved
node-src/index.test.ts Outdated Show resolved Hide resolved
Copy link
Contributor

@codykaup codykaup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, mean to "comment" instead of "approve" 😬

@jwir3
Copy link
Contributor Author

jwir3 commented Nov 21, 2024

Sorry, mean to "comment" instead of "approve" 😬

No worries. I'll re-request review before pushing after I make those changes.

The status of particular test cases is now reported in the
JUnit-formatted XML report. It is given as a `<property>` child element
on the `<testcase>` element.

Refs CAP-2408.
@jwir3 jwir3 force-pushed the jwir3/cap-2408-add-in-type-for-accepted-tests-in-a-junit-report branch from 1ec939f to 06aeb09 Compare November 21, 2024 16:57
@jwir3 jwir3 requested a review from codykaup November 21, 2024 16:57
Copy link
Contributor

@codykaup codykaup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, nice work!

@jwir3 jwir3 added this pull request to the merge queue Nov 21, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 21, 2024
@jwir3 jwir3 added this pull request to the merge queue Nov 22, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 22, 2024
@jwir3
Copy link
Contributor Author

jwir3 commented Nov 22, 2024

@brockwood Do you happen to know if this might be failing to merge on the merge queues possibly due to a token issue after all the token recycles yesterday?

@codykaup
Copy link
Contributor

@brockwood Do you happen to know if this might be failing to merge on the merge queues possibly due to a token issue after all the token recycles yesterday?

@jwir3 it's failed on a GraphQL query for some reason. 🤔

INTERNAL_SERVER_ERROR: Cannot return null for non-nullable field PullRequest.headRefName.

@codykaup
Copy link
Contributor

@brockwood Do you happen to know if this might be failing to merge on the merge queues possibly due to a token issue after all the token recycles yesterday?

@jwir3 it's failed on a GraphQL query for some reason. 🤔

INTERNAL_SERVER_ERROR: Cannot return null for non-nullable field PullRequest.headRefName.

Pretty sure this is related to me updating the smoke test project. Looking now!

@codykaup codykaup added this pull request to the merge queue Nov 22, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 22, 2024
@codykaup codykaup added this pull request to the merge queue Nov 22, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 22, 2024
Copy link

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
Report missing for 691ad521 93.33% (target: 80.00%)
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (691ad52) Report Missing Report Missing Report Missing
Head commit (06aeb09) 7140 4863 68.11%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#1125) 30 28 93.33%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more

Footnotes

  1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.

@codykaup codykaup added this pull request to the merge queue Nov 22, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 22, 2024
@jwir3 jwir3 added this pull request to the merge queue Nov 25, 2024
Merged via the queue into main with commit e29b808 Nov 25, 2024
21 checks passed
@jwir3 jwir3 deleted the jwir3/cap-2408-add-in-type-for-accepted-tests-in-a-junit-report branch November 25, 2024 18:06
@chromatic-ci-bot
Copy link
Collaborator

🚀 PR was released in v11.19.0 🚀

@chromatic-ci-bot chromatic-ci-bot added the released Verdict: This issue/pull request has been released label Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
minor Auto: Increment the minor version when merged release Auto: Create a `latest` release when merged released Verdict: This issue/pull request has been released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants