Open
Description
Parsec E2E tests are implemented in Rust, but ran from an improvised framework written in bash. That makes the code a bit fragmented and the tests themselves rely on the environment/user to set everything up.
An alternative would be for us to implement a framework in Rust that runs all the tests that we need and handles the environment closer to the test material so that developers see exactly what's happening before and after their tests.
There's probably a bit of investigation here as to how best to handle this, since Rust isn't really a scripting language.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
jn9e9 commentedon Nov 8, 2021
sounds sensible- assuming you're thinking of rustifying the running of tpm backends etc done in ci.sh?
would be nice if whatever we come up with works well with non rust clients (we need to test the clients too!)
maybe define api config points for rust tests, and cli or some such exposure for non rust (e.g. go)? - just noodling