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

task: Add Unit test result check task #3695

Merged
merged 12 commits into from
May 25, 2023
Merged

task: Add Unit test result check task #3695

merged 12 commits into from
May 25, 2023

Conversation

chriswk
Copy link
Contributor

@chriswk chriswk commented May 5, 2023

After a Team Retro, one of our squads felt like we needed more data on our test suites. This is the first effort to make our test results easier to grab. It uses the test-reporter action to add a github check to our main build and PR builds with our test results.

This at least should make it easier to parse which tests are failing. However, it does not give us trends. So it does not yet make it easier to decide which tests are flaky just from a quick view.

@chriswk chriswk self-assigned this May 5, 2023
@vercel
Copy link

vercel bot commented May 5, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
unleash-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 25, 2023 10:54am
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
unleash-monorepo-frontend ⬜️ Ignored (Inspect) Visit Preview May 25, 2023 10:54am

Copy link
Member

@sighphyre sighphyre left a comment

Choose a reason for hiding this comment

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

Awesome! Where does this report end up, out of curiousity?

Edit: Never mind, I see it in the failing output xD still happy with the approve though, it looks good overall outside of the failing report

@github-actions
Copy link

After enabling strictNullChecks this PR would be increasing the number of null check errors from 292 to 5762.
Make sure your branch is up-to-date with main and check the diff in the console output to pinpoint the offending files.

Comment on lines 33 to 35
- run: yarn install --frozen-lockfile --ignore-scripts
- run: yarn build
- run: yarn build:frontend
Copy link
Contributor

Choose a reason for hiding this comment

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

This is out of date, build is already building the frontend, but if we want to build frontend, I think we also need to remove --ignore-scripts (I'm not sure why we have them)

@@ -19,5 +19,4 @@ jobs:
cache: 'yarn'
- run: yarn install --frozen-lockfile --ignore-scripts
- run: yarn lint
- run: yarn build:backend
#- run: yarn build:frontend # not needed
- run: yarn build
Copy link
Contributor

Choose a reason for hiding this comment

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

Not sure if this is intended, but build will also build the frontend, in which case we need to remove --ignore-scripts from yarn install to also install frontend dependencies

Copy link
Contributor

@gastonfournier gastonfournier left a comment

Choose a reason for hiding this comment

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

LGTM!

.github/workflows/build_prs.yaml Outdated Show resolved Hide resolved
@chriswk chriswk merged commit 3409b0c into main May 25, 2023
9 of 10 checks passed
@chriswk chriswk deleted the task/addTestReporting branch May 25, 2023 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

3 participants