Re: New GnomeGoal proposal: InstalledTests

So, two weeks later.  A quick status update on prototyping this:

First, I converted gjs to have an "installed-tests" subdirectory:

That worked, however I got some pushback:

Meanwhile, I tried doing this for both glib:
and GTK+:

Of those, the glib patches are unreviewed as of yet (but work in local
testing).  Much more exciting is that I now have the GTK+ reftests under
automation; they run after every build, and I'm taking screenshots along
the way:

(I manually saved that particular task run, otherwise it'd eventually be
rotated out by later integration test runs)

I also converted the ostree tests to be installed:

So, is this useful and worth the additional maintenance as a different
option from "make check"?  I strongly believe so.  For the core modules
like glib/gtk+, it definitely felt conclusive from this thread that we
should keep "make check" working.  Sometimes that was quite un-obvious
and tricky, and so for "my" module ostree I decided to just burn the
bridges and have the tests only work installed.

Next steps:

* Add --enable-installed-tests to jhbuild
* Teach Debian's Autopkgtest how to run these
* Improve gnome-desktop-testing's runner binary "gnome-desktop-testing-runner"
* More tests.  More!

The specification is still open to revision of course too.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]