-
Notifications
You must be signed in to change notification settings - Fork 175
TestPackage function and 'testpackage' make target #647
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
Merged
markuspf
merged 3 commits into
gap-system:stable-4.8
from
olexandr-konovalov:test-one-package
Mar 7, 2016
Merged
TestPackage function and 'testpackage' make target #647
markuspf
merged 3 commits into
gap-system:stable-4.8
from
olexandr-konovalov:test-one-package
Mar 7, 2016
Conversation
This file contains hidden or 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
Usage: make testpackage PKGNAME=<pkgname> This will run standard tests of the package <pkgname> in the same way like we run them in our regression testing (though with the user's selection of packages that may be different). It will write test output to 3 log files dev/log/testpackageX_timestamp.pkgname where X=1 with no packages, 2 with all packages and A with default packages.
Member
Author
|
Example: testing a package with .g file using 'make testpackage': |
Member
Author
|
Example: testing a package with .tst file using |
a310263 to
b830e2d
Compare
Member
|
This looks good to me. |
Member
Author
|
Thanks @markuspf. I've now added the documentation, so I think this is ready for merge. |
markuspf
added a commit
that referenced
this pull request
Mar 7, 2016
TestPackage function and 'testpackage' make target
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.
This is in response to the issue #637 by @ChrisJefferson.
This PR adds two ways of testing a GAP package.
The first is called from the shell using
This is as maximally close to the setting in which we run regression tests as possible - the difference is of course in the local version of GAP and the selection of package. Otherwise, it will run the test three times, each in a new GAP session (without/default/all packages), with assertion level 2, and will produce three log files in the dev/log directory.
The second may be called from the GAP prompt via
In this case assertion level will not be changed, and the test will run only once in the current GAP session.
I've labeled this "DO NOT MERGE" since I should also document this before merging, but I'm submitting the code to get some feedback.