This repository was archived by the owner on Dec 9, 2025. It is now read-only.
This repository was archived by the owner on Dec 9, 2025. It is now read-only.
Organize the e2e tests #137
Description
- We should have a more consistent structure, right now we use a github action and git submodules, but it seems it will be possible to use git for everything https://bats-core.readthedocs.io/en/stable/tutorial.html#quick-installation that will allow to have a more hermetic development workflow.
- We should have a make target , like
make e2e-testsor something like that - The e2e test grew holistically, with manifest spread on the ./examples/ folder and the e2e tests in the /tests/ folder, manifests for tests will be better into /tests/fixtures or /tests/manifests
- Remove the tests that depend on others, I added them just for velocity but tests should be independent
- Document better the tests in the contributor guidelines, in site/content/ ...
- Consider to split or reorganize better the tests , maybe we didn't get to that point yet, but something we may consider