mirror of
https://github.com/brl/mutter.git
synced 2024-11-23 08:30:42 -05:00
8e437e838f
This removes a lot of code from test-cogl-primitives to make it easier to follow. The TestCoglBox custom actor has gone and instead a blank ClutterGroup is created with a paint signal handler. Instead of rendering constantly and updating when a GTimer elapses a second, a ClutterTimeline is used with 1 fps and a new redraw is queued every frame. The custom main loop is replaced with a regular call to clutter_main. This fixes the close button of the stage window so you can quit without having to press Ctrl+C. |
||
---|---|---|
.. | ||
conform | ||
data | ||
interactive | ||
micro-bench | ||
tools | ||
Makefile.am | ||
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.