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.

Sign up for GitHub

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

Jump to bottom

Tracking issue for setup-scripts #978

Open

5 tasks

sunshowers opened this issue Sep 26, 2023 · 0 comments

Labels

Member

sunshowers commented Sep 26, 2023 •

edited

Loading

Initial implementation: [nextest-runner] add support for setup scripts #977
Documentation: https://nexte.st/book/setup-scripts.html

Open questions

How do we support build archive/reuse with Cargo binaries?
Is the current format for environment variables (KEY=value) okay? Do we need to check that KEY/value are unique identifiers?
Should we have a special syntax for running Cargo binaries? (Might tie into build archive/reuse discussions).
We likely need a numerical priority system, especially once tools are involved.
Gather community feedback.

sunshowers changed the title ~~Tracking feature for setup-scripts~~ Tracking issue for setup-scripts

This was referenced Sep 26, 2023

[nextest-runner] add support for setup scripts #977

Merged

Support for setup and teardown scripts #683

Open

sunshowers added the experimental label

adamchalmers mentioned this issue

Rust tests should use 1 engine instance KittyCAD/modeling-app#2580

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment