mirror of
https://github.com/brl/mutter.git
synced 2024-12-25 04:22:05 +00:00
8d98c28dfa
* cairo-texture: [cairo-texture] Remove the construct only restriction on surface size [cairo-texture] Silently discard 0x0 surfaces Re-indent ClutterPath header Add a test case for the new cairo path functions Add clutter_path_to_cairo_path and clutter_path_add_cairo_path Warn instead of returning in the IN_PAINT check Small documentation fixes Print a warning when creating a cairo_t while painting Do not set the IN_PAINT flag inside the Stage paint Set the IN_PAINT private flag [docs] Add ClutterCairoTexture to the API reference Add ClutterCairoTexture Require Cairo as a Clutter dependency Conflicts: Fix merge conflict in clutter/clutter-path.h |
||
|---|---|---|
| .. | ||
| 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.