Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration Tests: Force exit of USE #32

Open
h-man2 opened this issue Apr 22, 2022 · 1 comment
Open

Integration Tests: Force exit of USE #32

h-man2 opened this issue Apr 22, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@h-man2
Copy link
Contributor

h-man2 commented Apr 22, 2022

Is your feature request related to a problem? Please describe.
When adding integration tests to the test suite so-called .in files are createt that contain commands and expected outputs. To end the tests, an explicit exit command needs to be specified at the end of the .in file. This exit is often left out resulting in a forever running integration tests suite.

Describe the solution you'd like
The intergration test ShellIT should always append an exit-command at the end of the generated command file.

Describe alternatives you've considered
Providing a warning, but this just forces a user to to stuff the testsuite can do.

@h-man2 h-man2 added the enhancement New feature or request label Apr 22, 2022
@h-man2
Copy link
Contributor Author

h-man2 commented Apr 26, 2022

While it is easy to add an exit at the end of the test in-files, if not present. A problem exists with tests that provide a invalid USE model, i. e., USE exits by itself.

One solution would be to mark this tests with a comment like #expected exit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant