Skip to content

Ideas for tests to add during Outreachy

We are submitting an Outreachy project proposal for adding more end-to-end tests of GNOME OS.

The idea is to add tests for specific functionality in the Shell and core apps: Settings, Nautilus, and everything else. Currently, each core app has a single "Does it launch?" test and nothing more.

The plan is that end-to-end tests for a module should live in that module's source tree and that module's CI pipelines. That is not ready yet. This issue is about adding app-specific tests to https://gitlab.gnome.org/GNOME/openqa-tests, which can be migrated to the module source tree later when that becomes possible.

We should prioritize adding tests to modules where the developers and/or maintainers are actively interested in having end-to-end this testing.

Here's a list of all modules we can currently test, grouped roughly by module development team. Tick when we have spoken to the development team and have a corresponding issue listing ideas for specific test cases.

  • Baobab
  • Calculator
  • Calendar
  • Characters
  • Clocks
  • Connections
  • Console
  • Desktop search (Tracker/Tracker Miners) - @sthursfield is interested - #8
  • Disk Utility
  • Epiphany
  • Evince - @pabloyoyoista is interested - #47
  • Font Viewer - not discussed with dev team - #44
  • Logs
  • Loupe
  • Maps
  • Music
  • Nautilus - @antoniof is interested, more once they can live in the Nautilus sourcetree - #48
  • Settings
  • Shell/Mutter - not discussed with dev team - #34
  • Simple Scan
  • Snapshot
  • Software
  • System Monitor
  • Totem
  • Tour
  • Weather
  • Yelp

For completeness, here are other testsuites we can work on during Outreachy which don't correspond so neatly to one module:

Another useful task could be: view the journal logs during the tests, for any warning or error that you see, report and fix it in the corresponding app/library project

Edited by Sam Thursfield