summaryrefslogtreecommitdiff
path: root/tests/gi-tester
Commit message (Collapse)AuthorAgeFilesLines
* gi-test: Fix gir file testsChun-wei Fan2019-05-021-1/+1
| | | | | | | | | | | | | | | | | | | Meson unfortunately does not normalize the paths for us, so we couldn't just rely on it to give us the correct target name without the full target path when the path separator is not '/' (such as on Visual Studio builds, where the path separator is '\\' (with escape character). This means that, that on Visual Studio builds, targetname would be: D:\\gi.build\\tests\\scanner\\Typedefs-1.0.gir instead of: Typedefs-1.0.gir Since we have the targetbase variable which actually has the correct info we need, use that to deduce the correct reference .gir file to compare to.
* build: extend PYTHONPATH instead of replacing it. Fixes #126Christoph Reiter2018-12-191-1/+2
| | | | So we don't ignore any PYTHONPATH set by the user.
* gi-tester: Port to PythonChristoph Reiter2018-07-221-60/+121
| | | | | | Removes the dependency on bash there, so we can potentially use it on Windows as well. Not integrated with meson yet, but will hopefully make it easier to do so.
* tests: Ignore platform-dependent field in test resultsPhilip Chimento2018-03-271-2/+7
| | | | | | | | | The "shared-library" field of the GIR is platform-dependent, since shared libraries have different names on different platforms. For example, on OS X, the field refers to a .dylib rather than a .so. We ignore this field when comparing the expected output with the generated output. See #139.
* Replace GNU -B extension with a more portable -I equivalentJasper Lievisse Adriaanse2016-04-261-4/+4
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=765618
* gi-tester: Don't use negative substring parametersDavide Bertola2014-02-131-1/+3
| | | | Bash from OSX 10.9 seems not to support them.
* tests: Remove debug echo from gi-testerSimon Feltman2014-01-041-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=721477
* tests: Update GI to use parallel test harnessSimon Feltman2014-01-041-1/+1
| | | | | | | | There was some dependence on the serial test harness in the recent tests that were added. Update GI to use the parallel test harness to avoid incompatibilities. https://bugzilla.gnome.org/show_bug.cgi?id=721477
* tests: Update Python stanza to change directories before running testsSimon Feltman2014-01-021-3/+5
| | | | | | | | Ensure PYTHONPATH uses absolute paths for top_builddir and top_srcdir. Use pushd/popd before and after running tests with "python -m unittest...". This ensures TESTARGS can be used from within a vpath build directory. https://bugzilla.gnome.org/show_bug.cgi?id=720713
* tests: Use Python unittest module parameterization for annotationparserSimon Feltman2013-12-291-1/+13
| | | | | | | | | | | | | | Add Python unittest module parameterization support to gi-tester through the use of a "TESTARGS" variable. Use the Automake test harness along with gi-tester for running the Python annotationparser tests. Add tests/scanner/annotationparser/Makefile.am and localize testing rules and EXTRA_DIST setup to this file. Specific Python tests can now be run as follows: cd tests/scanner/annotationparser make check TESTS=test_patterns.py TESTARGS=TestTagValueStability https://bugzilla.gnome.org/show_bug.cgi?id=720713
* tests: Use Automake test harness for scanner diff testsSimon Feltman2013-12-291-0/+39
Add gi-tester script for dispatching various scanner diff tests based on their target suffix. Hook the dispatcher script into the Automake test harness which is passed the diff test target name. Remove usage of check-local which is always run regardless of whether or not the TESTS variable is set from the command line. This allows for both the ability to use the harnesses XFAIL_TESTS variable for expected failures as well as testing of targets individually, for example: cd tests/scanner make check TESTS=GtkFrob-1.0.gir make check TESTS=Regress-1.0-Python Add Headeronly-1.0-expected.gir for validating the results of the header only gir creation test. https://bugzilla.gnome.org/show_bug.cgi?id=720713
View Lorry Controller Status