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
Test files in Packs might have a standard expected layout so can do things like:
?- pack_run_tests(some_pack,[....]).
or
?- pack_verify(some_pack,[....]).
Right now everyone uses: test/ tests/ t/ or your_mom/
test/
tests/
t/
your_mom/
Maybe a pathname or something could be added to the pack.pl file?
and/or a single file found someplace like pack_verify.plt
pack_verify.plt
And maybe a way to globally test all packs (for all packs that conform to this standard) like:
?- pack_test_all([include([pack1,pack2...]),exclude(...). ...]).
The text was updated successfully, but these errors were encountered:
That makes a lot of sense. The internal test files use these conventions:
test_*.pl
run_tests([test1, test2. ...])
Given a standard directory name, we are done in that case. That might be easier than extending pack.pl?
Sorry, something went wrong.
No branches or pull requests
Test files in Packs might have a standard expected layout so can do things like:
or
Right now everyone uses:
test/
tests/
t/
oryour_mom/
Maybe a pathname or something could be added to the pack.pl file?
and/or a single file found someplace like
pack_verify.plt
And maybe a way to globally test all packs (for all packs that conform to this standard) like:
The text was updated successfully, but these errors were encountered: