-
Notifications
You must be signed in to change notification settings - Fork 489
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
Boilerplate for integration tests (within js-sdk) #519
Conversation
|
…stress-test-e2b-1360
…s stress test to integration suite
@@ -35,7 +35,8 @@ | |||
"update-deps": "ncu -u && pnpm i", | |||
"postPublish": "./scripts/post-publish.sh || true", | |||
"test:bun": "bun test tests/runtimes/bun --env-file=.env", | |||
"test:deno": "deno test tests/runtimes/deno/ --allow-net --allow-read --allow-env --unstable-sloppy-imports --trace-leaks" | |||
"test:deno": "deno test tests/runtimes/deno/ --allow-net --allow-read --allow-env --unstable-sloppy-imports --trace-leaks", | |||
"test:integration": "E2B_INTEGRATION_TEST=1 vitest run tests/integration/**" |
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.
can we do it only based on directory structure? 🙏
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.
IIRC, I initially tried that, but the way vitest workspace works makes it impossible to exclude the integration tests when when running pnpm test
, bc that just picks up everything — maybe i'm missing something tho!
Co-authored-by: Jakub Novák <jakub@e2b.dev>
…ess-test-e2b-1360
Description
pnpm test:integration