2
1
Outline of test categories:
4
The conform/ tests should be non-interactive unit-tests that verify a single feature is behaving as documented. See conform/ADDING_NEW_TESTS for more details.
6
The micro-bench/ tests should be focused perfomance test, ideally testing a single metric. Please never forget that these tests are synthetec and if you are using them then you understand what metric is being tested. They probably don't reflect any real world application loads and the intention is that you use these tests once you have already determined the crux of your problem and need focused feedback that your changes are indeed improving matters. There is no exit status requirements for these tests, but they should give clear feedback as to their performance. If the framerate is the feedback metric, then the test should forcibly enable FPS debugging.
8
The interactive/ tests are any tests whos status can not be determined without a user looking at some visual output, or providing some manual input etc. This covers most of the original Clutter tests. Ideally some of these tests will be migrated into the conformance/ directory so they can be used in automated nightly tests.
3
The conform/ tests should be non-interactive unit-tests that verify a single
4
feature is behaving as documented. See conform/ADDING_NEW_TESTS for more
7
The micro-bench/ tests should be focused perfomance test, ideally testing a
8
single metric. Please never forget that these tests are synthetec and if you
9
are using them then you understand what metric is being tested. They probably
10
don't reflect any real world application loads and the intention is that you
11
use these tests once you have already determined the crux of your problem and
12
need focused feedback that your changes are indeed improving matters. There is
13
no exit status requirements for these tests, but they should give clear
14
feedback as to their performance. If the framerate is the feedback metric, then
15
the test should forcibly enable FPS debugging.
17
The interactive/ tests are any tests whose status can not be determined without
18
a user looking at some visual output, or providing some manual input etc. This
19
covers most of the original Clutter tests. Ideally some of these tests will be
20
migrated into the conformance/ directory so they can be used in automated
23
The data/ directory contains optional data (like images and ClutterScript
24
definitions) that can be referenced by a test.
11
All tests should ideally include a detailed description in the source explaining exactly what the test is for, how the test was designed to work, and possibly a rationale for the approach taken for testing.
28
• All tests should ideally include a detailed description in the source
29
explaining exactly what the test is for, how the test was designed to work,
30
and possibly a rationale for the approach taken for testing.
32
• When running tests under Valgrind, you should follow the instructions
35
http://live.gnome.org/Valgrind
37
and also use the suppression file available inside the data/ directory.
added
removed
tests/README
