mutter

brl/mutter

History

Emmanuele Bassi 7d891d9dd4 tests: Allow getting data files from the tests/data directory The units under the conformance test suite should be able to use external files. Linking the files in tests/conform like the interactive tests do seems like a hack piled on top of a hack, so instead we should provide a programmatic way for a conformance test unit to get the full path of a file, regardless of where the tests/data directory is. We can use a define to get the full path of tests/data and then a function using g_build_filename() to construct the path to the file we want.		2009-11-04 11:47:09 +00:00
..
conform	tests: Allow getting data files from the tests/data directory	2009-11-04 11:47:09 +00:00
data	[build] Split out the custom silent rules	2009-09-16 17:47:59 +01:00
interactive	[test-fbo] greatly simplify the test	2009-11-04 03:34:09 +00:00
micro-bench	Intial Re-layout of the Cogl source code and introduction of a Cogl Winsys	2009-10-16 18:58:50 +01:00
tools	Intial Re-layout of the Cogl source code and introduction of a Cogl Winsys	2009-10-16 18:58:50 +01:00
.gitignore	[gitignore] Ignore new test-color-hls-roundtrip test	2009-08-03 14:25:08 +01:00
Makefile.am	2008-11-17 Emmanuele Bassi <ebassi@linux.intel.com>	2008-11-18 09:50:03 +00:00
README	[docs] Fix typos and remove mentions of SVN	2009-07-12 01:38:40 +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 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.

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.