mutter

brl/mutter

History

Neil Roberts 51edcc5251 Added a test for non-power-of-two sized textures The test simply creates an odd sized texture with different colors at each of the four corners. It then renders the texture and verifies that the colors are the expected values. This should help ensure that the sliced texture rendering code is working properly.		2009-02-09 12:48:58 +00:00
..
conform	Added a test for non-power-of-two sized textures	2009-02-09 12:48:58 +00:00
data	Adds a CoglMaterial abstraction, which includes support for multi-texturing	2008-12-22 16:35:52 +00:00
interactive	[text] Rename :alignment to :line-alignment	2009-02-05 19:54:48 +00:00
micro-bench	[test-text] Use g_setenv instead of setenv	2009-01-23 18:20:46 +00:00
tools	Make libdisable-npots a bit more portable	2009-01-05 17:11:44 +00:00
Makefile.am	2008-11-17 Emmanuele Bassi <ebassi@linux.intel.com>	2008-11-18 09:50:03 +00:00
README

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 aproach taken for testing.