[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
test suites for packages
From: |
Colin Macdonald |
Subject: |
test suites for packages |
Date: |
Wed, 15 Oct 2014 11:18:28 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 |
Hi,
Is there some "best practice" about how to actually run a test suite
driver with a package? I looked at odepkg, control, signal, image,
general.
"test_control" just runs all the tests like:
> test @lti/c2d
> test @lti/connect
> test @lti/d2c
> test @lti/d2d
which is nice but bit hard to see what is happening if you have some
"xtest". It also doesn't give a nice summary. odepkg has explicit
test files but I don't see a friendly driver function.
For OctSymPy, I hacked a copy of "__run_test_suite__.m" to run all my
tests. I'm quite happy with this output:
> @sym/uminus.m ................................... PASS 2/2
> @sym/uplus.m .................................... PASS 2/2
> @sym/vertcat.m .................................. PASS 10/10 XFAIL 2
> @sym/xor.m ...................................... PASS 5/5
> @symfun/minus.m ................................. PASS 4/4
----8<-----
> PASS 832
> FAIL 0
> XFAIL 16
> TIME 393s (347s CPU)
Unfortunately, I've noticed that it must be run from the directory
where my package is installed. Probably I can fix but I feel like I'm
hacking on something others must have thought about before.
Have I missed something?
I can has "pkg test mypkg"? ;-)
thanks,
Colin
--
Colin Macdonald
Associate Professor
Tutorial Fellow at Oriel College
University of Oxford
0xC5326EE5.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
- test suites for packages,
Colin Macdonald <=