runtest cmd line args. Fixes #42 #86
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
If you decide to merge this PR, do not forget to add libargtable2-0 to the list of required packages. Also, Travis could not start compiling because aptitude failed with an error when installing libgemplugin-ruby. I guess it will fail again because libargtable is not installed. |
|
Hi, can you check if the code compiles successfully on your local machine? |
|
Sure. Sorry for the delay. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
runtest can now parse command line arguments using argtable2. It is possible to run specific test suites (eg : util + commandline) or a specific test in a specific suite (eg: "initialization" in the suite "core"). The -f parameter causes the tests to run in forked mode and --help displays the help text.
argtable2 is available in debian (I use linux mint) repository (libargtable2) so I hope that won't be a problem.
However, I could not figure out a way to run specific tests from specific suites. For example, I cannot run selectively the tests "initialization" and "varnamc" from the suites "core" and "commandline" together (I can run all the tests in both core and util together though). argtable won't let me set both suite name and test name as parameters that can take variable number of arguments.