Tracking issue for setup-scripts - Githubissues

nextest-rs / nextest

A next-generation test runner for Rust.

https://nexte.st

Apache License 2.0

2.11k stars 92 forks source link

Tracking issue for setup-scripts #978

Open sunshowers opened 11 months ago

sunshowers commented 11 months ago

Initial implementation: https://github.com/nextest-rs/nextest/pull/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.

tisonkun commented 1 month ago

This setup script seems to be executed before test. How can I do if I'd set up a database and teardown after the test suite finished?

For non-blocking start, I may use & to keep the database running in the background. But it seems missing a teardown script hook.