Description
This is a sub-issue of #726.
An integration testing framework to ensure that drunc executes correctly in an SSH shell environment, with default options, and produces the expected output/state transitions. Currently, the integration tests validate the basic commands (boot-> conf -> start etc.) without any options. The new integration tests in ./integtest/ should test the command sequence with the following parameters:
Potential impact radius
Small/Isolated
Reason for change
Validate that drunc workflow works reliably on different platforms and ensure new changes don't break functionality.
Suggested implementations
- new
./integtest directory to contain integration tests
- use CLIRunner to run each command via SSH shell PM
- use
--integtest-ssh-shell marker to run the tests
- check outputs and state transitions
- capture CLI outout using
tee for validation
Testing suggestions
No response
Anything else?
No response
Description
This is a sub-issue of #726.
An integration testing framework to ensure that drunc executes correctly in an SSH shell environment, with default options, and produces the expected output/state transitions. Currently, the integration tests validate the basic commands (
boot->conf->startetc.) without any options. The new integration tests in./integtest/should test the command sequence with the following parameters:etc.
Potential impact radius
Small/Isolated
Reason for change
Validate that drunc workflow works reliably on different platforms and ensure new changes don't break functionality.
Suggested implementations
./integtestdirectory to contain integration tests--integtest-ssh-shellmarker to run the teststeefor validationTesting suggestions
No response
Anything else?
No response