QuasarApp/qca
4
0
Fork 0
mirror of https://github.com/QuasarApp/qca.git synced 2025-05-09 09:19:33 +00:00
Code Issues Projects Releases Wiki Activity

Update the test plan to reflect the "make test" target for

Browse Source 
qconf/qmake.

svn path=/trunk/kdesupport/qca/; revision=685631
This commit is contained in:
Brad Hards 2007-07-09 10:56:41 +00:00
parent 6302b633dc
commit 6b9080fcc6
1 changed files with 9 additions and 11 deletions

20
unittest/TestPlan

@ -54,8 +54,7 @@ are installed.
Note: automated unit testing with qmake is experimental.
If using cmake, run "make test" in the build directory. If using
qmake/qconf, run "make check".
Run "make test" in the build directory.
Expected result: All (23) tests pass.
@ -64,16 +63,15 @@ Expected result: All (23) tests pass.
Additional "self checking" tests
Depending on test requirements, consider running additional unit tests
that are not in the "make test" / "make check" set. For example, to
run the unit tests for TLS Server Name Indication, run the "veloxunittest"
test application from the "unittest/velox" directory.
that are not in the "make test" set. For example, to run the unit
tests for TLS Server Name Indication, run the "veloxunittest" test
application from the "unittest/velox" directory.
Note that tests outside the "make test" / "make check" set are
potentially fragile, and should not be expected to pass in all
circumstances. Nor should the tests be expected to fail if there is a
problem. You should ensure that you understand what the test is
supposed to be checking before running the test and attempting to
interpret the results.
Note that tests outside the "make test" set are potentially fragile,
and should not be expected to pass in all circumstances. Nor should
the tests be expected to fail if there is a problem. You should ensure
that you understand what the test is supposed to be checking before
running the test and attempting to interpret the results.