brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
046a4b8047
mutter/tests
History
Damien Lespiau afb30f4013 tests: blend-string: use g_assert_cmpint 
It's very useful to see the actual number the reference value is
compared too when the test fails. GTest has g_assert_cmp$type()
functions for that, so make good use of them.
2010-01-26 17:25:10 +00:00
..
conform tests: blend-string: use g_assert_cmpint 2010-01-26 17:25:10 +00:00
data Remove trailing comma from test UI definition 2010-01-05 11:02:39 +00:00
interactive test-cogl-multitexture: use several materials with texture matrices 2010-01-26 16:59:50 +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 disable-npots: Don't allow the GL version to be 2.0 2009-11-18 17:28:08 +00:00
Makefile.am
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.