| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
only for TEST-02-UNITTESTS
|
| |
|
|
|
|
|
| |
Since c6552ad we now try to collect coverage even in situations where
it's basically impossible (like in test-mount-util where the whole / is
mounted as read-only). As dealing with this is not worth the trouble,
let's ignore the missing coverage errors thrown by gcov in such cases.
|
| | |
|
| | |
|
| |
|
|
|
| |
The return code is initialized to fail if /testok is not found, but
that also covers the case where all tests are skipped.
|
| |
|
|
|
|
| |
Specifying the test number manually is tedious and prone to errors (as
recently proven). Since we have all the necessary data to work out the
test number, let's do it automagically.
|
| |
|
|
|
|
| |
The logic to query test state was rather complex. I don't quite grok the point
of ret=$((ret+1))… But afaics, the precise result was always ignored by the
caller anyway.
|
| | |
|
|
|
When tests are executed serially (the default), it seems better to launch
the fairly generic test that runs the unittests early in the sequence.
Right now the tests are ordered based on when they were written, but
this doesn't make much sense.
|
