-
-
Notifications
You must be signed in to change notification settings - Fork 658
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
There was a problem hiding this 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
After enabling |
- run: yarn install --frozen-lockfile --ignore-scripts | ||
- run: yarn build | ||
- run: yarn build:frontend |
There was a problem hiding this comment.
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)
.github/workflows/build_prs.yaml
Outdated
@@ -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 |
There was a problem hiding this comment.
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
d298b04
to
926e7cc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
6fb4e29
to
cb83b9b
Compare
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.