Add tests for gdbus-codegen
Currently, the tests for gdbus-codegen
are all tied up in the build system, as a series of custom uninstalled targets which run gdbus-codegen
with various inputs and options.
It would be better if we had a gdbus-codegen.py
test program, like we have gobject/tests/mkenums.py
. Then we could build a proper test harness around gdbus-codegen
, and perform more comprehensive checks on the code it generates (rather than just “do gdbus-codegen
and gcc
report success with these options and this input file). It would also make the gdbus-codegen
tests easier to run individually, and allow them to be run as installed-tests.
Particular things to test:
- Order of input files doesn’t matter (reproducible builds)
- (list other things here)
Edited by Philip Withnall