Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Mention the GUI test in the unit test tech note.

Browse Source 
Update the tech note to mention the (relatively) new GUI test program too.

See #11431.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@66057 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2010-11-07 14:00:31 +00:00
parent 5fcef18409
commit 62d3301bf9
1 changed files with 9 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/tech/tn0017.txt
View File

@@ -62,7 +62,9 @@ II. Writing tests with CppUnit
event type. It disconnects again once it is out of scope. It simply reduces
the amount of typing required to count events.
3. add a '<sources>' tag for your source file to tests/test.bkl
3. add a '<sources>' tag for your source file to tests/test.bkl. Make sure it's
in the correct section: the one starting '<exe id="test_gui"' for a gui test,
the one starting '<exe id="test" template="wx_sample_console' otherwise.
III. Running the tests
@@ -76,16 +78,17 @@ III. Running the tests
2. Build the test program using one of the make/project files in the tests
subdirectory.
3. Run the test program with no arguments to run the default set of tests
(which are all those registered with CPPUNIT_TEST_SUITE_REGISTRATION).
3. Run the test program by using the command 'test' for the console tests,
'test_gui' for the gui ones. With no arguments, all the default set of tests
(all those registered with CPPUNIT_TEST_SUITE_REGISTRATION) are run.
Or to list the test suites without running them:
test -l
test -l or test_gui -l
4. Tests that have been registered under a name using
CPPUNIT_TEST_SUITE_NAMED_REGISTRATION can also be run separately. For
example:
test MBConvTestCase
or to list the tests:
test_gui ButtonTestCase
or to list the tests done by a particular testcase:
test -L MBConvTestCase
5. Fault navigation.