Ubuntu

GNOME upstream testing

Registered by Martin Pitt

In 12.04 we started to add tests to GNOME upstream (gvfs, preparing gnome-settings-daemon tests, etc.). Continue this initiative and discuss which components would benefit most from automatic test cases.

Blueprint information

Status:
Complete
Approver:
Gema Gomez
Priority:
Medium
Drafter:
Martin Pitt
Direction:
Approved
Assignee:
Canonical Platform QA Team
Definition:
Approved
Series goal:
Accepted for raring
Implementation:
Implemented
Milestone target:
milestone icon ubuntu-13.04-beta-1
Started by
Martin Pitt
Completed by
Martin Pitt

Related branches

Sprints

Whiteboard

Options for jhbuild failure notifications:
- mailing individual maintainers about regressions might seem unfriendly, and sometimes you really need to make the corresponding change to other modules
- one big mailing list with all failures, and machine parseable headers for module/test
- compromise for daily testing until we have by-commit: email the modules maintainers from both the changed and the broken module

desrt is working on a "jhbuild to go" which outputs the resulting binaries in an OSTree-like fashion

pitti, 2013-01-18: Dropping "suspend on lid close" test for g-s-d, as this moved to logind.

(?)

Work Items

Work items for ubuntu-13.04-beta-1:
[pitti] Agree with gnome-settings-daemon upstream about how tests should look like: DONE
[pitti] Write gnome-settings-daemon power plugin tests (suspend after configured idle time, suspend after low-on-battery, handling of multiple batteries) : DONE
[pitti] Write gnome-settings-daemon keyboard plugin tests (multiple keyboard layouts, changing them in gsettings gets propagated to X, a configured compose key works, etc.): POSTPONED
[pitti] If we can mock/simulate monitors, write g-s-d xrandr plugin test cases for multipe monitor handling: POSTPONED
[pitti] Get the full gvfs test suite (gvfs-testbed) upstream: DONE
[pitti] Write a gvfs upstream test which reproduces an existing bug (#667641, #686798): DONE
[pitti] Extend gvfs upstream tests to cover the Gio API, not just the CLI programs: DONE
[pitti] Add gvfs upstream test to cover trash: DONE
[pitti] announce jhbuild @ jenkins.ubuntu to desktop-devel-list@, propose/discuss different notification modes: DONE
[pitti] write standard tool to run your program and iterate through all menu items / buttons, checking that it does not crash and changes some state: POSTPONED
[desrt] write standard tool to iterate through GActionGroup on the session D-BUS: POSTPONED
[desrt] get gcov macros into gnome-common: DONE

Work items for ubuntu-13.04-month-6:
[jibel] implement jhbuild failure notifications, subscriptions: DONE
[jibel] Allow the server to send notifications (RT60258): BLOCKED

Dependency tree

* Blueprints in grey have been implemented.

Nearby

This blueprint contains Public information 
Everyone can see this information.