Don't interfere with failure screenshots with @After

[labkey-tchad]

Rationale

PanoramaPublicMyDataViewTest has been failing intermittently but we can't investigate the failure because PanoramaPublicBaseTest.afterTest navigates away before we can take failure screenshots.

org.openqa.selenium.StaleElementReferenceException: The element with the reference 4b968cbd-bcdb-48a2-80f4-82f579b56e2f is stale; either its node document is not the active document, or it is no longer connected to the DOM
[...]
  at app//org.labkey.test.tests.panoramapublic.PanoramaPublicMyDataViewTest.myDataView(PanoramaPublicMyDataViewTest.java:195)
  at app//org.labkey.test.tests.panoramapublic.PanoramaPublicMyDataViewTest.verifyColumnValues(PanoramaPublicMyDataViewTest.java:156)
  at app//org.labkey.test.tests.panoramapublic.PanoramaPublicMyDataViewTest.viewSubmitterData(PanoramaPublicMyDataViewTest.java:127)
  at app//org.labkey.test.tests.panoramapublic.PanoramaPublicMyDataViewTest.testMyDataView(PanoramaPublicMyDataViewTest.java:81)

We can avoid this navigation by making verifySymlinks not care whether the test is currently impersonating.

Related Pull Requests

• N/A

Changes

• Don't interfere with failure screenshots with @after