-
Notifications
You must be signed in to change notification settings - Fork 365
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
Meaningful names for tests #164
Comments
Shell Script Test Template #!/bin/sh
set -eu
# Check dependencies
# Create temporary directory
# Run test
# Cleanup See also: https://github.com/qemu/qemu/blob/master/tests/docker/common.rc |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See also: #96 (comment)
Many of these tests contain a valid git commit id, which can be used to reference
the functionality of the test in question.
Additionally, all shell scripts should be modified to pass
shellcheck
(See also: CII Best Practices Badge Program).Finally, old tests should simply be removed. If we really need them,
they can be found in the git history or in a previous release.
echo
to be in/usr/bin
The text was updated successfully, but these errors were encountered: