libmirclient exports symbols only needed by the test framework
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Triaged
|
Low
|
Chris Halse Rogers | ||
mir (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
The acceptance tests ought to work through APIs exposed to users of Mir and not use backdoors. (They are about behaviour the users require.)
This is mostly true, but the test framework used for the tests needs access to some otherwise internal symbols of libmirclient vis:
MirConnectio
MirConnectio
MirConnectio
mir:
vtable?
typeinfo?
These are to support stubbing the client graphics. (See UsingStubClient
That's a lot of internals exposed that ought to be hidden.
Changed in mir: | |
milestone: | 0.7.0 → 0.8.0 |
Changed in mir: | |
milestone: | 0.8.0 → 0.9.0 |
Changed in mir: | |
milestone: | 0.9.0 → 0.8.0 |
Changed in mir: | |
milestone: | 0.8.0 → 0.9.0 |
Changed in mir: | |
milestone: | 0.9.0 → 0.10.0 |
Changed in mir: | |
milestone: | 0.10.0 → 0.11.0 |
Changed in mir: | |
status: | In Progress → Triaged |
milestone: | 0.11.0 → none |
I've already got part of a stub client platform in the privatise- all-the- things branch. It should be reasonable to get it usable for all the acceptance tests.