1787234 - Android: GleanTestLocalServer state sticks around and influences other tests

Status: RESOLVED FIXED

(Data Platform and Tools :: Glean: SDK, defect, P1)

Description

[Jan-Erik Rediger [:janerik]]

It looks like using GleanTestLocalServer can cause its state to stick around across test classes, leading to intermittens because data is not received in the right local server.

We should look into whether we can better separate the state between tests.

Comment 1

[Jonathan Almeida [:jonalmeida]]

Travis, I noticed that in this TestWatcher, we also use initialize the TestWorkManager. Could we employ the same fix to this one as we did in bug 1719905?

I can file a separate bug if that's more convenient instead of using this one.

Comment 2

[Travis Long [:travis_]]

Nope I think that fixing that along with addressing any other state issues falls under the scope of this bug, thanks for pointing it out to us, Jonathan!

Comment 3

[BMO Github Automation]

Attachment: [mozilla/glean] Bug 1787234 - Fix `GleanTestLocalServer` test rule leaking between tests (#2915)

Comment 4

[Travis Long [:travis_]]

Turns out I was able to reproduce the issue pretty repeatably with the glean sample app. After adding a way to await the WorkManager executor to complete the tasks and then closing its database, the tests seemed to pass reliably. Hopefully this helps with the problems we have been seeing.