After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 721818 - generating and extending InstalledTests
generating and extending InstalledTests
Status: RESOLVED OBSOLETE
Product: gnome-continuous
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Continuous maintainer(s)
GNOME Continuous maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-01-08 19:18 UTC by Colin Walters
Modified: 2021-06-05 16:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Store test results in a separate dir (1.03 KB, patch)
2014-02-20 16:04 UTC, Vadim Rutkovsky
none Details | Review
Store results in installed-test-results dir in workdir (2.97 KB, patch)
2014-04-10 16:16 UTC, Vadim Rutkovsky
committed Details | Review

Description Colin Walters 2014-01-08 19:18:21 UTC
Right now we have a custom "applicationtest" that starts/stop each app.

I've been thinking lately though that InstalledTests has been so successful as a framework that I'd like to push more testing that way.

We could add some code that *generates* InstalledTests.  For example, we could statically inspect the disk, loop over /usr/share/applications, and generate a test named:

gnome-continuous/${appname}/start-stop

The reason I mention this is Matthias specifically mentioned RTL as something that we should test.  It'd be easy then to do:

gnome-continuous/${appname}/start-stop-rtl

Or perhaps we want to boot the whole OS with LANG=he_IL.UTF-8?

We could also generate many other types of tests.  Say that we had a test that entered/exited the shell overview.  We could run that test at different resolutions too.
Comment 1 Colin Walters 2014-01-08 19:27:33 UTC
InstalledTests could use two new features:

* The ability to request a screenshot (likely custom to Continuous for now)
* A way to export test result data; for example, if an installed test creates a directory "test-results", we grab that from the guest.
Comment 2 Matthias Clasen 2014-01-08 19:31:03 UTC
as mentioned in the discussion, having a screenshot api and a way to export test results (including those shots) would be very useful to just generate more screenshots, so we can get more than just the initial screen - it could be combined with a11y-driven tests that 'click through' some of the app ui.
Comment 3 Vadim Rutkovsky 2014-02-20 16:04:51 UTC
Created attachment 269815 [details] [review]
Store test results in a separate dir
Comment 4 Vadim Rutkovsky 2014-04-10 16:16:03 UTC
Created attachment 274008 [details] [review]
Store results in installed-test-results dir in workdir
Comment 5 Vadim Rutkovsky 2014-04-21 22:50:12 UTC
(In reply to comment #4)
> Created an attachment (id=274008) [details] [review]
> Store results in installed-test-results dir in workdir

This patch also solves test failures (Child process killed by signal 13), which happen due to ratelimiting being off. After it gets applied we can update the UI to turn failed test names into a links to a test logs
Comment 6 Colin Walters 2014-04-22 20:33:46 UTC
Review of attachment 274008 [details] [review]:

Cool, this looks good to me.
Comment 8 André Klapper 2021-06-05 16:29:36 UTC
gnome-continuous is not under active development anymore. Its codebase has been archived: https://gitlab.gnome.org/Archive/gnome-continuous

Closing all its open tickets as part of housekeeping.