Merge lp:~alan-griffiths/mir/introducing-mir_test_framework-main into lp:mir
| Status: | Merged |
|---|---|
| Approved by: | Alan Griffiths on 2015-06-26 |
| Approved revision: | 2706 |
| Merged at revision: | 2707 |
| Proposed branch: | lp:~alan-griffiths/mir/introducing-mir_test_framework-main |
| Merge into: | lp:mir |
| Diff against target: |
129 lines (+83/-5) 4 files modified
include/test/mir_test_framework/main.h (+43/-0) tests/mir_test_framework/CMakeLists.txt (+1/-0) tests/mir_test_framework/command_line_server_configuration.cpp (+9/-5) tests/mir_test_framework/main.cpp (+30/-0) |
| To merge this branch: | bzr merge lp:~alan-griffiths/mir/introducing-mir_test_framework-main |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Approve on 2015-06-26 | |
| Alexandros Frantzis (community) | 2015-06-25 | Approve on 2015-06-26 | |
|
Review via email:
|
|||
Commit Message
tests: make it simple for a libmir-
Description of the Change
tests: make it simple for a libmir-
| Alexandros Frantzis (afrantzis) wrote : | # |
Although a step in the right direction, I think this approach is still too restrictive; we are still forcing *our* way of running the tests, allowing no alternative. For example, this approach doesn't allow users to set some custom googletest behavior, like event handlers.
We should provide a way for users to use our infrastructure independently of any particular (google)test initialization. Since the only prerequisite for using the infrastructure is setting up the test server command line, we would just need to offer an mtf::init() or similar function.
I don't mind offering a convenience mtf::main() as this branch does (but I don't think it's necessary either), but that should be in addition to an mtf::init() type function.
Need discussion
- 2706. By Alan Griffiths on 2015-06-26
-
Even finer grained control of test initialization
| PS Jenkins bot (ps-jenkins) wrote : | # |
PASSED: Continuous integration, rev:2706
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://

PASSED: Continuous integration, rev:2705 jenkins. qa.ubuntu. com/job/ mir-ci/ 4200/ jenkins. qa.ubuntu. com/job/ mir-android- vivid-i386- build/2999 jenkins. qa.ubuntu. com/job/ mir-clang- wily-amd64- build/516 jenkins. qa.ubuntu. com/job/ mir-mediumtests -vivid- touch/2947 jenkins. qa.ubuntu. com/job/ mir-wily- amd64-ci/ 356 jenkins. qa.ubuntu. com/job/ mir-wily- amd64-ci/ 356/artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ mir-mediumtests -builder- vivid-armhf/ 2947 jenkins. qa.ubuntu. com/job/ mir-mediumtests -builder- vivid-armhf/ 2947/artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ mir-mediumtests -runner- mako/5765 s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 21486
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/mir- ci/4200/ rebuild
http://