This repository has been archived by the owner on Nov 7, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathREADME
87 lines (63 loc) · 2.51 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
==========================
Wayland integration tests
==========================
This project aims to create small framework for simple testing
of interaction between wayland's display and client.
Directory structure:
TOP \
| src/ - WIT framework sources
| test/ - tests, including self-tests
| test-runner/ - testing framework
| benchmarks/ - folder containing benchmarks results
| tools/ - tools for manipulating with tests outcomes
Part of this code was taken from Wayland test-suite (namely test/test-runner.c,
test/test-runner.h and test/test-helpers.c). Backtrace function in test-runner.c
is from Weston.
=== Dependencies ===
Required:
wayland-server
wayland-client
Optional:
libunwind
=== Building WIT ===
Autotools requierments:
automake 1.11
autoconf 2.64
libtool 2.2
Getting WIT, compiling and running:
$ git clone https://github.com/mchalupa/wayland-integration-tests
$ cd wayland-integration-tests
$ ./autogen.sh
$ make
$ make check
When only make is run then the framework is compiled. Tests are run by make check.
=== Running WIT ===
$ make check
will compile and run all tests in test/ directory.
Selected tests can be run using
$ make check TESTS="test1 test2"
$ make check TESTS="wit-test wl_shm-test" # example
Or if tests have been compiled you can run the test without using make:
$ ./test_name
$ ./wit-test # example
To run only one test-case from test you can do
$ ./test_name test_case_name
$ ./wit-test client_populate_tst # run client_populate_tst from wit-test
=== Colored log ===
You can use tools/colorlog to colorize tests output. When no argument
to colorlog is given, it reads from stdin, otherwise it searches for
files in . or test/ directory. Also you don't have to give it full name,
because it looks for "arg".log and "arg"-test.log.
Another parameters can be pattern that it should look for and colour
of text matching the pattern (default = yellow).
Examples:
$ tools/colorlog abc-test.log # following three command will do the same
$ tools/colorlog abc-test # that is print colored output of abc-test
$ tools/colorlog abc
$ tools/colorlog abc delete_id # color even lines containing text 'delete_id'
$ tools/colorlog abc done '\033[0;31m' # color even lines containing text
# done with given color
=== Writing tests ===
See test/README
=== Authors ===
Marek Chalupa <[email protected]>