Remove obsolete test setup #269
Conversation
Vagrant is no longer shipped in Factory and new formulas already were not integrated into the setup anymore but rather ship test suites which can easily be invoked directly (though some logic could be abstracted to a new library). Signed-off-by: Georg Pfuetzenreuter <[email protected]>
|
Just wondering - would the If the answer is "no", I'm fine with deleting the unused/now useless tests. |
|
Interesting, will need to look into it - but it would in any case require writing a new framework around it, at least a quick search does not reveal any existing Pytest/Testinfra integration for it, and I think the files deleted here would not be useful with any new integration (they do not contain any tests, just tooling to execute the tests which are still inside the individual formula directories). Most test suites (like apache_httpd and 389ds which I already wrote independently) run fine against a regular Podman container, merely some run script / Makefile might be useful to gather the needed commands. The Vagrant layer was intended to support tests which need a cluster with nested virtualization, but I never finished #32 to make use of that. |
2 participants
Vagrant is no longer shipped in Factory and new formulas already were not integrated into the setup anymore but rather ship test suites which can easily be invoked directly (though some logic could be abstracted to a new library).