Merge lp:~ken-vandine/content-hub/url-dispatcher-tests into lp:content-hub
| Status: | Merged |
|---|---|
| Approved by: | Michael Sheldon on 2015-06-09 |
| Approved revision: | 216 |
| Merged at revision: | 215 |
| Proposed branch: | lp:~ken-vandine/content-hub/url-dispatcher-tests |
| Merge into: | lp:content-hub |
| Diff against target: |
99 lines (+52/-4) 5 files modified
debian/tests/control (+1/-1) debian/tests/url-dispatcher (+40/-0) tests/peers/importer/autoimporter.cpp (+4/-1) tests/peers/sharer/autosharer.cpp (+4/-1) tools/send/autoexporter.cpp (+3/-1) |
| To merge this branch: | bzr merge lp:~ken-vandine/content-hub/url-dispatcher-tests |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michael Sheldon (community) | 2015-06-04 | Approve on 2015-06-09 | |
| PS Jenkins bot | continuous-integration | Approve on 2015-06-05 | |
|
Review via email:
|
|||
Commit Message
Make the import and share testability peers return 1 if the transfer is aborted.
Added url-dispatcher autopkgtest.
Description of the Change
Make the import and share testability peers return 1 if the transfer is aborted.
Added url-dispatcher autopkgtest.
| Ken VanDine (ken-vandine) wrote : | # |
Are there any related MPs required for this MP to build/function as expected? Please list.
* No
Is your branch in sync with latest trunk (e.g. bzr pull lp:trunk -> no changes)
* Yes
Did you perform an exploratory manual test run of your code change and any related functionality on device or emulator?
* Yes I did, however the changes are all testing related
Did you successfully run all tests found in your component's Test Plan (https:/
* Yes
If you changed the UI, was the change specified/approved by design?
* No change
If you changed UI labels, did you update the pot file?
* No change
If you changed the packaging (debian), did you add a core-dev as a reviewer to this MP?
* I'm a core-dev, added autopkgtests
| Michael Sheldon (michael-sheldon) wrote : | # |
It might be nice to have a test that tries to export a file:// URI (with the expectation that it fails), to ensure no change accidentally enables that in the future.
| Michael Sheldon (michael-sheldon) wrote : | # |
dobey had a couple of comments on IRC:
<dobey> dbus itself doesn't require X, and i don't think the other commands being used do either
<dobey> would probably be better if each test was pulled out to individual tests, and they were run using dbus-test-runner or similar
<dobey> this level of integration testing could probably also be run during the build of the package as well
- 216. By Ken VanDine on 2015-06-05
-
Added autopkgtest to verify that file uris are rejected from url-dispatcher
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:216
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Michael Sheldon (michael-sheldon) wrote : | # |
Did you perform an exploratory manual test run of the code change and any related functionality on device or emulator?
* Yes (tested new autopkgtests with adt-run)
Did CI run pass? If not, please explain why.
* Yes
Have you checked that submitter has accurately filled out the submitter checklist and has taken no shortcut?
* Yes

PASSED: Continuous integration, rev:215 jenkins. qa.ubuntu. com/job/ content- hub-ci/ 258/ jenkins. qa.ubuntu. com/job/ content- hub-vivid- amd64-ci/ 54 jenkins. qa.ubuntu. com/job/ content- hub-vivid- armhf-ci/ 54 jenkins. qa.ubuntu. com/job/ content- hub-vivid- armhf-ci/ 54/artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ content- hub-vivid- i386-ci/ 54
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/content- hub-ci/ 258/rebuild
http://