-
Notifications
You must be signed in to change notification settings - Fork 435
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(cli): remove v2 fixtures and bump timeouts #7974
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
No changes to documentation |
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: npm/[email protected], npm/[email protected] |
Component Testing Report Updated Dec 9, 2024 9:04 AM (UTC) ✅ All Tests Passed -- expand for details
|
⚡️ Editor Performance ReportUpdated Mon, 09 Dec 2024 09:05:47 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
5e43a2c
to
d6cdc47
Compare
d6cdc47
to
038b610
Compare
038b610
to
b8cc9b3
Compare
@@ -27,23 +27,7 @@ describeCliTest('CLI: `sanity build` / `sanity deploy`', () => { | |||
expect(result.code).toBe(0) | |||
|
|||
// These _could_ theoretically change, but is unlikely to with v2 being in support mode |
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.
Tiny nit: this comment looks to be redundant now?
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.
Looks good to me!
Description
Given that v2 has been EOL for a while, we can now safely remove v2 test and v2 specific code paths in our CLI test suite.
I started out debugging CI test failures, initially suspecting it had something to do with our old v2 tests still being run, but found out that it was caused simply by the tests taking longer to complete than usual, and now seem to have exceeded the default test timeout of 30s the cli tests are using. This PR also includes bumping the default timeouts to 60s.
Also includes a small change to make it easier to run CLI tests locally.
lmk if I should split these changes into separate PRs.
What to review
Does it look sensible? Are CI passing now?
Testing
n/a - this is improving tests
Notes for release
n/a - internal