isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-24 00:50:42 -05:00
Code Issues Packages Projects Releases Wiki Activity
77ec8774a0
mutter/tests/conform/test-conform-main.c

273 lines
11 KiB
C
Raw Normal View History

2008-11-18 Emmanuele Bassi <ebassi@linux.intel.com> * tests/conform/test-conform-main.c (main): Do not run the conformance test suite if we are on X11 but we do not have a DISPLAY available. Some of the tests require a DISPLAY, and everything passes through a clutter_init() call which will fail anyway. If we are running make distcheck on an headless box we might as well just skip the conformance test suite without a meaningless error.
2008-11-18 08:06:02 -05:00
#include "config.h"
Bug 1162 - Re-works the tests/ to use the glib-2.16 unit testing framework * configure.ac: * tests/*: The tests have been reorganised into different categories: conformance, interactive and micro benchmarks. - conformance tests can be run as part of automated tests - interactive tests are basically all the existing tests - micro benchmarks focus on a single performance metric I converted the timeline tests to conformance tests and also added some tests from Neil Roberts and Ebassi. Note: currently only the conformance tests use the glib test APIs, though the micro benchmarks should too. The other change is to make the unit tests link into monolithic binaries which makes the build time for unit tests considerably faster. To deal with the extra complexity this adds to debugging individual tests I have added some sugar to the makefiles so all the tests can be run directly via a symlink and when an individual test is run this way, then a note is printed to the terminal explaining exactly how that test may be debugged using GDB. There is a convenience make rule: 'make test-report', that will run all the conformance tests and hopefully even open the results in your web browser. It skips some of the slower timeline tests, but you can run those using 'make full-report'
2008-11-07 14:32:28 -05:00
#include <clutter/clutter.h>
#include <glib.h>
[tests] Abstract GTest and Clutter initialization The set up process of the conformance test suite is complex enough to warrant a split up into its own function.
2009-08-14 10:58:00 -04:00
#include <locale.h>
Bug 1162 - Re-works the tests/ to use the glib-2.16 unit testing framework * configure.ac: * tests/*: The tests have been reorganised into different categories: conformance, interactive and micro benchmarks. - conformance tests can be run as part of automated tests - interactive tests are basically all the existing tests - micro benchmarks focus on a single performance metric I converted the timeline tests to conformance tests and also added some tests from Neil Roberts and Ebassi. Note: currently only the conformance tests use the glib test APIs, though the micro benchmarks should too. The other change is to make the unit tests link into monolithic binaries which makes the build time for unit tests considerably faster. To deal with the extra complexity this adds to debugging individual tests I have added some sugar to the makefiles so all the tests can be run directly via a symlink and when an individual test is run this way, then a note is printed to the terminal explaining exactly how that test may be debugged using GDB. There is a convenience make rule: 'make test-report', that will run all the conformance tests and hopefully even open the results in your web browser. It skips some of the slower timeline tests, but you can run those using 'make full-report'
2008-11-07 14:32:28 -05:00
#include <stdlib.h>
#include "test-conform-common.h"
[tests] Add TEST_CONFORM_SKIP() macro Sometimes a test unit should not be executed depending on a condition. It would be good to have a macro doing this, along with TEST_CONFORM_SIMPLE(). Additionally, the skipped unit should be added to a specific namespace, so that any coverage report will be able to catch it. For this reason, here's TEST_CONFORM_SKIP() which follows the syntax: TEST_CONFORM_SKIP (condition, namespace, function); If condition evaluates to FALSE the test is skipped and the unit added to the "/skipped" namespace.
2009-02-14 06:41:55 -05:00
static void
test_conform_skip_test (TestConformSimpleFixture *fixture,
gconstpointer data)
{
/* void */
}
Bug 1162 - Re-works the tests/ to use the glib-2.16 unit testing framework * configure.ac: * tests/*: The tests have been reorganised into different categories: conformance, interactive and micro benchmarks. - conformance tests can be run as part of automated tests - interactive tests are basically all the existing tests - micro benchmarks focus on a single performance metric I converted the timeline tests to conformance tests and also added some tests from Neil Roberts and Ebassi. Note: currently only the conformance tests use the glib test APIs, though the micro benchmarks should too. The other change is to make the unit tests link into monolithic binaries which makes the build time for unit tests considerably faster. To deal with the extra complexity this adds to debugging individual tests I have added some sugar to the makefiles so all the tests can be run directly via a symlink and when an individual test is run this way, then a note is printed to the terminal explaining exactly how that test may be debugged using GDB. There is a convenience make rule: 'make test-report', that will run all the conformance tests and hopefully even open the results in your web browser. It skips some of the slower timeline tests, but you can run those using 'make full-report'
2008-11-07 14:32:28 -05:00
conform: Implement TEST_CONFORM_TODO() correctly The TODO() macro for adding new tests to the test suite has always meant to be implemented like the TODO block in Test::More, i.e. a test that is assumed to fail, and which warns if it unexpectedly succeeds. Since GTest lacks the expressivity of Test::More, the implementation just verifies that the tests marked as TODO actually fail, and will fail if they happen to succeed - at which point the developer will have to change the macro to SIMPLE or SKIP.
2010-10-12 12:11:52 -04:00
static void
test_conform_todo_test (TestConformSimpleFixture *fixture,
gconstpointer data)
{
#ifdef G_OS_UNIX
const TestConformTodo *todo = data;
if (g_test_trap_fork (0, G_TEST_TRAP_SILENCE_STDOUT | G_TEST_TRAP_SILENCE_STDERR))
{
todo->func (fixture, NULL);
exit (0);
}
g_test_trap_assert_failed ();
#endif
}
conform: Start cleaning up the conformance test suite Re-order the units into a sensible list, with basic tests at the beginning, and per-class tests at the end - with Cogl last. Also, start renaming the unit functions from test_<foo> to <foo>, so that the executable wrappers and the reports have sensible names.
2010-10-12 12:31:15 -04:00
void
verify_failure (TestConformSimpleFixture *fixture,
gconstpointer data)
{
g_assert (FALSE);
}
[tests] Abstract GTest and Clutter initialization The set up process of the conformance test suite is complex enough to warrant a split up into its own function.
2009-08-14 10:58:00 -04:00
static TestConformSharedState *shared_state = NULL;
Bug 1162 - Re-works the tests/ to use the glib-2.16 unit testing framework * configure.ac: * tests/*: The tests have been reorganised into different categories: conformance, interactive and micro benchmarks. - conformance tests can be run as part of automated tests - interactive tests are basically all the existing tests - micro benchmarks focus on a single performance metric I converted the timeline tests to conformance tests and also added some tests from Neil Roberts and Ebassi. Note: currently only the conformance tests use the glib test APIs, though the micro benchmarks should too. The other change is to make the unit tests link into monolithic binaries which makes the build time for unit tests considerably faster. To deal with the extra complexity this adds to debugging individual tests I have added some sugar to the makefiles so all the tests can be run directly via a symlink and when an individual test is run this way, then a note is printed to the terminal explaining exactly how that test may be debugged using GDB. There is a convenience make rule: 'make test-report', that will run all the conformance tests and hopefully even open the results in your web browser. It skips some of the slower timeline tests, but you can run those using 'make full-report'
2008-11-07 14:32:28 -05:00
/* This is a bit of sugar for adding new conformance tests:
*
* - It adds an extern function definition just to save maintaining a header
* that lists test entry points.
* - It sets up callbacks for a fixture, which lets us share initialization
* *code* between tests. (see test-conform-common.c)
* - It passes in a shared *data* pointer that is initialised once in main(),
* that gets passed to the fixture setup and test functions. (See the
* definition in test-conform-common.h)
*/
[tests] Add TEST_CONFORM_SKIP() macro Sometimes a test unit should not be executed depending on a condition. It would be good to have a macro doing this, along with TEST_CONFORM_SIMPLE(). Additionally, the skipped unit should be added to a specific namespace, so that any coverage report will be able to catch it. For this reason, here's TEST_CONFORM_SKIP() which follows the syntax: TEST_CONFORM_SKIP (condition, namespace, function); If condition evaluates to FALSE the test is skipped and the unit added to the "/skipped" namespace.
2009-02-14 06:41:55 -05:00
#define TEST_CONFORM_SIMPLE(NAMESPACE, FUNC) G_STMT_START { \
conform: Start cleaning up the conformance test suite Re-order the units into a sensible list, with basic tests at the beginning, and per-class tests at the end - with Cogl last. Also, start renaming the unit functions from test_<foo> to <foo>, so that the executable wrappers and the reports have sensible names.
2010-10-12 12:31:15 -04:00
extern void FUNC (TestConformSimpleFixture *, gconstpointer); \
g_test_add ("/conform" NAMESPACE "/" #FUNC, \
TestConformSimpleFixture, \
shared_state, /* data argument for test */ \
test_conform_simple_fixture_setup, \
FUNC, \
[tests] Add TEST_CONFORM_SKIP() macro Sometimes a test unit should not be executed depending on a condition. It would be good to have a macro doing this, along with TEST_CONFORM_SIMPLE(). Additionally, the skipped unit should be added to a specific namespace, so that any coverage report will be able to catch it. For this reason, here's TEST_CONFORM_SKIP() which follows the syntax: TEST_CONFORM_SKIP (condition, namespace, function); If condition evaluates to FALSE the test is skipped and the unit added to the "/skipped" namespace.
2009-02-14 06:41:55 -05:00
test_conform_simple_fixture_teardown); } G_STMT_END
Bug 1162 - Re-works the tests/ to use the glib-2.16 unit testing framework * configure.ac: * tests/*: The tests have been reorganised into different categories: conformance, interactive and micro benchmarks. - conformance tests can be run as part of automated tests - interactive tests are basically all the existing tests - micro benchmarks focus on a single performance metric I converted the timeline tests to conformance tests and also added some tests from Neil Roberts and Ebassi. Note: currently only the conformance tests use the glib test APIs, though the micro benchmarks should too. The other change is to make the unit tests link into monolithic binaries which makes the build time for unit tests considerably faster. To deal with the extra complexity this adds to debugging individual tests I have added some sugar to the makefiles so all the tests can be run directly via a symlink and when an individual test is run this way, then a note is printed to the terminal explaining exactly how that test may be debugged using GDB. There is a convenience make rule: 'make test-report', that will run all the conformance tests and hopefully even open the results in your web browser. It skips some of the slower timeline tests, but you can run those using 'make full-report'
2008-11-07 14:32:28 -05:00
[tests] Add TEST_CONFORM_SKIP() macro Sometimes a test unit should not be executed depending on a condition. It would be good to have a macro doing this, along with TEST_CONFORM_SIMPLE(). Additionally, the skipped unit should be added to a specific namespace, so that any coverage report will be able to catch it. For this reason, here's TEST_CONFORM_SKIP() which follows the syntax: TEST_CONFORM_SKIP (condition, namespace, function); If condition evaluates to FALSE the test is skipped and the unit added to the "/skipped" namespace.
2009-02-14 06:41:55 -05:00
/* this is a macro that conditionally executes a test if CONDITION
* evaluates to TRUE; otherwise, it will put the test under the
conform: Clean up test names Drop the 'test-' prefix: it's the conformance test suite, we know it's full of tests.
2012-02-27 07:54:23 -05:00
* "/skipped" namespace and execute a dummy function that will always
[tests] Add TEST_CONFORM_SKIP() macro Sometimes a test unit should not be executed depending on a condition. It would be good to have a macro doing this, along with TEST_CONFORM_SIMPLE(). Additionally, the skipped unit should be added to a specific namespace, so that any coverage report will be able to catch it. For this reason, here's TEST_CONFORM_SKIP() which follows the syntax: TEST_CONFORM_SKIP (condition, namespace, function); If condition evaluates to FALSE the test is skipped and the unit added to the "/skipped" namespace.
2009-02-14 06:41:55 -05:00
* pass.
*/
#define TEST_CONFORM_SKIP(CONDITION, NAMESPACE, FUNC) G_STMT_START { \
conform: Clean up test names Drop the 'test-' prefix: it's the conformance test suite, we know it's full of tests.
2012-02-27 07:54:23 -05:00
if (CONDITION) { TEST_CONFORM_SIMPLE (NAMESPACE, FUNC); } \
else { \
[tests] Add TEST_CONFORM_SKIP() macro Sometimes a test unit should not be executed depending on a condition. It would be good to have a macro doing this, along with TEST_CONFORM_SIMPLE(). Additionally, the skipped unit should be added to a specific namespace, so that any coverage report will be able to catch it. For this reason, here's TEST_CONFORM_SKIP() which follows the syntax: TEST_CONFORM_SKIP (condition, namespace, function); If condition evaluates to FALSE the test is skipped and the unit added to the "/skipped" namespace.
2009-02-14 06:41:55 -05:00
g_test_add ("/skipped" NAMESPACE "/" #FUNC, \
TestConformSimpleFixture, \
shared_state, /* data argument for test */ \
test_conform_simple_fixture_setup, \
test_conform_skip_test, \
test_conform_simple_fixture_teardown); \
conform: Clean up test names Drop the 'test-' prefix: it's the conformance test suite, we know it's full of tests.
2012-02-27 07:54:23 -05:00
} } G_STMT_END
Bug 1162 - Re-works the tests/ to use the glib-2.16 unit testing framework * configure.ac: * tests/*: The tests have been reorganised into different categories: conformance, interactive and micro benchmarks. - conformance tests can be run as part of automated tests - interactive tests are basically all the existing tests - micro benchmarks focus on a single performance metric I converted the timeline tests to conformance tests and also added some tests from Neil Roberts and Ebassi. Note: currently only the conformance tests use the glib test APIs, though the micro benchmarks should too. The other change is to make the unit tests link into monolithic binaries which makes the build time for unit tests considerably faster. To deal with the extra complexity this adds to debugging individual tests I have added some sugar to the makefiles so all the tests can be run directly via a symlink and when an individual test is run this way, then a note is printed to the terminal explaining exactly how that test may be debugged using GDB. There is a convenience make rule: 'make test-report', that will run all the conformance tests and hopefully even open the results in your web browser. It skips some of the slower timeline tests, but you can run those using 'make full-report'
2008-11-07 14:32:28 -05:00
[tests] Add TEST_CONFORM_TODO macro The TEST_CONFORM_TODO macro is a simple placeholder macro that adds the test function to the "/todo" namespace and skips the test. It can be used for tests that are known to fail because of bugs that haven't been fixed yet, or because of features not yet implemented.
2009-02-19 11:51:37 -05:00
#define TEST_CONFORM_TODO(NAMESPACE, FUNC) G_STMT_START { \
conform: Implement TEST_CONFORM_TODO() correctly The TODO() macro for adding new tests to the test suite has always meant to be implemented like the TODO block in Test::More, i.e. a test that is assumed to fail, and which warns if it unexpectedly succeeds. Since GTest lacks the expressivity of Test::More, the implementation just verifies that the tests marked as TODO actually fail, and will fail if they happen to succeed - at which point the developer will have to change the macro to SIMPLE or SKIP.
2010-10-12 12:11:52 -04:00
extern void FUNC (TestConformSimpleFixture *, gconstpointer); \
TestConformTodo *_clos = g_new0 (TestConformTodo, 1); \
_clos->name = g_strdup ( #FUNC ); \
_clos->func = FUNC; \
g_test_add ("/todo" NAMESPACE "/" #FUNC, \
[tests] Add TEST_CONFORM_TODO macro The TEST_CONFORM_TODO macro is a simple placeholder macro that adds the test function to the "/todo" namespace and skips the test. It can be used for tests that are known to fail because of bugs that haven't been fixed yet, or because of features not yet implemented.
2009-02-19 11:51:37 -05:00
TestConformSimpleFixture, \
conform: Implement TEST_CONFORM_TODO() correctly The TODO() macro for adding new tests to the test suite has always meant to be implemented like the TODO block in Test::More, i.e. a test that is assumed to fail, and which warns if it unexpectedly succeeds. Since GTest lacks the expressivity of Test::More, the implementation just verifies that the tests marked as TODO actually fail, and will fail if they happen to succeed - at which point the developer will have to change the macro to SIMPLE or SKIP.
2010-10-12 12:11:52 -04:00
_clos, \
[tests] Add TEST_CONFORM_TODO macro The TEST_CONFORM_TODO macro is a simple placeholder macro that adds the test function to the "/todo" namespace and skips the test. It can be used for tests that are known to fail because of bugs that haven't been fixed yet, or because of features not yet implemented.
2009-02-19 11:51:37 -05:00
test_conform_simple_fixture_setup, \
conform: Implement TEST_CONFORM_TODO() correctly The TODO() macro for adding new tests to the test suite has always meant to be implemented like the TODO block in Test::More, i.e. a test that is assumed to fail, and which warns if it unexpectedly succeeds. Since GTest lacks the expressivity of Test::More, the implementation just verifies that the tests marked as TODO actually fail, and will fail if they happen to succeed - at which point the developer will have to change the macro to SIMPLE or SKIP.
2010-10-12 12:11:52 -04:00
test_conform_todo_test, \
[tests] Add TEST_CONFORM_TODO macro The TEST_CONFORM_TODO macro is a simple placeholder macro that adds the test function to the "/todo" namespace and skips the test. It can be used for tests that are known to fail because of bugs that haven't been fixed yet, or because of features not yet implemented.
2009-02-19 11:51:37 -05:00
test_conform_simple_fixture_teardown); } G_STMT_END
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 06:47:09 -05:00
gchar *
clutter_test_get_data_file (const gchar *filename)
{
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
return g_build_filename (TESTS_DATADIR, filename, NULL);
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 06:47:09 -05:00
}
[tests] Abstract GTest and Clutter initialization The set up process of the conformance test suite is complex enough to warrant a split up into its own function.
2009-08-14 10:58:00 -04:00
static void
clutter_test_init (gint *argc,
gchar ***argv)
Bug 1162 - Re-works the tests/ to use the glib-2.16 unit testing framework * configure.ac: * tests/*: The tests have been reorganised into different categories: conformance, interactive and micro benchmarks. - conformance tests can be run as part of automated tests - interactive tests are basically all the existing tests - micro benchmarks focus on a single performance metric I converted the timeline tests to conformance tests and also added some tests from Neil Roberts and Ebassi. Note: currently only the conformance tests use the glib test APIs, though the micro benchmarks should too. The other change is to make the unit tests link into monolithic binaries which makes the build time for unit tests considerably faster. To deal with the extra complexity this adds to debugging individual tests I have added some sugar to the makefiles so all the tests can be run directly via a symlink and when an individual test is run this way, then a note is printed to the terminal explaining exactly how that test may be debugged using GDB. There is a convenience make rule: 'make test-report', that will run all the conformance tests and hopefully even open the results in your web browser. It skips some of the slower timeline tests, but you can run those using 'make full-report'
2008-11-07 14:32:28 -05:00
{
Remove useless manual timeline ticking The master clock now works fine whether or not there are any stages, so in the timeline conformance tests don't need to set up their own times. Set CLUTTER_VBLANK=none for the conformance tests, which in addition to removing an test-environment dependency, will result in the ticking for timeline tests being throttled to the default frame rate. http://bugzilla.openedhand.com/show_bug.cgi?id=1637 Signed-off-by: Emmanuele Bassi <ebassi@linux.intel.com>
2009-06-08 13:13:18 -04:00
/* Turning of sync-to-vblank removes a dependency on the specifics of the
* test environment. It also means that the timeline-only tests are
* throttled to a reasonable frame rate rather than running in tight
* infinite loop.
*/
g_setenv ("CLUTTER_VBLANK", "none", FALSE);
[tests] Abstract GTest and Clutter initialization The set up process of the conformance test suite is complex enough to warrant a split up into its own function.
2009-08-14 10:58:00 -04:00
g_test_init (argc, argv, NULL);
Renames the mesh api to the "vertex buffer api". This better reflects the fact that the api manages sets of vertex attributes, and the attributes really have no implied form. It is only when you use the attributes to draw that they become mesh like; when you specify how they should be interpreted, e.g. as triangle lists or fans etc. This rename frees up the term "mesh", which can later be applied to a concept slightly more fitting. E.g. at some point it would be nice to have a higher level abstraction that sits on top of cogl vertex buffers that adds the concept of faces. (Somthing like Blender's mesh objects.) There have also been some discussions over particle engines, and these can be defined in terms of emitter faces; so some other kind of mesh abstraction might be usefull here.
2009-01-20 16:12:44 -05:00
conform: Clean up test names Drop the 'test-' prefix: it's the conformance test suite, we know it's full of tests.
2012-02-27 07:54:23 -05:00
g_test_bug_base ("http://bugzilla.gnome.org/show_bug.cgi?id=%s");
Bug 1162 - Re-works the tests/ to use the glib-2.16 unit testing framework * configure.ac: * tests/*: The tests have been reorganised into different categories: conformance, interactive and micro benchmarks. - conformance tests can be run as part of automated tests - interactive tests are basically all the existing tests - micro benchmarks focus on a single performance metric I converted the timeline tests to conformance tests and also added some tests from Neil Roberts and Ebassi. Note: currently only the conformance tests use the glib test APIs, though the micro benchmarks should too. The other change is to make the unit tests link into monolithic binaries which makes the build time for unit tests considerably faster. To deal with the extra complexity this adds to debugging individual tests I have added some sugar to the makefiles so all the tests can be run directly via a symlink and when an individual test is run this way, then a note is printed to the terminal explaining exactly how that test may be debugged using GDB. There is a convenience make rule: 'make test-report', that will run all the conformance tests and hopefully even open the results in your web browser. It skips some of the slower timeline tests, but you can run those using 'make full-report'
2008-11-07 14:32:28 -05:00
/* Initialise the state you need to share with everything.
*/
[tests] Abstract GTest and Clutter initialization The set up process of the conformance test suite is complex enough to warrant a split up into its own function.
2009-08-14 10:58:00 -04:00
shared_state = g_new0 (TestConformSharedState, 1);
shared_state->argc_addr = argc;
shared_state->argv_addr = argv;
}
int
main (int argc, char **argv)
{
clutter_test_init (&argc, &argv);
[test-conformance] we were calling clutter_init with un-initialized arguments This ensure we initialize shared_state->arg{c,v}_addr before calling clutter_init
2009-05-22 11:59:14 -04:00
tests: Generate the stub scripts using sed Instead of trying to run ./test-conformance with the -l option to generate a list of available tests it now runs sed on the test-conform-main.c file instead. Running the generated executable is a pain for cross-compiling so it would be nice to avoid it unless it's absolutely necessary. Although you could tell people who are cross compiling to just disable the conformance tests, this seems a shame because they could still be useful along with the wrappers for example if the cross compile is built to a shared network folder where the tests can be run on the actual device. The sed script is a little more ugly than it could be because it tries to avoid using the GNU extensions '\+' and '\|'. The script ends up placing restrictions on the format of the C file because the tests must all be listed on one line each. There is now a comment to explain this. Hopefully the trade off is worth it. http://bugzilla.clutter-project.org/show_bug.cgi?id=2363
2010-10-11 11:16:45 -04:00
/* This file is run through a sed script during the make step so the
lines containing the tests need to be formatted on a single line
each. To comment out a test use the SKIP or TODO macros. Using
#if 0 would break the script. */
conform: Start cleaning up the conformance test suite Re-order the units into a sensible list, with basic tests at the beginning, and per-class tests at the end - with Cogl last. Also, start renaming the unit functions from test_<foo> to <foo>, so that the executable wrappers and the reports have sensible names.
2010-10-12 12:31:15 -04:00
/* sanity check for the test suite itself */
conform: Implement TEST_CONFORM_TODO() correctly The TODO() macro for adding new tests to the test suite has always meant to be implemented like the TODO block in Test::More, i.e. a test that is assumed to fail, and which warns if it unexpectedly succeeds. Since GTest lacks the expressivity of Test::More, the implementation just verifies that the tests marked as TODO actually fail, and will fail if they happen to succeed - at which point the developer will have to change the macro to SIMPLE or SKIP.
2010-10-12 12:11:52 -04:00
TEST_CONFORM_TODO ("/suite", verify_failure);
conform: Add a suite for the Actor scene graph API Verify that insertion and removal maintain a stable graph, with pointers to the various children. This should help out tracking regressions in the scene graph API.
2011-12-18 15:59:07 -05:00
TEST_CONFORM_SIMPLE ("/actor", actor_add_child);
TEST_CONFORM_SIMPLE ("/actor", actor_insert_child);
conform/actor-graph: Add lower/raise units Check that the lower_bottom(), lower(), raise(), and raise_top() methods work as intended.
2011-12-18 16:09:44 -05:00
TEST_CONFORM_SIMPLE ("/actor", actor_raise_child);
TEST_CONFORM_SIMPLE ("/actor", actor_lower_child);
actor: Provide a proper implementation of replace_child() The correct sequence of actions should be remove(old) → insert(new), not insert(new) → remove(old). We can implement a simple delegate insertion functions to insert the new child between the previous and next siblings of the old child. While we're at it, let's also add a unit test for replace_child().
2011-12-19 09:37:42 -05:00
TEST_CONFORM_SIMPLE ("/actor", actor_replace_child);
actor: Add remove_all_children() A simple method for removing all children of an actor in one fell swoop.
2011-12-19 13:01:04 -05:00
TEST_CONFORM_SIMPLE ("/actor", actor_remove_child);
TEST_CONFORM_SIMPLE ("/actor", actor_remove_all);
conform/actor: Add unit for the Container signals ClutterActor should be emitting signals defined on the ClutterContainer interface, as well as ensuring that manipulating the scene graph is still possible from within them. The new unit checks that we're emitting signals, by implementing something similar to the Bin class available in toolkits like gtk, st, and mx — i.e. a container that can only hold one child at any given point.
2012-02-09 11:44:28 -05:00
TEST_CONFORM_SIMPLE ("/actor", actor_container_signals);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
TEST_CONFORM_SIMPLE ("/actor", actor_destruction);
TEST_CONFORM_SIMPLE ("/actor", actor_anchors);
TEST_CONFORM_SIMPLE ("/actor", actor_pick);
conform: Start cleaning up the conformance test suite Re-order the units into a sensible list, with basic tests at the beginning, and per-class tests at the end - with Cogl last. Also, start renaming the unit functions from test_<foo> to <foo>, so that the executable wrappers and the reports have sensible names.
2010-10-12 12:31:15 -04:00
TEST_CONFORM_SIMPLE ("/actor", actor_fixed_size);
TEST_CONFORM_SIMPLE ("/actor", actor_preferred_size);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
TEST_CONFORM_SIMPLE ("/actor", actor_basic_layout);
TEST_CONFORM_SIMPLE ("/actor", actor_margin_layout);
TEST_CONFORM_SIMPLE ("/actor", actor_offscreen_redirect);
TEST_CONFORM_SIMPLE ("/actor", actor_shader_effect);
Bug 1162 - Re-works the tests/ to use the glib-2.16 unit testing framework * configure.ac: * tests/*: The tests have been reorganised into different categories: conformance, interactive and micro benchmarks. - conformance tests can be run as part of automated tests - interactive tests are basically all the existing tests - micro benchmarks focus on a single performance metric I converted the timeline tests to conformance tests and also added some tests from Neil Roberts and Ebassi. Note: currently only the conformance tests use the glib test APIs, though the micro benchmarks should too. The other change is to make the unit tests link into monolithic binaries which makes the build time for unit tests considerably faster. To deal with the extra complexity this adds to debugging individual tests I have added some sugar to the makefiles so all the tests can be run directly via a symlink and when an individual test is run this way, then a note is printed to the terminal explaining exactly how that test may be debugged using GDB. There is a convenience make rule: 'make test-report', that will run all the conformance tests and hopefully even open the results in your web browser. It skips some of the slower timeline tests, but you can run those using 'make full-report'
2008-11-07 14:32:28 -05:00
actor: Add ClutterActorIter Iterating over children and ancestors of an actor is a relatively common operation. Currently, you only have one option: start a for() loop, get the first child of the actor, and advance to the next sibling for the list of children; or start a for() loop and advance to the parent of the actor. These operations can be easily done through the ClutterActor API, but they all require going through the public API, and performing multiple type checks on the arguments. Along with the DOM API, it would be nice to have an ancillary, utility API that uses an iterator structure to hold the state, and can be advanced in a loop. https://bugzilla.gnome.org/show_bug.cgi?id=668669
2012-01-25 10:27:57 -05:00
TEST_CONFORM_SIMPLE ("/actor/iter", actor_iter_traverse_children);
TEST_CONFORM_SIMPLE ("/actor/iter", actor_iter_traverse_remove);
conform: Check that iterators work post-assignment It should be possible to copy a ClutterActorIter just by copying its contents (either via assignment or memcpy).
2012-06-27 07:44:22 -04:00
TEST_CONFORM_SIMPLE ("/actor/iter", actor_iter_assignment);
actor: Add ClutterActorIter Iterating over children and ancestors of an actor is a relatively common operation. Currently, you only have one option: start a for() loop, get the first child of the actor, and advance to the next sibling for the list of children; or start a for() loop and advance to the parent of the actor. These operations can be easily done through the ClutterActor API, but they all require going through the public API, and performing multiple type checks on the arguments. Along with the DOM API, it would be nice to have an ancillary, utility API that uses an iterator structure to hold the state, and can be advanced in a loop. https://bugzilla.gnome.org/show_bug.cgi?id=668669
2012-01-25 10:27:57 -05:00
conform/invariants: Clean up Use modern API, and add a minimal check that hiding an actor will cause it to unmap.
2012-02-15 08:43:15 -05:00
TEST_CONFORM_SIMPLE ("/actor/invariants", actor_initial_state);
TEST_CONFORM_SIMPLE ("/actor/invariants", actor_shown_not_parented);
conformance/invariants: Test that visibility is not recursive The show and hide methods should not recurse; that is the job of show_all and hide_all, which are deprecated.
2012-03-05 12:45:23 -05:00
TEST_CONFORM_SIMPLE ("/actor/invariants", actor_visibility_not_recursive);
conform/invariants: Clean up Use modern API, and add a minimal check that hiding an actor will cause it to unmap.
2012-02-15 08:43:15 -05:00
TEST_CONFORM_SIMPLE ("/actor/invariants", actor_realized);
TEST_CONFORM_SIMPLE ("/actor/invariants", actor_realize_not_recursive);
TEST_CONFORM_SIMPLE ("/actor/invariants", actor_map_recursive);
TEST_CONFORM_SIMPLE ("/actor/invariants", actor_mapped);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
TEST_CONFORM_SIMPLE ("/actor/invariants", actor_show_on_set_parent);
conform/invariants: Clean up Use modern API, and add a minimal check that hiding an actor will cause it to unmap.
2012-02-15 08:43:15 -05:00
TEST_CONFORM_SIMPLE ("/actor/invariants", clone_no_map);
TEST_CONFORM_SIMPLE ("/actor/invariants", actor_contains);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
TEST_CONFORM_SIMPLE ("/actor/invariants", default_stage);
actor: rollback pivot translation even on explicit transforms When setting an explicit transform with clutter_actor_set_transform() and a non (0,0) pivot-point, clutter_actor_apply_transform() will fail to roll back the pivot-point translation done before multiplying the transformation matrix due to the "out:" label being slightly misplaced in clutter_actor_real_apply_transform(). This works properly: clutter_actor_set_pivot_point (actor, 0.5, 0.5); clutter_actor_set_rotation_angle (actor, CLUTTER_Z_AXIS, 30); This results in the actor being moved to the pivot-point position: clutter_actor_set_pivot_point (actor, 0.5, 0.5); clutter_matrix_init_identity(&matrix); cogl_matrix_rotate (&matrix, 30, 0, 0, 1.0); clutter_actor_set_transform (actor, &matrix); This also add a conformance test checking that even when using a pivot-point, no matter how a rotation is set the resulting transformation matrix will be the same. https://bugzilla.gnome.org/show_bug.cgi?id=690214
2012-12-14 12:05:26 -05:00
TEST_CONFORM_SIMPLE ("/actor/invariants", actor_pivot_transformation);
actor: Add ClutterActorIter Iterating over children and ancestors of an actor is a relatively common operation. Currently, you only have one option: start a for() loop, get the first child of the actor, and advance to the next sibling for the list of children; or start a for() loop and advance to the parent of the actor. These operations can be easily done through the ClutterActor API, but they all require going through the public API, and performing multiple type checks on the arguments. Along with the DOM API, it would be nice to have an ancillary, utility API that uses an iterator structure to hold the state, and can be advanced in a loop. https://bugzilla.gnome.org/show_bug.cgi?id=668669
2012-01-25 10:27:57 -05:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
TEST_CONFORM_SIMPLE ("/actor/opacity", opacity_label);
TEST_CONFORM_SIMPLE ("/actor/opacity", opacity_rectangle);
TEST_CONFORM_SIMPLE ("/actor/opacity", opacity_paint);
conform: Start cleaning up the conformance test suite Re-order the units into a sensible list, with basic tests at the beginning, and per-class tests at the end - with Cogl last. Also, start renaming the unit functions from test_<foo> to <foo>, so that the executable wrappers and the reports have sensible names.
2010-10-12 12:31:15 -04:00
TEST_CONFORM_SIMPLE ("/text", text_utf8_validation);
TEST_CONFORM_SIMPLE ("/text", text_set_empty);
TEST_CONFORM_SIMPLE ("/text", text_set_text);
TEST_CONFORM_SIMPLE ("/text", text_append_some);
TEST_CONFORM_SIMPLE ("/text", text_prepend_some);
TEST_CONFORM_SIMPLE ("/text", text_insert);
TEST_CONFORM_SIMPLE ("/text", text_delete_chars);
TEST_CONFORM_SIMPLE ("/text", text_delete_text);
TEST_CONFORM_SIMPLE ("/text", text_cursor);
TEST_CONFORM_SIMPLE ("/text", text_event);
TEST_CONFORM_SIMPLE ("/text", text_get_chars);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
TEST_CONFORM_SIMPLE ("/text", text_cache);
conform: Start cleaning up the conformance test suite Re-order the units into a sensible list, with basic tests at the beginning, and per-class tests at the end - with Cogl last. Also, start renaming the unit functions from test_<foo> to <foo>, so that the executable wrappers and the reports have sensible names.
2010-10-12 12:31:15 -04:00
TEST_CONFORM_SIMPLE ("/text", text_password_char);
conform: Clean up test names Drop the 'test-' prefix: it's the conformance test suite, we know it's full of tests.
2012-02-27 07:54:23 -05:00
TEST_CONFORM_SIMPLE ("/text", text_idempotent_use_markup);
conform: Start cleaning up the conformance test suite Re-order the units into a sensible list, with basic tests at the beginning, and per-class tests at the end - with Cogl last. Also, start renaming the unit functions from test_<foo> to <foo>, so that the executable wrappers and the reports have sensible names.
2010-10-12 12:31:15 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
TEST_CONFORM_SIMPLE ("/rectangle", rectangle_set_size);
TEST_CONFORM_SIMPLE ("/rectangle", rectangle_set_color);
TEST_CONFORM_SIMPLE ("/texture", texture_pick_with_alpha);
TEST_CONFORM_SIMPLE ("/texture", texture_fbo);
TEST_CONFORM_SIMPLE ("/texture/cairo", texture_cairo);
conform: Initial suite for ClutterInterval ClutterInterval is undertested, so we should start adding a unit test for it.
2012-06-18 12:51:48 -04:00
TEST_CONFORM_SIMPLE ("/interval", interval_initial_state);
conform/interval: Add transformation unit test Verify that it's possible to pass a transformable type to ClutterInterval.
2012-06-18 13:04:10 -04:00
TEST_CONFORM_SIMPLE ("/interval", interval_transform);
conform: Initial suite for ClutterInterval ClutterInterval is undertested, so we should start adding a unit test for it.
2012-06-18 12:51:48 -04:00
conformance: Clean up Remove the last inconsistent bits.
2012-02-27 08:08:31 -05:00
TEST_CONFORM_SIMPLE ("/path", path_base);
Bug 1252 - Merge ClutterBehaviourPath and ClutterBehaviourBspline * clutter/clutter-path.h: * clutter/clutter-path.c: Implementation of new ClutterPath object to represent a path combining straight line and bezier curve elements. * clutter/clutter.h: Include clutter-path.h and remove clutter-behaviour-bspline.h * tests/interactive/test-threads.c (test_threads_main): * tests/interactive/test-script.c: * tests/interactive/test-behave.c (test_behave_main): Use new path API * clutter/clutter-effect.c: Use the new ClutterBehaviourPath API. * clutter/clutter-bezier.h: * clutter/clutter-bezier.c: Moved bezier curve handling code out from clutter-behaviour-bspline.c to a separate file. * clutter/clutter-behaviour-path.h: * clutter/clutter-behaviour-path.c: Reimplemented to work with a ClutterPath * clutter/clutter-behaviour-bspline.h: * clutter/clutter-behaviour-bspline.c: Removed * clutter/Makefile.am: Add clutter-path and clutter-bezier, remove clutter-behaviour-bspline. * tests/conform/test-path.c: New automatic test for ClutterPath consistency * tests/conform/test-conform-main.c (main): Add test_path * tests/conform/Makefile.am (test_conformance_SOURCES): Add test-path.c * clutter/clutter-sections.txt: Add ClutterPath docs * clutter/clutter.types: * clutter/clutter-docs.xml: * doc/reference/clutter/clutter-animation-tutorial.xml: Remove mention of ClutterBehaviourBspline * clutter/clutter-marshal.list: Add VOID:UINT
2008-12-05 08:13:37 -05:00
conform: Clean up test names Drop the 'test-' prefix: it's the conformance test suite, we know it's full of tests.
2012-02-27 07:54:23 -05:00
TEST_CONFORM_SIMPLE ("/binding-pool", binding_pool);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
TEST_CONFORM_SIMPLE ("/model", list_model_populate);
TEST_CONFORM_SIMPLE ("/model", list_model_iterate);
TEST_CONFORM_SIMPLE ("/model", list_model_filter);
TEST_CONFORM_SIMPLE ("/model", list_model_from_script);
TEST_CONFORM_SIMPLE ("/model", list_model_row_changed);
conform: Clean up test names Drop the 'test-' prefix: it's the conformance test suite, we know it's full of tests.
2012-02-27 07:54:23 -05:00
TEST_CONFORM_SIMPLE ("/color", color_from_string_valid);
TEST_CONFORM_SIMPLE ("/color", color_from_string_invalid);
TEST_CONFORM_SIMPLE ("/color", color_to_string);
TEST_CONFORM_SIMPLE ("/color", color_hls_roundtrip);
TEST_CONFORM_SIMPLE ("/color", color_operators);
TEST_CONFORM_SIMPLE ("/units", units_constructors);
TEST_CONFORM_SIMPLE ("/units", units_string);
TEST_CONFORM_SIMPLE ("/units", units_cache);
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
TEST_CONFORM_SIMPLE ("/group", group_depth_sorting);
TEST_CONFORM_SIMPLE ("/script", script_single);
TEST_CONFORM_SIMPLE ("/script", script_child);
TEST_CONFORM_SIMPLE ("/script", script_implicit_alpha);
TEST_CONFORM_SIMPLE ("/script", script_object_property);
TEST_CONFORM_SIMPLE ("/script", script_animation);
TEST_CONFORM_SIMPLE ("/script", script_named_object);
TEST_CONFORM_SIMPLE ("/script", script_layout_property);
TEST_CONFORM_SIMPLE ("/script", animator_base);
TEST_CONFORM_SIMPLE ("/script", animator_properties);
TEST_CONFORM_SIMPLE ("/script", animator_multi_properties);
TEST_CONFORM_SIMPLE ("/script", state_base);
TEST_CONFORM_SIMPLE ("/script", script_margin);
conform: Clean up test names Drop the 'test-' prefix: it's the conformance test suite, we know it's full of tests.
2012-02-27 07:54:23 -05:00
TEST_CONFORM_SIMPLE ("/timeline", timeline_base);
TEST_CONFORM_SIMPLE ("/timeline", timeline_markers_from_script);
TEST_CONFORM_SKIP (g_test_slow (), "/timeline", timeline_interpolation);
TEST_CONFORM_SKIP (g_test_slow (), "/timeline", timeline_rewind);
timeline: Add support for step() progress The CSS3 Transitions specification from the W3C defines the possibility of using a parametrized step() timing function, with the following prototype: steps(n_steps, [ start | end ]) where @n_steps represents the number of steps used to divide an interval between 0 and 1; the 'start' and 'end' tokens describe whether the value change should happen at the start of the transition, or at the end. For instance, the "steps(3, start)" timing function has the following profile: 1 | x | | | x---| | ' | | x---' | | ' | 0 |---' | Whereas the "steps(3, end)" timing function has the following profile: 1 | x---| | ' | | x---' | | ' | x---' | | | 0 | | Since ClutterTimeline uses an enumeration for controlling the progress mode, we need additional API to define the parameters of the steps() progress; for this reason, we need a CLUTTER_STEPS enumeration value, and a method for setting the number of steps and the value transition policy. The CSS3 Transitions spec helpfully also defines a step-start and a step-end shorthands, which expand to step(1, start) and step(1, end) respectively; we can provide a CLUTTER_STEP_START and CLUTTER_STEP_END enumeration values for those.
2012-07-19 19:47:48 -04:00
TEST_CONFORM_SIMPLE ("/timeline", timeline_progress_mode);
TEST_CONFORM_SIMPLE ("/timeline", timeline_progress_step);
conform: Clean up test names Drop the 'test-' prefix: it's the conformance test suite, we know it's full of tests.
2012-02-27 07:54:23 -05:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
TEST_CONFORM_SIMPLE ("/score", score_base);
TEST_CONFORM_SIMPLE ("/behaviours", behaviours_base);
conform/events-touch: Silently bail out if init failed This removes the need to conditionally run the test.
2012-06-07 07:23:49 -04:00
TEST_CONFORM_SIMPLE ("/events", events_touch);
conform: Temporarily disable Cally's conformance test See bug: https://bugzilla.gnome.org/show_bug.cgi?id=655588 for the failure.
2011-08-15 09:09:24 -04:00
/* FIXME - see bug https://bugzilla.gnome.org/show_bug.cgi?id=655588 */
TEST_CONFORM_TODO ("/cally", cally_text);
conform: Disable the Cogl tests Cogl is being tested pretty well, these days; also, there is a failure in the mipmap test that I really don't have time to bisect.
2013-02-20 18:31:17 -05:00
#if 0
conform: Adds a test-cogl-object conformance test This tests the new cogl_object_get/set_user_data API
2010-06-01 12:27:59 -04:00
TEST_CONFORM_SIMPLE ("/cogl", test_cogl_object);
tests: rename cogl conformance tests so they can be clearly identified All Cogl conformance tests are now prefixed 'test-cogl-'
2009-11-26 19:28:39 -05:00
TEST_CONFORM_SIMPLE ("/cogl", test_cogl_fixed);
TEST_CONFORM_SIMPLE ("/cogl", test_cogl_materials);
TEST_CONFORM_SIMPLE ("/cogl", test_cogl_premult);
TEST_CONFORM_SIMPLE ("/cogl", test_cogl_readpixels);
TEST_CONFORM_SIMPLE ("/cogl/texture", test_cogl_npot_texture);
journal: Fixes logging of multiple sets of texture coordinates If a user supplied multiple groups of texture coordinates with cogl_rectangle_with_multitexture_coords() then we would repeatedly log only the first group in the journal. This fixes that bug and adds a conformance test to verify the fix. Thanks to Gord Allott for reporting this bug.
2010-01-12 06:02:09 -05:00
TEST_CONFORM_SIMPLE ("/cogl/texture", test_cogl_multitexture);
tests: Add a simple conformance test for texture mipmaps This adds a test which renders a texture into a 1x1 pixel quad with and without filters that use mipmaps. The pixel without mipmaps will be one of the colors from the texture and the one with will be the average of all the pixels in the texture.
2010-01-15 07:02:09 -05:00
TEST_CONFORM_SIMPLE ("/cogl/texture", test_cogl_texture_mipmaps);
Add a conformance test for rectangle textures The test creates a GL_TEXTURE_RECTANGLE_ARB texture using cogl_texture_new_from_foreign and confirms that rendering it works correctly. If the rectangle texture extension isn't available then this test always succeeds. http://bugzilla.openedhand.com/show_bug.cgi?id=2015
2010-03-02 10:18:00 -05:00
TEST_CONFORM_SIMPLE ("/cogl/texture", test_cogl_texture_rectangle);
Add a test case for CoglTexturePixmapX11
2010-06-18 13:51:15 -04:00
TEST_CONFORM_SIMPLE ("/cogl/texture", test_cogl_texture_pixmap_x11);
Add a conformance test for cogl_texture_{get_data,set_region} This verifies that calling cogl_texture_get_data returns the same data uploaded to the texture. The bottom quarter of the texture is replaced using cogl_texture_set_region. It tries creating the texture with different sizes and flags in the hope that it will hit different texture backends.
2010-07-08 09:25:23 -04:00
TEST_CONFORM_SIMPLE ("/cogl/texture", test_cogl_texture_get_set_data);
Add a conformance test for atlas migration This adds a conformance test which creates a lot of textures with increasing size and destroys them again a number of times in order to cause a few atlas migrations. The last time the textures are created they are all read back and the data is verified to confirm that the atlas migration successfully preserved the data.
2011-02-24 15:30:30 -05:00
TEST_CONFORM_SIMPLE ("/cogl/texture", test_cogl_atlas_migration);
tests: rename cogl conformance tests so they can be clearly identified All Cogl conformance tests are now prefixed 'test-cogl-'
2009-11-26 19:28:39 -05:00
TEST_CONFORM_SIMPLE ("/cogl/vertex-buffer", test_cogl_vertex_buffer_contiguous);
TEST_CONFORM_SIMPLE ("/cogl/vertex-buffer", test_cogl_vertex_buffer_interleved);
TEST_CONFORM_SIMPLE ("/cogl/vertex-buffer", test_cogl_vertex_buffer_mutability);
/* left to the end because they aren't currently very orthogonal and tend to
* break subsequent tests! */
TEST_CONFORM_SIMPLE ("/cogl", test_cogl_viewport);
conform: Disable the Cogl tests Cogl is being tested pretty well, these days; also, there is a failure in the mipmap test that I really don't have time to bisect.
2013-02-20 18:31:17 -05:00
#endif
tests: rename cogl conformance tests so they can be clearly identified All Cogl conformance tests are now prefixed 'test-cogl-'
2009-11-26 19:28:39 -05:00
2008-11-12 Emmanuele Bassi <ebassi@linux.intel.com> * tests/conform/Makefile.am: * tests/conform/test-conform-main.c: * tests/conform/test-paint-opacity.c: Add test unit for label, rectangle and paint opacity.
2008-11-12 09:41:01 -05:00
return g_test_run ();
}
Reference in New Issue Copy Permalink