We need to offer e2e testing, besides what rust offer for integration testing per crate or unittesting
The idea would be to have e2e folder where these testing live.
-c/--config this will be required, as you want to test based on the config you will deploy.
We want to offer 3 different options:
- rust (by leveraging workspaces)
- python (by using uv)
- js/ts (this for later, great ecosystem but too opinionated like npm/yarn/pnpm/bun/deno)
The tool will coordinate the spawning of the cyberfabric system, and it will forward where the grpc host / rest host / unix socket, etc. To the env variable, so the tests can use that reference.
Ideally there should be a utils/entry library where the user can get easily the reference.
Rust:
Python:
We need to offer e2e testing, besides what rust offer for integration testing per crate or unittesting
The idea would be to have e2e folder where these testing live.
-c/--configthis will be required, as you want to test based on the config you will deploy.We want to offer 3 different options:
The tool will coordinate the spawning of the cyberfabric system, and it will forward where the grpc host / rest host / unix socket, etc. To the env variable, so the tests can use that reference.
Ideally there should be a utils/entry library where the user can get easily the reference.
Rust:
Python: