mutter

brl/mutter

History

Neil Roberts 7fd6273c25 tests: Generate the stub scripts using sed Instead of trying to run ./test-conformance with the -l option to generate a list of available tests it now runs sed on the test-conform-main.c file instead. Running the generated executable is a pain for cross-compiling so it would be nice to avoid it unless it's absolutely necessary. Although you could tell people who are cross compiling to just disable the conformance tests, this seems a shame because they could still be useful along with the wrappers for example if the cross compile is built to a shared network folder where the tests can be run on the actual device. The sed script is a little more ugly than it could be because it tries to avoid using the GNU extensions '\+' and '\\|'. The script ends up placing restrictions on the format of the C file because the tests must all be listed on one line each. There is now a comment to explain this. Hopefully the trade off is worth it. http://bugzilla.clutter-project.org/show_bug.cgi?id=2363		2010-10-12 15:24:32 +01:00
..
accessibility	build: Autogenerate more ignore files	2010-08-14 08:43:16 +01:00
conform	tests: Generate the stub scripts using sed	2010-10-12 15:24:32 +01:00
data	test-script-parser: Add a second child to the container	2010-08-25 16:18:25 +01:00
interactive	test-flow-layout: Track stage size by default	2010-10-12 14:53:20 +01:00
micro-bench	build: Use maintainer-clean for the ignore files removal	2010-08-15 18:42:54 +01:00
tools	disable-npots: Don't allow the GL version to be 2.0	2009-11-18 17:28:08 +00:00
Makefile.am	build: Distcheck fixes after the Cally merge	2010-07-07 16:30:31 +01:00
README	Add accessibility tests	2010-07-05 16:45:43 +01:00

README

Outline of test categories:

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.

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.

The interactive/ tests are any tests whose 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.

The accessibility/ tests are tests created to test the accessibility support of
clutter, testing some of the atk interfaces.

The data/ directory contains optional data (like images and ClutterScript
definitions) that can be referenced by a test.

Other notes:

• 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.

• When running tests under Valgrind, you should follow the instructions
available here:

        http://live.gnome.org/Valgrind

and also use the suppression file available inside the data/ directory.