-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Capture engine/run unit tests with prysk #3592
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
Capture engine/run unit tests with prysk #3592
Conversation
Combine with existing Topological Deps integration tests.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
🟢 CI successful 🟢Thanks |
@@ -24,3 +24,19 @@ Check my-app#build output | |||
Cached: 0 cached, 2 total | |||
Time:\s*[\.0-9]+m?s (re) | |||
|
|||
|
|||
|
|||
Graph |
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.
What's the goal of this test? I'm not really that well versed in this part of the codebase.
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 merged in from here: https://github.com/vercel/turbo/blob/main/cli/integration_tests/topological_deps/graph.t
The underlying config is:
{
"$schema": "https://turbo.build/schema.json",
"pipeline": {
"build": {
"dependsOn": ["^build"]
},
"//#build": {
"dependsOn": []
}
}
}
So I think the idea is to validate that the task graph is generated correctly
Co-authored-by: Nicholas Yang <nicholas.yang@vercel.com>
This converts more unit tests to integration tests. The purpose of this change is to make it easier to land #3562, which breaks all these unit tests, and it's a lot of unnecessary work to fix as unit tests. Additionally, because we're lazy loading task definitions in that PR, these unit tests would need access to a file system, breaking their "unit" nature, anyway.
--graph
, because that's what the underlying tests were doing also. I could execute, but parallel execution makes it a bit more challenging to assert against logs.topological-deps
integration tests.Previous similar work: