This has been discussed a lot, but I think that there is still a real need for this. Some of the latest discussion can be found [here](https://github.com/mozilla-mobile/android-components/pull/3099#discussion_r302458357) in a PR I was working on that ran into the problem head-on. The TL;DR is that Glean being implemented the way that it is, can persist state between tests in the same class, as well as between tests in different test classes. I'm sure that this is probably causing us trouble with intermittent test failures, as well as sometimes making the order that tests are ran in significant (which in itself is an issue as we have no good way to control the order in which the tests are ran).
Bug 1565240 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This has been discussed a lot, but I think that there is still a real need for this. Some of the latest discussion can be found [here](https://github.com/mozilla-mobile/android-components/pull/3099#discussion_r302458357) in a PR I was working on that ran into the problem head-on. The TL;DR is that Glean, being implemented the way that it is, can persist state between tests in the same class, as well as between tests in different test classes. I'm sure that this is probably causing us trouble with intermittent test failures, as well as sometimes making the order that tests are ran in significant (which in itself is an issue as we have no good way to control the order in which the tests are ran).