We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The testsuite needs lots of love, but for now, here are some steps to add a new test.
There are more than one type of test, compiled tests written in c, or shell scripts.
Also, if you take a peek at test/GNUmakefile, you will see some tests are hard-coded in there for some reason.
test/GNUmakefile
I recently added test/test-python01.sh, so you can use that one as a proper example.
test/test-python01.sh
See also: proot-me/proot#164
The text was updated successfully, but these errors were encountered:
@emilio1625 does this help any?
Sorry, something went wrong.
Hey thanks! this helps a lot
Also, per the release guide,
All shell scripts must pass shellcheck.
If you aren't familiar with shellcheck, then check it out, https://www.shellcheck.net
Also, you can run the testsuite with V=1 for verbose. That really helps, but it is very verbose..
V=1
Update writing_tests.md
54c935d
Bug: #8
oxr463
No branches or pull requests
The testsuite needs lots of love, but for now, here are some steps to add a new test.
There are more than one type of test, compiled tests written in c, or shell scripts.
Also, if you take a peek at
test/GNUmakefile
, you will see some tests are hard-coded in there for some reason.I recently added
test/test-python01.sh
, so you can use that one as a proper example.See also: proot-me/proot#164
The text was updated successfully, but these errors were encountered: