2
Testing and running et tests.
4
Testing gui api/applications can be hard, but we can at least
5
test that wxerlang behaves as we expected, i.e. that the api
6
is consistent and that it don't crash.
8
The tests are structured as they are because we want you to
9
be able to run them in three different ways.
10
- direct via an erlang shell
11
- via common_test application
12
- via erlang/OTP inhouse ts tool.
14
To run all the tests compile them and on unix
15
run ./ett to create an erlang terminal.
17
Invoke ett:t(). in the erlang shell to run all regression tests.
18
If you want to specific tests invoke ett:t(Module)
19
or ett:t(Module, TestCase).
21
To run all tests including the ones that require manual intervention run.
22
ett:t(all, [{user,true}]).
24
To see every test_case window use
25
ett:t(all, [{user,step}]).
26
This requires that you manually close each window to step to the
29
If you want to run specific test_cases use:
30
ett:t({Module,TestCase}, [{user,step}]).