-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
Test Directory Documentation #5538
Comments
Trott
added
test
Issues and PRs related to the tests.
good first issue
Issues that are suitable for first-time contributors.
labels
Mar 2, 2016
4 tasks
This may be a good a time as any to talk about our debugger directory doing nothing |
Removing the |
Trott
removed
the
good first issue
Issues that are suitable for first-time contributors.
label
Mar 4, 2016
@thealphanerd Working on it, one test file at a time. #5532 |
This was fixed (at least an initial doc) by @mike182uk so I'm going to close this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
test
directory has a number of subdirectories that could use some explanation. It is probably a good idea to add aREADME
to that directory to explain what each subdirectory is and whether or not the tests in that directory get run on the continuous integration server or not. (Look at thetest-ci
task in the Makefile to find out.)I'm labeling this
good first contribution
even though a first-time contributor might not know what all the directories are. Don't worry about it, First Time Contributor! Just take your best guess after perusing the test files in each directory for a little bit and any mistakes will get sorted out in the pull request conversation.The text was updated successfully, but these errors were encountered: