Merge lp://staging/~dholbach/ubuntu-packaging-guide/autopkgtest into lp://staging/ubuntu-packaging-guide
Proposed by
Daniel Holbach
| Status: | Merged |
|---|---|
| Merged at revision: | 171 |
| Proposed branch: | lp://staging/~dholbach/ubuntu-packaging-guide/autopkgtest |
| Merge into: | lp://staging/ubuntu-packaging-guide |
| Diff against target: |
141 lines (+126/-0) 2 files modified
ubuntu-packaging-guide/auto-pkg-test.rst (+125/-0) ubuntu-packaging-guide/index.rst (+1/-0) |
| To merge this branch: | bzr merge lp://staging/~dholbach/ubuntu-packaging-guide/autopkgtest |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Martin Pitt | Approve | ||
| Ubuntu Packaging Guide Team | Pending | ||
|
Review via email:
|
|||
To post a comment you must log in.
Revision history for this message
| Martin Pitt (pitti) wrote | # |
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
Thanks so much for adding this!
One issue:
+* The `gtk+3.0 tests`_ do two things: firstly they run the upstream
+ test-suite as part of ``autopkgtest``. Secondly they execute a python
+ program using ``xvfb`` to emulate a running X session.
That's not quite true, the upstream tests are currently only run during package build. Somethign like this:
* The `gtk+3.0 tests`_ also do a compile/link/run check in the "build" test. There is an additional "python3-gi" test which verifies that the GTK library can also be used through introspection.
+While Debian does not have an automatic testing infrastructure set up yet, it
+makes a lot of sense to forward ``autopkgtest`` changes to Debian as well.
Perhaps "... yet, they should still be submitted to Debian, as DEP-8 is a Debian specification and Debian developers or users can still manually run the tests."