isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-25 17:40:40 -05:00
Code Issues Packages Projects Releases Wiki Activity
gnome-3-22
mutter/clutter/tests/interactive/Makefile.am

148 lines
3.5 KiB
Makefile
Raw Permalink Normal View History

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
UNIT_TESTS = \
test-textures -> test-texture-slicing The unit is supposed to be testing the slicing support in CoglTexture.
2011-09-27 12:50:51 -04:00
test-texture-slicing.c \
[tests] Added test-texture-async
2009-03-11 14:26:30 -04:00
test-texture-async.c \
texture: Use a base material for all instances Creating new materials for every Texture instance results in a lot of ARBfp programs being generated/compiled. Since most textures will just be similar we should create a template material for all of them, and then copy it in every instance. Cogl will try to optimize the generation of the program and, hopefully, will reuse the same program most of the time. With this change, a simple test shows that loading 48 textures will result in just two programs being compiled - with and without batching enabled. http://bugzilla.clutter-project.org/show_bug.cgi?id=2295
2010-09-02 09:48:30 -04:00
test-texture-material.c \
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
test-events.c \
test-scale.c \
test-actors.c \
interactive: Rename test-rotate The rotation test is now really testing the shader-based effects we ship with Clutter. The name should be changed to reflect that.
2010-12-16 10:30:53 -05:00
test-shader-effects.c \
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
test-script.c \
test-grab.c \
tests/interactive: Adds a test-cogl-shader-arbfp.c This tests the ARBfp support for cogl_program and cogl_shader using the shaders Chris Lord adapted from test-shader when he was experimenting with adding ARBfp support to clutter back in 2008 (See: http://bugzilla.clutter-project.org/show_bug.cgi?id=1049)
2010-08-05 10:20:49 -04:00
test-cogl-shader-arbfp.c \
tests-interactive: Adds a test-cogl-shader-glsl.c This is based on test-shader.c but is solely implemented with the cogl_program/shader APIs instead of the clutter shader APIs.
2010-08-05 10:18:39 -04:00
test-cogl-shader-glsl.c \
Add ClutterAnimator ClutterAnimator is a class for managing the animation of multiple properties of multiple actors over time with keyframing of values. The Animator class is meant to be used to effectively describe animations using the ClutterScript definition format, and to construct complex implicit animations from the ground up. Signed-off-by: Emmanuele Bassi <ebassi@linux.intel.com>
2010-02-05 07:32:00 -05:00
test-animator.c \
state machine: added state machine
2010-05-11 10:04:34 -04:00
test-state.c \
test-state-animator.c \
[tests] Ensures that test-viewport.c is built test-viewport.c wasn't listed correctly in the UNIT_TESTS variable (it was missing the .c extension, and so it wasn't being built.)
2008-12-19 16:31:18 -05:00
test-fbo.c \
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
test-multistage.c \
test-cogl-tex-tile.c \
test-cogl-tex-convert.c \
test-cogl-tex-foreign.c \
test-cogl-offscreen.c \
test-cogl-tex-polygon.c \
Fully integrates CoglMaterial throughout the rest of Cogl This glues CoglMaterial in as the fundamental way that Cogl describes how to fill in geometry. It adds cogl_set_source (), which is used to set the material which will be used by all subsequent drawing functions It adds cogl_set_source_texture as a convenience for setting up a default material with a single texture layer, and cogl_set_source_color is now also a convenience for setting up a material with a solid fill. "drawing functions" include, cogl_rectangle, cogl_texture_rectangle, cogl_texture_multiple_rectangles, cogl_texture_polygon (though the cogl_texture_* funcs have been renamed; see below for details), cogl_path_fill/stroke and cogl_vertex_buffer_draw*. cogl_texture_rectangle, cogl_texture_multiple_rectangles and cogl_texture_polygon no longer take a texture handle; instead the current source material is referenced. The functions have also been renamed to: cogl_rectangle_with_texture_coords, cogl_rectangles_with_texture_coords and cogl_polygon respectivly. Most code that previously did: cogl_texture_rectangle (tex_handle, x, y,...); needs to be changed to now do: cogl_set_source_texture (tex_handle); cogl_rectangle_with_texture_coords (x, y,....); In the less likely case where you were blending your source texture with a color like: cogl_set_source_color4ub (r,g,b,a); /* where r,g,b,a isn't just white */ cogl_texture_rectangle (tex_handle, x, y,...); you will need your own material to do that: mat = cogl_material_new (); cogl_material_set_color4ub (r,g,b,a); cogl_material_set_layer (mat, 0, tex_handle)); cogl_set_source_material (mat); Code that uses the texture coordinates, 0, 0, 1, 1 don't need to use cog_rectangle_with_texure_coords since these are the coordinates that cogl_rectangle will use. For cogl_texture_polygon; as well as dropping the texture handle, the n_vertices and vertices arguments were transposed for consistency. So code previously written as: cogl_texture_polygon (tex_handle, 3, verts, TRUE); need to be written as: cogl_set_source_texture (tex_handle); cogl_polygon (verts, 3, TRUE); All of the unit tests have been updated to now use the material API and test-cogl-material has been renamed to test-cogl-multitexture since any textured quad is now technically a test of CoglMaterial but this test specifically creates a material with multiple texture layers. Note: The GLES backend has not been updated yet; that will be done in a following commit.
2009-01-23 11:15:40 -05:00
test-cogl-multitexture.c \
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
test-stage-read-pixels.c \
test-paint-wrapper.c \
test-texture-quality.c \
2008-11-17 Emmanuele Bassi <ebassi@linux.intel.com> Bug 1014 - Clutter Animation API Improvements * clutter/Makefile.am: * clutter/clutter.h: Update the build * clutter/clutter-types.h: Add AnimationMode, an enumeration for easing functions. * clutter/clutter-alpha.[ch]: Add the :mode property to control the function bound to an Alpha instance using an enumeration value. Also add six new alpha functions: - ease-in, ease-out, ease-in-out - sine-in, sine-out, sine-in-out * clutter/clutter-deprecated.h: Deprecate the #defines for the alpha functions. They will be replaced by entries in the ClutterAnimationMode. * clutter/clutter-interval.[ch]: Add ClutterInterval, an object for defining, validating and computing an interval between two values. * clutter/clutter-animation.[ch]: Add ClutterAnimation, an object responsible for animation the properties of a single actor along an interval of values. ClutterAnimation memory management is automatic. A simple wrapper method for ClutterActor is provided: clutter_actor_animate() which will create, or update, an animation for the passed actor. * clutter/clutter-debug.h: * clutter/clutter-main.c: Add a new 'animation' debug note. * clutter/clutter-script.c: Clean up the alpha functions whitelist, and add the new functions. * doc/reference/clutter/Makefile.am: * doc/reference/clutter/clutter-sections.txt: Update the API reference. * doc/reference/clutter/clutter-animation.xml: Renamed to doc/reference/clutter/clutter-animation-tutorial.xml to avoid clashes with the ClutterAnimation section. * doc/reference/clutter/clutter-docs.sgml: Renamed to doc/reference/clutter/clutter-docs.xml, as it was an XML file and not a SGML file. * tests/Makefile.am: * tests/interactive/Makefile.am: * tests/interactive/test-animation.c: * tests/interactive/test-easing.c: Add two tests for the new simple animation API and the easing functions. * tests/interactive/test-actors.c: * tests/interactive/test-behave.c: * tests/interactive/test-depth.c: * tests/interactive/test-effects.c: * tests/interactive/test-layout.c: * tests/interactive/test-multistage.c: * tests/interactive/test-paint-wrapper.c: * tests/interactive/test-rotate.c: * tests/interactive/test-scale.c: * tests/interactive/test-texture-quality.c: * tests/interactive/test-threads.c: * tests/interactive/test-viewport.c: Update interactive tests to the deprecations and new alpha API.
2008-11-18 04:50:03 -05:00
test-layout.c \
test-animation.c \
2008-12-08 Emmanuele Bassi <ebassi@linux.intel.com> * clutter/Makefile.am: * clutter/clutter.h: Add ClutterBindingPool to the build. * clutter/clutter-binding-pool.c: * clutter/clutter-binding-pool.h: Add ClutterBindingPool, a data structure meant to hold (key symbol, modifiers) pairs and associate them to a closure. The ClutterBindingPool can be used to install key bindings for actors and then execute closures inside the key-press-event signal handlers, removing the need for big switch() or if() blocks for each key. * clutter/clutter-event.c: Consistently use "key symbol" instead of "key value". * clutter/clutter-event.h: Add more modifier masks. * clutter/clutter-marshal.list: * tests/conform/Makefile.am: * tests/conform/test-binding-pool.c: * tests/conform/test-conform-main.c: Add ClutterBindingPool conformance test. * tests/interactive/Makefile.am: * tests/interactive/test-binding-pool.c: Add interactive test (and example code) for the ClutterBindingPool usage.
2008-12-08 08:57:10 -05:00
test-easing.c \
Initial import of the Text actor from Tidy The TidyText actor is meant as a replacement for both ClutterLabel and ClutterText. Any text-displaying and editing actor should derive from ClutterText and implement the various visual cues to differentiate the editable from the non-editable state. Those visual cues usually belong to a high-level toolkit, especially if themeing is involved.
2008-12-11 06:12:48 -05:00
test-binding-pool.c \
[tests] Add text field interactive test The test-text-field is a test/example that shows how to use the ClutterText as a text input field in single line mode.
2009-01-06 19:27:50 -05:00
test-text.c \
[tests] Adds a flowery clutter_cairo_texture unit test This is simply a copy of flowers.c from the old clutter-cairo repo
2009-01-08 13:54:48 -05:00
test-text-field.c \
cairo-texture: Use signal-based drawing The current "create context/draw/destroy context" pattern presents various problems. The first issue is that it defers memory management to the caller of the create() or create_region() methods, which makes bookkeeping of the cairo_t* harder for language bindings and third party libraries. The second issue is that, while it's easier for draw-and-forget texturs, this API is needlessly complicated for contents that have to change programmatically - and it introduces constraints like calling the drawing code explicitly after a surface resize (e.g. inside an allocate() implementation). By using a signal-based approach we can make the CairoTexture actor behave like other actors, and like other libraries using Cairo as their 2D drawing API. The semantics of the newly-introduced ::draw signal are the same as the one used by GTK+: - the signal is emitted on invalidation; - the cairo_t* context is owned by the actor; - it is safe to have multiple callbacks attached to the same signal, to allow composition; - the cairo_t* is already clipped to the invalidated area, so that Cairo can discard geometry immediately before we upload the texture data. There are possible future improvements, like coalescing multiple invalidations inside regions, and performing clipped draws during the paint cycle; we could even perform clipped redraws if we know the extent of the invalidated area.
2011-07-26 07:40:52 -04:00
test-cairo-clock.c \
cairo-texture: Allow overriding the surface creation By using a new signal, ::create-surface (width, height), it should be possible for third party code and sub-classes to override the default surface creation code in CairoSurface. This commit takes a bit of the patch from: http://bugzilla.clutter-project.org/show_bug.cgi?id=1878 which cleans up CairoTexture; the idea, mutuated from that bug, is that the CairoTexture actor checks whether the surface it has it's an image one, and in that case it uses a Cogl texture as the backing store. In case the surface is not an image one we assume that the surface itself has some way of updating the GL state and flush the surface.
2010-10-15 12:35:41 -04:00
test-cairo-flowers.c \
[tests] Add a Box interactive test
2009-09-11 10:34:13 -04:00
test-cogl-vertex-buffer.c \
action: Add DragAction, an action implementing drag capabilities DragAction is an Action sub-class that provides dragging capabilities to any actor. DragAction has: • drag-begin, drag-motion and drag-end signals, relaying the event information like coordinates, button and modifiers to user code; • drag-threshold property, for delaying the drag start by a given amount of pixels; • drag-handle property, to allow using other actors as the drag handle. • drag-axis property, to allow constraining the dragging to a specific axis. An interactive test demonstrating the various features is also provided.
2010-05-12 07:00:33 -04:00
test-stage-sizing.c \
bind-constraint: Add width and height binding Allow using the BindConstraint to bind width and height of a source actor. Also, add a test for the BindConstraint showing all types of usages for this constraint class.
2010-06-28 12:18:35 -04:00
test-scrolling.c \
Add ClutterSwipeAction and ClutterGestureAction To allow actors to handle gestures in a more organized way. http://bugzilla.clutter-project.org/show_bug.cgi?id=2585
2011-03-09 04:06:44 -05:00
test-swipe-action.c \
Add ClutterTableLayout, a layout showing children in rows and columns A TableLayout is a layout manager that allocates its children in rows and columns. Each child is assigned to a cell (or more if a cell span is set). The supported child properties are: • x-expand and y-expand: if this cell with try to allocate the available extra space for the table. • x-fill and y-fill: if the child will get all the space available in the cell. • x-align and y-align: if the child does not fill the cell, then where the child will be aligned inside the cell. • row-span and col-span: number of cells the child will allocate for itself. Also, the TableLayout has row-spacing and col-spacing for specifying the space in pixels between rows and between columns. We also include a simple test of the layout manager, and the documentation updates. The TableLayout was implemented starting from MxTable and ClutterBoxLayout. http://bugzilla.clutter-project.org/show_bug.cgi?id=2038 Signed-off-by: Emmanuele Bassi <ebassi@linux.intel.com>
2010-03-18 12:02:31 -04:00
test-cogl-point-sprites.c \
tests: Add a PathConstraint interactive test
2010-10-25 10:47:15 -04:00
test-table-layout.c \
Add SnapConstraint A SnapConstraint is a constraint that "snaps" the edges of two actors together.
2010-11-10 11:37:34 -05:00
test-path-constraint.c \
Add ClutterDropAction ClutterDropAction is an Action sub-class that allows writing actors that react to dragged actors being dropped on them. https://bugzilla.gnome.org/show_bug.cgi?id=652842
2011-06-17 11:54:31 -04:00
test-state-script.c \
tests/interactive: Add a simple test for Actor It's meant to be xincluded in the API reference.
2011-12-20 09:47:35 -05:00
test-devices.c \
Add ClutterCanvas, a drawing content
2012-03-08 05:31:21 -05:00
test-content.c \
Add ClutterScrollActor ClutterScrollActor is an actor that allows showing a portion of its contents.
2012-04-12 10:56:53 -04:00
test-keyframe-transition.c \
tests: Add interactive test for touch events https://bugzilla.gnome.org/show_bug.cgi?id=677390
2012-06-04 07:15:43 -04:00
test-bind-constraint.c \
tests: add an interactive test for rotate and zoom actions https://bugzilla.gnome.org/show_bug.cgi?id=698836
2013-04-25 20:16:15 -04:00
test-touch-events.c \
test-rotate-zoom.c
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/interactive/Makefile.am * tests/interactive/test-pixmap.c: test-pixmap + test-devices accidentally got dropped from the makefiles when changing the unit test layout; this puts them back.
2008-11-15 10:03:09 -05:00
if X11_TESTS
interactive/devices: Build unconditionally The test-devices interactive test does not rely on the X11 API being present any more, after the introduction of the device manager API.
2011-10-17 11:06:15 -04:00
UNIT_TESTS += test-pixmap.c
* tests/interactive/Makefile.am * tests/interactive/test-pixmap.c: test-pixmap + test-devices accidentally got dropped from the makefiles when changing the unit test layout; this puts them back.
2008-11-15 10:03:09 -05:00
endif
interactive/image: Test ClutterImage Load up the image content using a GdkPixbuf; this means that the test is not compiled when --disable-gdk-pixbuf is passed.
2012-03-09 09:58:17 -05:00
if PIXBUF_TESTS
interactive/image-box: Add a pure Image test, suitable for docs
2012-03-09 11:26:34 -05:00
UNIT_TESTS += \
Move examples from tests/interactive to a new top-level The example code that is meant to be XIncluded into the API reference should not be part of the interactive test suite: it's code that it is meant to be used as a reference implementation - whereas the interactive test suite should be allowed to be lean and test behaviour even in nasty ways. In short: the test suite should not be the place where we show off idiomatic code for educational purposes.
2012-05-01 13:30:10 -04:00
test-image.c
interactive/image: Test ClutterImage Load up the image content using a GdkPixbuf; this means that the test is not compiled when --disable-gdk-pixbuf is passed.
2012-03-09 09:58:17 -05:00
endif
Removes the addition of the .exe extension to unit-test scripts, on win32. On win32, test scripts are created with a .exe extension. Under mingw, a .exe script is launched in 16 bit compatibility mode (through ntvdm), and so it just does not run. http://bugzilla.clutter-project.org/show_bug.cgi?id=2619
2011-03-25 07:49:44 -04:00
SHEXT = $(EXEEXT)
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
# For convenience, this provides a way to easily run individual unit tests:
build: Ensure tests are built only on make check Tests should only be enabled when we want to run them, or when we are generating a tarball.
2013-08-16 05:57:54 -04:00
wrappers: stamp-test-interactive
tests: Clean up interactive test build The build for interactive tests creates symbolic links for the data under tests/data; it also uses symbolic links for creating "binaries" for each interactive test. This is less than ideal, though. Instead, the tests should build a path to the data files by using a pre-processor define like TESTS_DATADIR; both g_build_filename() and pre-processor string concatenation can be used to generate a valid file name with the full path to the files. The build system should also create wrapper scripts, just like we do inside the conformance test suite, to be able to launch single tests.
2009-11-05 12:30:33 -05:00
@true
tests: Remove some trailing spaces
2011-11-18 11:38:45 -05:00
build: Drop ad hoc gitignore generation rules Instead, include Makefile.am.gitignore.
2015-01-01 14:40:18 -05:00
GIT_IGNORE_EXTRA = \
stamp-test-interactive \
stamp-test-unit-names \
test-unit-names.h \
$(UNIT_TESTS:.c=$(SHEXT))
build: Generate gitignore on BUILT_SOURCES The test-unit-names.h header file is generated unconditionally, so we need to generate the gitignore file that references it along with the header.
2013-08-16 06:07:35 -04:00
stamp-test-interactive: Makefile
@wrapper=$(abs_builddir)/wrapper.sh ; \
chmod +x $$wrapper && \
tests: give all the arguments to the wrapper Some tests can be given extra arguments. The test-interactive dispatch mechanism handles that but the small shell scripts around the wrapper do not forward the arguments to the wrapper. Reviewed-by: Emmanuele Bassi <ebassi@linux.intel.com>
2009-11-25 07:25:14 -05:00
for i in $(UNIT_TESTS); \
tests: Clean up interactive test build The build for interactive tests creates symbolic links for the data under tests/data; it also uses symbolic links for creating "binaries" for each interactive test. This is less than ideal, though. Instead, the tests should build a path to the data files by using a pre-processor define like TESTS_DATADIR; both g_build_filename() and pre-processor string concatenation can be used to generate a valid file name with the full path to the files. The build system should also create wrapper scripts, just like we do inside the conformance test suite, to be able to launch single tests.
2009-11-05 12:30:33 -05:00
do \
test_bin=$${i%*.c} ; \
build: Fix up the silent rules prefixes Automake increased the whitespace, so we need to do that for our "I Can't Believe It's Not Autotool™" rules.
2013-05-15 10:07:15 -04:00
echo " GEN $$test_bin" ; \
tests: Clean up interactive test build The build for interactive tests creates symbolic links for the data under tests/data; it also uses symbolic links for creating "binaries" for each interactive test. This is less than ideal, though. Instead, the tests should build a path to the data files by using a pre-processor define like TESTS_DATADIR; both g_build_filename() and pre-processor string concatenation can be used to generate a valid file name with the full path to the files. The build system should also create wrapper scripts, just like we do inside the conformance test suite, to be able to launch single tests.
2009-11-05 12:30:33 -05:00
( echo "#!/bin/sh" ; \
tests: give all the arguments to the wrapper Some tests can be given extra arguments. The test-interactive dispatch mechanism handles that but the small shell scripts around the wrapper do not forward the arguments to the wrapper. Reviewed-by: Emmanuele Bassi <ebassi@linux.intel.com>
2009-11-25 07:25:14 -05:00
echo "$$wrapper $$test_bin \$$@" \
Removes the addition of the .exe extension to unit-test scripts, on win32. On win32, test scripts are created with a .exe extension. Under mingw, a .exe script is launched in 16 bit compatibility mode (through ntvdm), and so it just does not run. http://bugzilla.clutter-project.org/show_bug.cgi?id=2619
2011-03-25 07:49:44 -04:00
) > $$test_bin$(SHEXT) ; \
chmod +x $$test_bin$(SHEXT) ; \
tests: Clean up interactive test build The build for interactive tests creates symbolic links for the data under tests/data; it also uses symbolic links for creating "binaries" for each interactive test. This is less than ideal, though. Instead, the tests should build a path to the data files by using a pre-processor define like TESTS_DATADIR; both g_build_filename() and pre-processor string concatenation can be used to generate a valid file name with the full path to the files. The build system should also create wrapper scripts, just like we do inside the conformance test suite, to be able to launch single tests.
2009-11-05 12:30:33 -05:00
done \
&& echo timestamp > $(@F)
test-interactive: Allow querying the interactive test for a description It would be nice if the interactive tests had a way to be queried for a description, instead of "Just Knowing" what they are meant to be doing.
2011-09-27 12:40:51 -04:00
test-unit-names.h: stamp-test-unit-names
@true
build: Drop ad hoc gitignore generation rules Instead, include Makefile.am.gitignore.
2015-01-01 14:40:18 -05:00
stamp-test-unit-names: Makefile
test-interactive: Allow querying the interactive test for a description It would be nice if the interactive tests had a way to be queried for a description, instead of "Just Knowing" what they are meant to be doing.
2011-09-27 12:40:51 -04:00
@( echo "/* ** This file is autogenerated. Do not edit. ** */" ; \
echo "" ; \
echo "const char *test_unit_names[] = {" ) > test-unit-names.h ; \
for i in $(UNIT_TESTS); \
do \
test_bin=$${i%*.c} ; \
echo " \"$$test_bin\"," >> test-unit-names.h ; \
done \
&& echo "};" >> test-unit-names.h \
&& echo timestamp > $(@F)
tests: Clean up interactive test build The build for interactive tests creates symbolic links for the data under tests/data; it also uses symbolic links for creating "binaries" for each interactive test. This is less than ideal, though. Instead, the tests should build a path to the data files by using a pre-processor define like TESTS_DATADIR; both g_build_filename() and pre-processor string concatenation can be used to generate a valid file name with the full path to the files. The build system should also create wrapper scripts, just like we do inside the conformance test suite, to be able to launch single tests.
2009-11-05 12:30:33 -05:00
clean-wrappers:
@for i in $(UNIT_TESTS); \
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
do \
tests: Clean up interactive test build The build for interactive tests creates symbolic links for the data under tests/data; it also uses symbolic links for creating "binaries" for each interactive test. This is less than ideal, though. Instead, the tests should build a path to the data files by using a pre-processor define like TESTS_DATADIR; both g_build_filename() and pre-processor string concatenation can be used to generate a valid file name with the full path to the files. The build system should also create wrapper scripts, just like we do inside the conformance test suite, to be able to launch single tests.
2009-11-05 12:30:33 -05:00
test_bin=$${i%*.c} ; \
build: Fix up the silent rules prefixes Automake increased the whitespace, so we need to do that for our "I Can't Believe It's Not Autotool™" rules.
2013-05-15 10:07:15 -04:00
echo " RM $$test_bin"; \
Removes the addition of the .exe extension to unit-test scripts, on win32. On win32, test scripts are created with a .exe extension. Under mingw, a .exe script is launched in 16 bit compatibility mode (through ntvdm), and so it just does not run. http://bugzilla.clutter-project.org/show_bug.cgi?id=2619
2011-03-25 07:49:44 -04:00
rm -f $$test_bin$(SHEXT); \
tests: Clean up interactive test build The build for interactive tests creates symbolic links for the data under tests/data; it also uses symbolic links for creating "binaries" for each interactive test. This is less than ideal, though. Instead, the tests should build a path to the data files by using a pre-processor define like TESTS_DATADIR; both g_build_filename() and pre-processor string concatenation can be used to generate a valid file name with the full path to the files. The build system should also create wrapper scripts, just like we do inside the conformance test suite, to be able to launch single tests.
2009-11-05 12:30:33 -05:00
done \
build: Fix distcheck
2011-11-22 07:11:06 -05:00
&& rm -f stamp-test-unit-names \
tests: Clean up interactive test build The build for interactive tests creates symbolic links for the data under tests/data; it also uses symbolic links for creating "binaries" for each interactive test. This is less than ideal, though. Instead, the tests should build a path to the data files by using a pre-processor define like TESTS_DATADIR; both g_build_filename() and pre-processor string concatenation can be used to generate a valid file name with the full path to the files. The build system should also create wrapper scripts, just like we do inside the conformance test suite, to be able to launch single tests.
2009-11-05 12:30:33 -05:00
&& rm -f stamp-test-interactive
2008-11-08 Emmanuele Bassi <ebassi@linux.intel.com> * tests/conform/Makefile.am: * tests/conform/test-actor-invariants.c: * tests/conform/test-conform-main.c: Move the actor invariants unit to the conform section of the test suite. * tests/interactive/Makefile.am: * tests/interactive/test-entry-auto.c: * tests/interactive/test-invariants.c: Remove the entry-auto and invariants test, since those two belong to the conform section.
2008-11-08 10:56:22 -05:00
tests: Clean up interactive test build The build for interactive tests creates symbolic links for the data under tests/data; it also uses symbolic links for creating "binaries" for each interactive test. This is less than ideal, though. Instead, the tests should build a path to the data files by using a pre-processor define like TESTS_DATADIR; both g_build_filename() and pre-processor string concatenation can be used to generate a valid file name with the full path to the files. The build system should also create wrapper scripts, just like we do inside the conformance test suite, to be able to launch single tests.
2009-11-05 12:30:33 -05:00
.PHONY: wrappers clean-wrappers
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
Fix build of clutter tests Various clutter test directly use cogl symbols, so they should be linked against mutter-cogl as well. Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk> https://bugzilla.gnome.org/show_bug.cgi?id=769636
2016-08-08 09:52:36 -04:00
common_ldadd = \
$(top_builddir)/clutter/libmutter-clutter-@CLUTTER_API_VERSION@.la \
$(top_builddir)/../cogl/cogl/libmutter-cogl.la
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
build: Ensure tests are built only on make check Tests should only be enabled when we want to run them, or when we are generating a tarball.
2013-08-16 05:57:54 -04:00
check_PROGRAMS = test-interactive
win32: drop win32 support
2016-01-12 11:23:09 -05:00
check_SCRIPTS = wrappers
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
build: Move test-unit-names.h out of the dist Let it be generated at build time, as it should. https://bugzilla.gnome.org/show_bug.cgi?id=674365
2012-05-28 10:33:01 -04:00
test_interactive_SOURCES = test-main.c $(UNIT_TESTS)
nodist_test_interactive_SOURCES = test-unit-names.h
interactive/image: Test ClutterImage Load up the image content using a GdkPixbuf; this means that the test is not compiled when --disable-gdk-pixbuf is passed.
2012-03-09 09:58:17 -05:00
test_interactive_CFLAGS = $(CLUTTER_CFLAGS) $(GDK_PIXBUF_CFLAGS)
tests: Clean up interactive test build The build for interactive tests creates symbolic links for the data under tests/data; it also uses symbolic links for creating "binaries" for each interactive test. This is less than ideal, though. Instead, the tests should build a path to the data files by using a pre-processor define like TESTS_DATADIR; both g_build_filename() and pre-processor string concatenation can be used to generate a valid file name with the full path to the files. The build system should also create wrapper scripts, just like we do inside the conformance test suite, to be able to launch single tests.
2009-11-05 12:30:33 -05:00
test_interactive_CPPFLAGS = \
Fully rework the conformance test suite The current conformance test suite is suboptimal in many ways. All tests are built into the same binary, which makes adding new tests, builting tests, and running groups of tests much more awkward than it needs to be. The first issue, especially, raises the bar of contribution in a significant way, while the other two take their toll on the maintainer. All of these changes were introduced back when we had both Clutter and Cogl tests in tree, and because we were building the test suite for every single change; since then, Cogl moved out of tree with all its tests, and we build the conformance test suite only when running the `check` make target. This admittedly large-ish commit changes the way the conformance test suite works, taking advantage of the changes in the GTest API and test harness. First of all, all tests are now built separately, using their own test suite as defined by each separate file. All tests run under the TAP harness provided by GTest and Automake, to gather a proper report using the Test Anything Protocol without using the `gtester` harness and the `gtester-report` script. We also use the Makefile rules provided by GLib to vastly simplify the build environment for the conformance test suite. On top of the changes for the build and harness, we also provide new API for creating and running test suites for Clutter. The API is public, because the test suite has to use it, but it's minimal and mostly provides convenience wrappers around GTest that make writing test units for Clutter easier. This commit disables all tests in the conformance test suite, as well as moving the data files outside of the tests/data directory; the next few commits will re-establish the conformance test suite separately so we can check that everything works in a reliable way.
2013-12-12 09:36:16 -05:00
-DTESTS_DATADIR=\""$(abs_srcdir)"\" \
keysyms: Update the macros to CLUTTER_KEY_* The keysyms defines in clutter-keysyms.h are generated from the X11 key symbols headers by doing the equivalent of a pass of sed from XK_* to CLUTTER_*. This might lead to namespace collisions, down the road. Instead, we should use the CLUTTER_KEY_* namespace. This commit includes the script, taken from GDK, that parses the X11 key symbols and generates two headers: - clutter-keysyms.h: the default included header, with CLUTTER_KEY_* - clutter-keysyms-compat.h: the compatibility header, with CLUTTER_* The compat.h header file is included if CLUTTER_DISABLE_DEPRECATED is not defined - essentially deprecating all the old key symbols. This does not change any ABI and, assuming that an application or library is not compiling with CLUTTER_DISABLE_DEPRECATED, the source compatibility is still guaranteed.
2010-09-10 08:41:49 -04:00
-DG_DISABLE_SINGLE_INCLUDES \
Disable deprecation warnings for the test suite We test deprecated functionality as well as current one, so we need to enable all symbols and disable the deprecation warnings.
2011-10-13 12:50:25 -04:00
-DGLIB_DISABLE_DEPRECATION_WARNINGS \
build: Disable Cogl deprecation warnings for tests We are exercising all sorts of deprecated API anyway.
2013-07-02 17:24:31 -04:00
-DCOGL_DISABLE_DEPRECATION_WARNINGS \
build: Remove INCLUDES directives They have been deprecated for a while, replaced by AM_CPPFLAGS.
2013-05-15 10:18:13 -04:00
-DCLUTTER_DISABLE_DEPRECATION_WARNINGS \
Fix the merged build https://bugzilla.gnome.org/show_bug.cgi?id=760439
2016-04-08 13:58:20 -04:00
-I$(top_srcdir)/../cogl \
-I$(top_builddir)/../cogl \
build: Remove INCLUDES directives They have been deprecated for a while, replaced by AM_CPPFLAGS.
2013-05-15 10:18:13 -04:00
-I$(top_srcdir) \
-I$(top_builddir) \
-I$(top_srcdir)/clutter \
-I$(top_builddir)/clutter
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
test_interactive_LDFLAGS = -export-dynamic
build: Use libtool macros to find libm Instead of using `-lm` everywhere, use LT_LIB_M inside configure.ac, and $(LIBM) inside Makefile.am.
2015-03-03 12:23:37 -05:00
test_interactive_LDADD = $(CLUTTER_LIBS) $(GDK_PIXBUF_LIBS) $(common_ldadd) $(LIBM)
[build] dist tests/interactive/wrapper.sh in tests/interactive/Makefile.am add wrapper.sh to EXTRA_DIST otherwise interactive unit tests wont be runnable when building from distributed tarballs.
2009-08-03 09:53:46 -04:00
Fix 'make dist'
2011-11-18 12:08:01 -05:00
EXTRA_DIST = \
Fully rework the conformance test suite The current conformance test suite is suboptimal in many ways. All tests are built into the same binary, which makes adding new tests, builting tests, and running groups of tests much more awkward than it needs to be. The first issue, especially, raises the bar of contribution in a significant way, while the other two take their toll on the maintainer. All of these changes were introduced back when we had both Clutter and Cogl tests in tree, and because we were building the test suite for every single change; since then, Cogl moved out of tree with all its tests, and we build the conformance test suite only when running the `check` make target. This admittedly large-ish commit changes the way the conformance test suite works, taking advantage of the changes in the GTest API and test harness. First of all, all tests are now built separately, using their own test suite as defined by each separate file. All tests run under the TAP harness provided by GTest and Automake, to gather a proper report using the Test Anything Protocol without using the `gtester` harness and the `gtester-report` script. We also use the Makefile rules provided by GLib to vastly simplify the build environment for the conformance test suite. On top of the changes for the build and harness, we also provide new API for creating and running test suites for Clutter. The API is public, because the test suite has to use it, but it's minimal and mostly provides convenience wrappers around GTest that make writing test units for Clutter easier. This commit disables all tests in the conformance test suite, as well as moving the data files outside of the tests/data directory; the next few commits will re-establish the conformance test suite separately so we can check that everything works in a reliable way.
2013-12-12 09:36:16 -05:00
wrapper.sh.in \
test-script.json \
test-script-signals.json \
redhand.png
Fix 'make dist'
2011-11-18 12:08:01 -05:00
test-interactive: Allow querying the interactive test for a description It would be nice if the interactive tests had a way to be queried for a description, instead of "Just Knowing" what they are meant to be doing.
2011-09-27 12:40:51 -04:00
DISTCLEANFILES = wrapper.sh .gitignore test-unit-names.h
build: Use maintainer-clean for the ignore files removal Instead of distclean.
2010-08-15 13:42:54 -04:00
build: Ensure tests are built only on make check Tests should only be enabled when we want to run them, or when we are generating a tarball.
2013-08-16 05:57:54 -04:00
BUILT_SOURCES = test-unit-names.h
tests: Clean up interactive test build The build for interactive tests creates symbolic links for the data under tests/data; it also uses symbolic links for creating "binaries" for each interactive test. This is less than ideal, though. Instead, the tests should build a path to the data files by using a pre-processor define like TESTS_DATADIR; both g_build_filename() and pre-processor string concatenation can be used to generate a valid file name with the full path to the files. The build system should also create wrapper scripts, just like we do inside the conformance test suite, to be able to launch single tests.
2009-11-05 12:30:33 -05:00
clean-local: clean-wrappers
Reference in New Issue Copy Permalink