Comment 2 for bug 1375301

The acceptance tests demonstrate the functionality and features that we have set out to build for the users of mir. Much like how building a feature that cannot be used doesn't doesn't make sense, and having an acceptance test for an externally unusable feature also doesn't make sense.

The acceptance tests can be molded and shaped (and drive the introduction and removal of different features), but having an acceptance test that tests the internals of the system is surely a problem. Acceptance tests are "end to end" (or less ideally "edge to edge" sometimes in the GOOS terminology), not internal tests.