From 5b2d02234898903440a34ca7e6e9b8f661830a86 Mon Sep 17 00:00:00 2001 From: Chris Peyer Date: Thu, 14 May 2026 21:20:06 -0400 Subject: [PATCH] fix: update versions test to handle multiple audit groups after #931 PR #931 changed formatVersions to keep audit entries in separate groups when split by a labeled version boundary. The test now finds two .is-audit elements (one before and one after 'ver 1'), causing a strict mode violation. Use .first() to target the most recent audit group. Co-Authored-By: Claude Sonnet 4.6 --- test/e2e/tests/versions.spec.js | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/test/e2e/tests/versions.spec.js b/test/e2e/tests/versions.spec.js index aec42e00..462a2d8a 100644 --- a/test/e2e/tests/versions.spec.js +++ b/test/e2e/tests/versions.spec.js @@ -62,7 +62,9 @@ test('Create Version and Restore from it', async ({ page }, workerInfo) => { // Check that there is an audit entry for the last edit (which we didn't) // expliticly create a version for. - const audit = await page.locator('.da-version-entry.is-audit'); + // Use .first() because PR #931 keeps audit groups separate across version boundaries, + // so there may be multiple is-audit entries (one before and one after 'ver 1'). + const audit = await page.locator('.da-version-entry.is-audit').first(); await audit.click(); const expectedUser = process.env.SKIP_AUTH ? 'anonymous' : 'da-test@adobetest.com';