isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-12-29 14:22:13 +00:00
Code Issues Packages Projects Releases Wiki Activity
4fd74e71e6
mutter/tests/conform/Makefile.am

181 lines
5.6 KiB
Makefile
Raw Normal View History

[build] Split out the custom silent rules The silent rules we use for custom targets should be moved into a separate Makefile.am that gets included from all the others.
2009-09-16 16:43:58 +00:00
include $(top_srcdir)/build/autotools/Makefile.am.silent
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
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 19:32:28 +00:00
noinst_PROGRAMS = test-conformance
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
test_conformance_SOURCES = \
test-conform-main.c \
test-conform-common.c \
test-conform-common.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 19:32:28 +00:00
\
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
test-timeline-interpolate.c \
test-timeline-rewind.c \
test-timeline.c \
tests: rename cogl conformance tests so they can be clearly identified All Cogl conformance tests are now prefixed 'test-cogl-'
2009-11-27 00:28:39 +00:00
test-cogl-vertex-buffer-contiguous.c \
test-cogl-vertex-buffer-interleved.c \
test-cogl-vertex-buffer-mutability.c \
test-cogl-fixed.c \
test-cogl-backface-culling.c \
test-cogl-npot-texture.c \
test-cogl-blend-strings.c \
test-cogl-premult.c \
test-cogl-materials.c \
test-cogl-viewport.c \
test-cogl-offscreen.c \
test-cogl-readpixels.c \
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 11:02:09 +00:00
test-cogl-multitexture.c \
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 12:02:09 +00:00
test-cogl-texture-mipmaps.c \
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 15:18:00 +00:00
test-cogl-texture-rectangle.c \
tests: Add a conformance test for the wrap modes of a cogl material This renders a texture using different combinations of wrap modes for the s and t coordinates and then verifies that the expected wrapping is acheived. The texture is drawn using rectangles, polygons and vbos. There is also code to test a rectangle using an atlased texture (which should test the manual repeating) however the validation for this is currently disabled because it doesn't work. http://bugzilla.openedhand.com/show_bug.cgi?id=2063
2010-03-31 17:54:34 +00:00
test-cogl-wrap-modes.c \
tests: Add a test for CoglPixelBuffers Exercise the whole public CoglBuffer / CoglPixelBuffer and cogl_texture_new_from_buffer API.
2010-01-22 15:38:31 +00:00
test-cogl-pixel-buffer.c \
Add a test case for cogl_path This tests various paths drawing rectangles and verifies that the expected pixels are filled in. Some of the paths are drawn by copying an existing path and modifying it which should test the copy-on-write code.
2010-04-08 16:18:40 +00:00
test-cogl-path.c \
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
test-path.c \
test-pick.c \
test-clutter-rectangle.c \
test-actor-invariants.c \
test-paint-opacity.c \
test-binding-pool.c \
Merge the ClutterText actor Merge branch 'text-actor' * text-actor: (108 commits) Re-align ClutterText header file [text] Fix cursor sizing Comments and whitespace fixes to ClutterText [docs] Add newly added :single-line-mode accessors Update the ignore file [tests] Add text field interactive test [text] Add single-line-mode to ClutterText [text] Fix the deletion actions [text] Use cached length when possible [tests] Add unit for the ClutterText:password-char property [docs] Update the Text section [text] Coalesce text visibility and password character Allow localizations to change the text direction Clean up the update_pango_context() function Pass the PangoContext, not the MainContext Revert the logic of the PangoContext check Remove the binding pool entry from the list Remove BindingPool::list_actions() Add ClutterActor::create_pango_context() Rename the PangoContext creation functions ...
2009-01-07 12:06:33 +00:00
test-clutter-text.c \
Add a conformance test for ClutterCairoTexture This adds a simple test for ClutterCairoTexture that draws two rectangles to the cairo surface in an idle callback and then verifies that they appeared at the right colours in the paint callback. If that succeeds then the second time the idle callback is invoked it will replace one of the rectangles with a sub region update and the following paint callback will again verify the rectangles.
2010-05-10 16:43:17 +00:00
test-clutter-cairo-texture.c \
Merge the ClutterText actor Merge branch 'text-actor' * text-actor: (108 commits) Re-align ClutterText header file [text] Fix cursor sizing Comments and whitespace fixes to ClutterText [docs] Add newly added :single-line-mode accessors Update the ignore file [tests] Add text field interactive test [text] Add single-line-mode to ClutterText [text] Fix the deletion actions [text] Use cached length when possible [tests] Add unit for the ClutterText:password-char property [docs] Update the Text section [text] Coalesce text visibility and password character Allow localizations to change the text direction Clean up the update_pango_context() function Pass the PangoContext, not the MainContext Revert the logic of the PangoContext check Remove the binding pool entry from the list Remove BindingPool::list_actions() Add ClutterActor::create_pango_context() Rename the PangoContext creation functions ...
2009-01-07 12:06:33 +00:00
test-text-cache.c \
Add a conformance test for the anchor point This verifies that the anchor point can be set from a gravity and then it moves when the anchor point changes size.
2009-01-22 13:14:02 +00:00
test-anchors.c \
[tests] Add conformance tests for ClutterModel ClutterModel has an interactive test but lacks a conformance unit for automatic testing. This is the beginning of that unit, which covers the population and iteration over a ListModel.
2009-02-14 11:45:27 +00:00
test-model.c \
[tests] Add ClutterColor conformance tests Add a conformance test unit for the to_string() and from_string() methods.
2009-06-01 17:43:47 +00:00
test-color.c \
[units] Rework Units into logical distance value Units as they have been implemented since Clutter 0.4 have always been misdefined as "logical distance unit", while they were just pixels with fractionary bits. Units should be reworked to be opaque structures to hold a value and its unit type, that can be then converted into pixels when Clutter needs to paint or compute size requisitions and perform allocations. The previous API should be completely removed to avoid collisions, and a new type: ClutterUnits should be added; the ability to install GObject properties using ClutterUnits should be maintained.
2009-06-03 10:12:09 +00:00
test-clutter-units.c \
[tests] Add a Group actor unit We need to test that the depth sorting of ClutterGroup works correctly in case we wish to change the data structure that stores the children, and do so without changing the default behaviour.
2009-08-25 16:55:51 +00:00
test-group.c \
[tests] Add initial sizing conformance test suite The size requisition and allocation mechanisms should be thoroughly tested to avoid unwanted regressions. For starters, we can test the explicit size setting and the side effects of calling clutter_actor_set_size().
2009-09-14 20:45:51 +00:00
test-actor-size.c \
Add a conformance test for clutter_texture_new_from_actor This contains four tests :- - A regular onscreen source with a clone next to it - An offscreen source with a clone. This is currently commented out because it no longer works. - An onscreen source with a rectangular clip and a clone. - An onscreen source with a clip from a path and a clone. The sources are all a 2x2 grid of colors. Each clone is tested that it either contains the color that should be at that grid position or that the stage color is showing through if the source is clipped.
2009-09-17 13:25:29 +00:00
test-texture-fbo.c \
cogl: Add a conformance test for sub textures This tests creating a sub texture from a larger texture using various different texture coordinates. It also tries to read back the texture data using cogl_texture_get_data.
2009-11-27 16:40:31 +00:00
test-cogl-sub-texture.c \
conform: Add the beginnings of a ClutterScript test suite ClutterScript is a very complicated piece of machinery, with a parser that has custom variations on top of the basic JSON format; it could also be extended in the future, so if we don't want to introduce regressions or break existing ClutterScript definitions, we'd better have a conformance test suite.
2009-11-04 11:50:45 +00:00
test-script-parser.c \
conform: Add test unit for the destruction of Containers Verify that internal children do not go through the remove() implementation, and that non-internal children do.
2009-12-18 23:29:11 +00:00
test-actor-destroy.c \
tests: Add an initial Behaviour conformance suite The coverage of the Behaviour sub-classes is currently abysmal. An initial test suite for Behaviours should at least verify that the accessors and the constructors are doing the right thing. This initial test suite just verifies the BehaviourOpacity sub-class, but it already bumps up the overall coverage by 2%.
2010-02-02 12:56:04 +00:00
test-behaviours.c \
animator: Provide a ClutterScript parser The whole point of having the Animator class is that the developer can describe a complex animation using ClutterScript. Hence, ClutterAnimator should hook into the Script machinery and parse a specific description format for its keys.
2010-02-08 15:52:18 +00:00
test-animator.c \
Merge the ClutterText actor Merge branch 'text-actor' * text-actor: (108 commits) Re-align ClutterText header file [text] Fix cursor sizing Comments and whitespace fixes to ClutterText [docs] Add newly added :single-line-mode accessors Update the ignore file [tests] Add text field interactive test [text] Add single-line-mode to ClutterText [text] Fix the deletion actions [text] Use cached length when possible [tests] Add unit for the ClutterText:password-char property [docs] Update the Text section [text] Coalesce text visibility and password character Allow localizations to change the text direction Clean up the update_pango_context() function Pass the PangoContext, not the MainContext Revert the logic of the PangoContext check Remove the binding pool entry from the list Remove BindingPool::list_actions() Add ClutterActor::create_pango_context() Rename the PangoContext creation functions ...
2009-01-07 12:06:33 +00:00
$(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 19:32:28 +00:00
# For convenience, this provides a way to easily run individual unit tests:
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
.PHONY: wrappers clean-wrappers
UNIT_TESTS = `./test-conformance -l -m thorough | $(GREP) '^/'`
[build] Do not rebuild the conformance tests scripts Make the build output a little bit cleaner by not re-creating the small shell scripts that allow launching the test units separately.
2009-05-14 07:32:46 +00:00
wrappers: stamp-test-conformance
@true
stamp-test-conformance: test-conformance$(EXEEXT)
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
@mkdir -p wrappers
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
@for i in $(UNIT_TESTS); \
do \
unit=`basename $$i | sed -e s/_/-/g`; \
[build] Split out the custom silent rules The silent rules we use for custom targets should be moved into a separate Makefile.am that gets included from all the others.
2009-09-16 16:43:58 +00:00
echo " GEN $$unit"; \
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
( echo "#!/bin/sh" ; echo "$(top_srcdir)/tests/conform/test-launcher.sh '$$i' \"\$$@\"" ) > $$unit$(EXEEXT) ; \
( echo "#!/bin/sh" ; echo "exec ./test-conformance$(EXEEXT) -p $$i \"\$$@\"" ) > wrappers/$$unit$(EXEEXT) ; \
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
chmod +x $$unit$(EXEEXT); \
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
chmod +x wrappers/$$unit$(EXEEXT); \
[build] Do not rebuild the conformance tests scripts Make the build output a little bit cleaner by not re-creating the small shell scripts that allow launching the test units separately.
2009-05-14 07:32:46 +00:00
done \
&& echo timestamp > $(@F)
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00: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 19:32:28 +00:00
do \
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
unit=`basename $$i | sed -e s/_/-/g`; \
[build] Split out the custom silent rules The silent rules we use for custom targets should be moved into a separate Makefile.am that gets included from all the others.
2009-09-16 16:43:58 +00:00
echo " RM $$unit"; \
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
rm -f $$unit$(EXEEXT) ; \
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
rm -f wrappers/$$unit$(EXEEXT) ; \
[build] Do not rebuild the conformance tests scripts Make the build output a little bit cleaner by not re-creating the small shell scripts that allow launching the test units separately.
2009-05-14 07:32:46 +00:00
done \
&& rm -f stamp-test-conformance
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
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 19:32:28 +00:00
# NB: BUILT_SOURCES here a misnomer. We aren't building source, just inserting
# a phony rule that will generate symlink scripts for running individual tests
BUILT_SOURCES = wrappers
[cogl-material] Support string based blending and layer combine descriptions Setting up layer combine functions and blend modes is very awkward to do programatically. This adds a parser for string based descriptions which are more consise and readable. E.g. a material layer combine function could now be given as: "RGBA = ADD (TEXTURE[A], PREVIOUS[RGB])" or "RGB = REPLACE (PREVIOUS)" "A = MODULATE (PREVIOUS, TEXTURE)" The simple syntax and grammar are only designed to expose standard fixed function hardware, more advanced combining must be done with shaders. This includes standalone documentation of blend strings covering the aspects that are common to blending and texture combining, and adds documentation with examples specific to the new cogl_material_set_blend() and cogl_material_layer_set_combine() functions. Note: The hope is to remove the now redundant bits of the material API before 1.0
2009-05-10 23:40:41 +00:00
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 11:47:09 +00:00
INCLUDES = \
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 19:32:28 +00:00
-I$(top_srcdir)/ \
-I$(top_srcdir)/clutter \
Intial Re-layout of the Cogl source code and introduction of a Cogl Winsys As part of an incremental process to have Cogl be a standalone project we want to re-consider how we organise the Cogl source code. Currently this is the structure I'm aiming for: cogl/ cogl/ <put common source here> winsys/ cogl-glx.c cogl-wgl.c driver/ gl/ gles/ os/ ? utils/ cogl-fixed cogl-matrix-stack? cogl-journal? cogl-primitives? pango/ The new winsys component is a starting point for migrating window system code (i.e. x11,glx,wgl,osx,egl etc) from Clutter to Cogl. The utils/ and pango/ directories aren't added by this commit, but they are noted because I plan to add them soon. Overview of the planned structure: * The winsys/ API is the API that binds OpenGL to a specific window system, be that X11 or win32 etc. Example are glx, wgl and egl. Much of the logic under clutter/{glx,osx,win32 etc} should migrate here. * Note there is also the idea of a winsys-base that may represent a window system for which there are multiple winsys APIs. An example of this is x11, since glx and egl may both be used with x11. (currently only Clutter has the idea of a winsys-base) * The driver/ represents a specific varient of OpenGL. Currently we have "gl" representing OpenGL 1.4-2.1 (mostly fixed function) and "gles" representing GLES 1.1 (fixed funciton) and 2.0 (fully shader based) * Everything under cogl/ should fundamentally be supporting access to the GPU. Essentially Cogl's most basic requirement is to provide a nice GPU Graphics API and drawing a line between this and the utility functionality we add to support Clutter should help keep this lean and maintainable. * Code under utils/ as suggested builds on cogl/ adding more convenient APIs or mechanism to optimize special cases. Broadly speaking you can compare cogl/ to OpenGL and utils/ to GLU. * clutter/pango will be moved to clutter/cogl/pango How some of the internal configure.ac/pkg-config terminology has changed: backendextra -> CLUTTER_WINSYS_BASE # e.g. "x11" backendextralib -> CLUTTER_WINSYS_BASE_LIB # e.g. "x11/libclutter-x11.la" clutterbackend -> {CLUTTER,COGL}_WINSYS # e.g. "glx" CLUTTER_FLAVOUR -> {CLUTTER,COGL}_WINSYS clutterbackendlib -> CLUTTER_WINSYS_LIB CLUTTER_COGL -> COGL_DRIVER # e.g. "gl" Note: The CLUTTER_FLAVOUR and CLUTTER_COGL defines are kept for apps As the first thing to take advantage of the new winsys component in Cogl; cogl_get_proc_address() has been moved from cogl/{gl,gles}/cogl.c into cogl/common/cogl.c and this common implementation first trys _cogl_winsys_get_proc_address() but if that fails then it falls back to gmodule.
2009-07-28 01:02:02 +00:00
-I$(top_srcdir)/clutter/cogl \
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 19:32:28 +00:00
-I$(top_builddir)/clutter \
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 11:47:09 +00:00
-I$(top_builddir)/clutter/cogl
test_conformance_CPPFLAGS = \
Disable single header inclusion for GLib In order to be ready for the next major version of GLib we need to disable single header inclusion by using the G_DISABLE_SINGLE_INCLUDES define in the build process.
2009-06-15 09:48:56 +00:00
-DG_DISABLE_SINGLE_INCLUDES \
build: Enable experimental COGL API in tests/conform Enable the experimental API when building the conformance test suite.
2010-02-15 11:58:55 +00:00
-DCOGL_ENABLE_EXPERIMENTAL_API \
build: Disable deprecated API in tests/conform We should not be using deprecated API in the conformance test suite.
2010-02-15 11:57:48 +00:00
-DCOGL_DISABLE_DEPRECATED \
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 11:47:09 +00:00
-DCLUTTER_DISABLE_DEPRECATED \
-DTESTS_DATADIR=\""$(top_srcdir)/tests/data"\"
build: Always build conformance tests with debug symbols Having the conformance test suite build without debug symbols doesn't make any sense.
2010-02-09 11:29:39 +00:00
test_conformance_CFLAGS = -g $(CLUTTER_CFLAGS) $(MAINTAINER_CFLAGS)
Split maintainer-flags from the compiler flags The maintainer compiler flags we use trigger warnings and errors in the autogenerated code that gtk-doc creates to scan the header and source files. Since we cannot control that, and we must run a distcheck with both --enable-gtk-doc and --enable-maintainer-flags turned on, we need to use less-strict compiler flags when inside the doc/reference subdirectories. The way to do this is to split the maintainer compiler flags into their own Makefile variable, called MAINTAINER_CFLAGS. The we can use $(MAINTAINER_CFLAGS) in the INCLUDES or _CFLAGS sections of each part of the source directories we wish to check with the anal retentiveness suited for maintainers.
2009-01-23 13:09:51 +00:00
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 11:47:09 +00:00
test_conformance_LDADD = $(top_builddir)/clutter/libclutter-@CLUTTER_WINSYS@-@CLUTTER_API_VERSION@.la $(CLUTTER_LIBS)
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 19:32:28 +00:00
script: Allow parsing child properties The ClutterScript parser needs to be extended to parse child properties and apply them after an actor has been added to a container. In order to distinguish child properties from regular GObject properties we can use the "child::" prefix, e.g.: { "type" : "ClutterRectangle", "id" : "child-01", "child::has-focus" : true, ... } Parsing child properties can be deferred to the ClutterScriptable interface, just like regular properties.
2009-11-04 16:45:44 +00:00
test_conformance_LDFLAGS = -rdynamic
Add a wrapper library to help testing without NPOTs. * tests/tools/Makefile.am: Optionally build the libdisable-npots.la library depending on whether libdl was detected in the configure script. A helper script is also generated to setup the LD_PRELOAD. * tests/conform/Makefile.am: There are now two versions of the test-report and full-report rules. test-report-normal is the same as before and test-report-disable-npots runs the tests with the disable-npots wrapper script. The full-report rule runs both of them and displays two separate HTML files. The test-report rule just runs the normal version as before. * configure.ac: Add a test for libdl * tests/tools/disable-npots.sh.in: New file. Template for the helper script * tests/tools/disable-npots.c: New file
2008-11-24 15:44:16 +00:00
.PHONY: test
.PHONY: test-report test-report-normal test-report-disable-npots
.PHONY: full-report full-report-normal full-report-disable-npots
.PHONY: full-report-generate
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
test: wrappers
@$(top_srcdir)/tests/conform/run-tests.sh \
./test-conformance$(EXEEXT) test-conformance-results.xml
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 19:32:28 +00:00
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
test-verbose: wrappers
@$(top_srcdir)/tests/conform/run-tests.sh \
./test-conformance$(EXEEXT) test-conformance-results.xml --verbose
Uniformly use floats in Actor properties All the underlying implementation and the public entry points have been switched to floats; the only missing bits are the Actor properties that deal with positioning and sizing. This usually means a major pain when dealing with GValues and varargs functions. While GValue will warn you when dealing with the wrong conversions, varags will simply die an horrible (and hard to debug) death via segfault. Nothing much to do here, except warn people in the release notes and hope for the best.
2009-05-31 14:15:46 +00:00
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
test-report-normal: wrappers
@$(top_srcdir)/tests/conform/run-tests.sh \
./test-conformance$(EXEEXT) test-conformance-results.xml -k \
Add a wrapper library to help testing without NPOTs. * tests/tools/Makefile.am: Optionally build the libdisable-npots.la library depending on whether libdl was detected in the configure script. A helper script is also generated to setup the LD_PRELOAD. * tests/conform/Makefile.am: There are now two versions of the test-report and full-report rules. test-report-normal is the same as before and test-report-disable-npots runs the tests with the disable-npots wrapper script. The full-report rule runs both of them and displays two separate HTML files. The test-report rule just runs the normal version as before. * configure.ac: Add a test for libdl * tests/tools/disable-npots.sh.in: New file. Template for the helper script * tests/tools/disable-npots.c: New file
2008-11-24 15:44:16 +00:00
&& ( gtester-report test-conformance-results.xml \
| sed 's/>GTester Unit Test Report</>GTester Unit Test Report (normal)</' \
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
> test-conformance-results.html ) \
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 19:32:28 +00:00
&& gnome-open ./test-conformance-results.html
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
test-report-disable-npots: wrappers
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
@../tools/disable-npots.sh \
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
$(top_srcdir)/tests/conform/run-tests.sh \
./test-conformance$(EXEEXT) test-conformance-results-dn.xml -k \
Add a wrapper library to help testing without NPOTs. * tests/tools/Makefile.am: Optionally build the libdisable-npots.la library depending on whether libdl was detected in the configure script. A helper script is also generated to setup the LD_PRELOAD. * tests/conform/Makefile.am: There are now two versions of the test-report and full-report rules. test-report-normal is the same as before and test-report-disable-npots runs the tests with the disable-npots wrapper script. The full-report rule runs both of them and displays two separate HTML files. The test-report rule just runs the normal version as before. * configure.ac: Add a test for libdl * tests/tools/disable-npots.sh.in: New file. Template for the helper script * tests/tools/disable-npots.c: New file
2008-11-24 15:44:16 +00:00
&& ( gtester-report test-conformance-results-dn.xml \
| sed 's/>GTester Unit Test Report</>GTester Unit Test Report (no NPOTs)</' \
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
> test-conformance-results-dn.html ) \
Add a wrapper library to help testing without NPOTs. * tests/tools/Makefile.am: Optionally build the libdisable-npots.la library depending on whether libdl was detected in the configure script. A helper script is also generated to setup the LD_PRELOAD. * tests/conform/Makefile.am: There are now two versions of the test-report and full-report rules. test-report-normal is the same as before and test-report-disable-npots runs the tests with the disable-npots wrapper script. The full-report rule runs both of them and displays two separate HTML files. The test-report rule just runs the normal version as before. * configure.ac: Add a test for libdl * tests/tools/disable-npots.sh.in: New file. Template for the helper script * tests/tools/disable-npots.c: New file
2008-11-24 15:44:16 +00:00
&& gnome-open ./test-conformance-results-dn.html
test-report: test-report-normal
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
full-report-normal: wrappers
@$(top_srcdir)/tests/conform/run-tests.sh \
./test-conformance$(EXEEXT) test-conformance-results.xml -k -m=slow \
Add a wrapper library to help testing without NPOTs. * tests/tools/Makefile.am: Optionally build the libdisable-npots.la library depending on whether libdl was detected in the configure script. A helper script is also generated to setup the LD_PRELOAD. * tests/conform/Makefile.am: There are now two versions of the test-report and full-report rules. test-report-normal is the same as before and test-report-disable-npots runs the tests with the disable-npots wrapper script. The full-report rule runs both of them and displays two separate HTML files. The test-report rule just runs the normal version as before. * configure.ac: Add a test for libdl * tests/tools/disable-npots.sh.in: New file. Template for the helper script * tests/tools/disable-npots.c: New file
2008-11-24 15:44:16 +00:00
&& ( gtester-report test-conformance-results.xml \
| sed 's/>GTester Unit Test Report</>GTester Unit Test Report (normal)</' \
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
> test-conformance-results.html )
Add a wrapper library to help testing without NPOTs. * tests/tools/Makefile.am: Optionally build the libdisable-npots.la library depending on whether libdl was detected in the configure script. A helper script is also generated to setup the LD_PRELOAD. * tests/conform/Makefile.am: There are now two versions of the test-report and full-report rules. test-report-normal is the same as before and test-report-disable-npots runs the tests with the disable-npots wrapper script. The full-report rule runs both of them and displays two separate HTML files. The test-report rule just runs the normal version as before. * configure.ac: Add a test for libdl * tests/tools/disable-npots.sh.in: New file. Template for the helper script * tests/tools/disable-npots.c: New file
2008-11-24 15:44:16 +00:00
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
full-report-disable-npots: wrappers
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
@../tools/disable-npots.sh \
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
$(top_srcdir)/tests/conform/run-tests.sh \
./test-conformance$(EXEEXT) test-conformance-results-dn.xml -k -m=slow \
Add a wrapper library to help testing without NPOTs. * tests/tools/Makefile.am: Optionally build the libdisable-npots.la library depending on whether libdl was detected in the configure script. A helper script is also generated to setup the LD_PRELOAD. * tests/conform/Makefile.am: There are now two versions of the test-report and full-report rules. test-report-normal is the same as before and test-report-disable-npots runs the tests with the disable-npots wrapper script. The full-report rule runs both of them and displays two separate HTML files. The test-report rule just runs the normal version as before. * configure.ac: Add a test for libdl * tests/tools/disable-npots.sh.in: New file. Template for the helper script * tests/tools/disable-npots.c: New file
2008-11-24 15:44:16 +00:00
&& ( gtester-report test-conformance-results-dn.xml \
| sed 's/>GTester Unit Test Report</>GTester Unit Test Report (no NPOTs)</' \
[tests] Create a real file for each test unit Currently, the conformance test suite creates symbolic links pointing to a wrapper script that just parses the name used to invoke it and calls the gtester with the correct path. Unfortunately, this presents two issues: - it does not really work on file systems that do not support symbolic links - it leaves behind the symbolic links, which cannot be automatically cleaning by 'make clean' Both can be solved by creating a small script that invokes the wrapper one with the test unit path. The Makefile will use test-conform to extract the unit test paths and generate a list that will be iterated over to create the executable name (using the "test-name" convention also used by the interactive tests, instead of "test_name"); the executable is then just a simple shell script that invokes the wrapper script passing the unit test path on the command line. The wrapper script will use the first argument to work correctly, so it could be simply executed like: ./test-wrapper.sh /path/to/unit_test Which is another improvement over the current implementation, where the wrapper script does not work when invoked directly.
2008-12-17 13:59:56 +00:00
> test-conformance-results-dn.html )
Add a wrapper library to help testing without NPOTs. * tests/tools/Makefile.am: Optionally build the libdisable-npots.la library depending on whether libdl was detected in the configure script. A helper script is also generated to setup the LD_PRELOAD. * tests/conform/Makefile.am: There are now two versions of the test-report and full-report rules. test-report-normal is the same as before and test-report-disable-npots runs the tests with the disable-npots wrapper script. The full-report rule runs both of them and displays two separate HTML files. The test-report rule just runs the normal version as before. * configure.ac: Add a test for libdl * tests/tools/disable-npots.sh.in: New file. Template for the helper script * tests/tools/disable-npots.c: New file
2008-11-24 15:44:16 +00:00
Split maintainer-flags from the compiler flags The maintainer compiler flags we use trigger warnings and errors in the autogenerated code that gtk-doc creates to scan the header and source files. Since we cannot control that, and we must run a distcheck with both --enable-gtk-doc and --enable-maintainer-flags turned on, we need to use less-strict compiler flags when inside the doc/reference subdirectories. The way to do this is to split the maintainer compiler flags into their own Makefile variable, called MAINTAINER_CFLAGS. The we can use $(MAINTAINER_CFLAGS) in the INCLUDES or _CFLAGS sections of each part of the source directories we wish to check with the anal retentiveness suited for maintainers.
2009-01-23 13:09:51 +00:00
XML_REPORTS = test-conformance-results.xml
HTML_REPORTS = test-conformance-results.html
Add a wrapper library to help testing without NPOTs. * tests/tools/Makefile.am: Optionally build the libdisable-npots.la library depending on whether libdl was detected in the configure script. A helper script is also generated to setup the LD_PRELOAD. * tests/conform/Makefile.am: There are now two versions of the test-report and full-report rules. test-report-normal is the same as before and test-report-disable-npots runs the tests with the disable-npots wrapper script. The full-report rule runs both of them and displays two separate HTML files. The test-report rule just runs the normal version as before. * configure.ac: Add a test for libdl * tests/tools/disable-npots.sh.in: New file. Template for the helper script * tests/tools/disable-npots.c: New file
2008-11-24 15:44:16 +00:00
if HAVE_LIBDL
Split maintainer-flags from the compiler flags The maintainer compiler flags we use trigger warnings and errors in the autogenerated code that gtk-doc creates to scan the header and source files. Since we cannot control that, and we must run a distcheck with both --enable-gtk-doc and --enable-maintainer-flags turned on, we need to use less-strict compiler flags when inside the doc/reference subdirectories. The way to do this is to split the maintainer compiler flags into their own Makefile variable, called MAINTAINER_CFLAGS. The we can use $(MAINTAINER_CFLAGS) in the INCLUDES or _CFLAGS sections of each part of the source directories we wish to check with the anal retentiveness suited for maintainers.
2009-01-23 13:09:51 +00:00
XML_REPORTS += test-conformance-results-dn.xml
HTML_REPORTS += test-conformance-results-dn.html
Add a wrapper library to help testing without NPOTs. * tests/tools/Makefile.am: Optionally build the libdisable-npots.la library depending on whether libdl was detected in the configure script. A helper script is also generated to setup the LD_PRELOAD. * tests/conform/Makefile.am: There are now two versions of the test-report and full-report rules. test-report-normal is the same as before and test-report-disable-npots runs the tests with the disable-npots wrapper script. The full-report rule runs both of them and displays two separate HTML files. The test-report rule just runs the normal version as before. * configure.ac: Add a test for libdl * tests/tools/disable-npots.sh.in: New file. Template for the helper script * tests/tools/disable-npots.c: New file
2008-11-24 15:44:16 +00:00
full-report-generate: full-report-normal full-report-disable-npots
else
full-report-generate: full-report-normal
endif
full-report: full-report-generate
Split maintainer-flags from the compiler flags The maintainer compiler flags we use trigger warnings and errors in the autogenerated code that gtk-doc creates to scan the header and source files. Since we cannot control that, and we must run a distcheck with both --enable-gtk-doc and --enable-maintainer-flags turned on, we need to use less-strict compiler flags when inside the doc/reference subdirectories. The way to do this is to split the maintainer compiler flags into their own Makefile variable, called MAINTAINER_CFLAGS. The we can use $(MAINTAINER_CFLAGS) in the INCLUDES or _CFLAGS sections of each part of the source directories we wish to check with the anal retentiveness suited for maintainers.
2009-01-23 13:09:51 +00:00
@for x in $(HTML_REPORTS); do \
Add a wrapper library to help testing without NPOTs. * tests/tools/Makefile.am: Optionally build the libdisable-npots.la library depending on whether libdl was detected in the configure script. A helper script is also generated to setup the LD_PRELOAD. * tests/conform/Makefile.am: There are now two versions of the test-report and full-report rules. test-report-normal is the same as before and test-report-disable-npots runs the tests with the disable-npots wrapper script. The full-report rule runs both of them and displays two separate HTML files. The test-report rule just runs the normal version as before. * configure.ac: Add a test for libdl * tests/tools/disable-npots.sh.in: New file. Template for the helper script * tests/tools/disable-npots.c: New file
2008-11-24 15:44:16 +00:00
gnome-open "$$x"; \
done
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 19:32:28 +00:00
conform: Make gtester run a list of wrappers Instead of asking gtester to run ./test-conformance directly we now tell it to run a list of wrapper scripts. This results in each test being spawned in a separate process avoiding leakage of state between tests which has been a big problem with the conformance tests for quite a while now.
2010-05-06 13:53:50 +00:00
EXTRA_DIST = ADDING_NEW_TESTS test-launcher.sh run-tests.sh
Split maintainer-flags from the compiler flags The maintainer compiler flags we use trigger warnings and errors in the autogenerated code that gtk-doc creates to scan the header and source files. Since we cannot control that, and we must run a distcheck with both --enable-gtk-doc and --enable-maintainer-flags turned on, we need to use less-strict compiler flags when inside the doc/reference subdirectories. The way to do this is to split the maintainer compiler flags into their own Makefile variable, called MAINTAINER_CFLAGS. The we can use $(MAINTAINER_CFLAGS) in the INCLUDES or _CFLAGS sections of each part of the source directories we wish to check with the anal retentiveness suited for maintainers.
2009-01-23 13:09:51 +00:00
Clean up the test reports Since we override the clean-generic target in order to remove the shell scripts we create for each conformance test unit, we cannot use CLEANFILES to remove the test reports.
2009-01-23 13:29:55 +00:00
# we override the clean-generic target to clean up the wrappers so
# we cannot use CLEANFILES
clean-generic: clean-wrappers
[build] Split out the custom silent rules The silent rules we use for custom targets should be moved into a separate Makefile.am that gets included from all the others.
2009-09-16 16:43:58 +00:00
$(QUIET_RM)rm -f $(XML_REPORTS) $(HTML_REPORTS)
Reference in New Issue Copy Permalink