Merge lp:~alan-griffiths/miral/first-cut-at-test-server into lp:miral
Proposed by
Alan Griffiths
on 2016-08-11
| Status: | Merged |
|---|---|
| Approved by: | Gerry Boland on 2016-08-12 |
| Approved revision: | 271 |
| Merged at revision: | 272 |
| Proposed branch: | lp:~alan-griffiths/miral/first-cut-at-test-server |
| Merge into: | lp:miral |
| Diff against target: |
245 lines (+225/-0) 3 files modified
test/CMakeLists.txt (+1/-0) test/test_server.cpp (+154/-0) test/test_server.h (+70/-0) |
| To merge this branch: | bzr merge lp:~alan-griffiths/miral/first-cut-at-test-server |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Gerry Boland | 2016-08-11 | Approve on 2016-08-12 | |
|
Review via email:
|
|||
Commit Message
Add a TestServer fixture for writing miral tests
Description of the Change
Add a TestServer fixture for writing miral tests
Prerequisite for writing further tests of miral
To post a comment you must log in.
lp:~alan-griffiths/miral/first-cut-at-test-server
updated
on 2016-08-11
- 271. By Alan Griffiths on 2016-08-11
-
Don't report startup until after init
| Alan Griffiths (alan-griffiths) wrote : | # |
> The mir test framework has a bunch of test servers, why is this needed? Isn't
> the HeadlessTestServer enough?
The objective is to enable tests of the MirAL infrastructure.
A lot of the logic is similar to HeadlessTestServer, but it uses the MirAL infrastructure (MirRunner et alia) to start the server. Once we start to consolidate the MirAL work with Mir there will be opportunities to simplify.

The mir test framework has a bunch of test servers, why is this needed? Isn't the HeadlessTestServer enough?