Skip to content

test(playwright): migrate propfind tests from Cypress to Playwright - #9021

Open
mejo- wants to merge 2 commits into
mainfrom
test/propfind_playwright
Open

test(playwright): migrate propfind tests from Cypress to Playwright#9021
mejo- wants to merge 2 commits into
mainfrom
test/propfind_playwright

Conversation

@mejo-

@mejo- mejo- commented Aug 9, 2026

Copy link
Copy Markdown
Member

Assisted-by: OpenCode:claude-fable-5

🏁 Checklist

  • Code is properly formatted (npm run lint / npm run stylelint / composer run cs:check)
  • Sign-off message is added to all commits
  • Tests (unit, integration and/or end-to-end) passing and the changes are covered with tests

🤖 AI (if applicable)

  • The content of this PR was partly generated using AI tools
  • The AI-generated content was reviewed, comprehended and tested by a human

@mejo- mejo- self-assigned this Aug 9, 2026
@mejo- mejo- added the tests If you write them we ♥ you label Aug 9, 2026
@github-project-automation github-project-automation Bot moved this to 🧭 Planning evaluation (don't pick) in 📝 Productivity team Aug 9, 2026
@mejo-

mejo- commented Aug 9, 2026

Copy link
Copy Markdown
Member Author

/backport to stable34

@mejo-

mejo- commented Aug 9, 2026

Copy link
Copy Markdown
Member Author

/backport to stable33

Signed-off-by: Jonas <jonas@freesources.org>
Assisted-by: OpenCode:claude-fable-5
@mejo-
mejo- force-pushed the test/propfind_playwright branch from 0282101 to b9c8505 Compare August 10, 2026 07:35
const [root1] = await propfindFolder(user, '/', 0, properties)
expect(root1).toHaveProperty(PROPERTY_WORKSPACE_FLAT, '')

await deleteWebDAVResource(user, '/Readme.md')

@mejo- mejo- Aug 10, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line most likely fixes the flakiness of the test compared to the Cypress one. Without this line, this test succeeds reliably locally but fails reliably (so far) in CI.

Claude assumes that this is because the storage cache doesn't get invalidated properly in CI when only overwriting the file compared to deleting it and uploading a new file (which results in new fileId etc). It may well be that the missing cache invalidation is due to different APCu caching setup in CI.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we could fix that different setup. Would such a setup have visible consequences in actual setups or is this a CI artifact we are observing?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have hard feelings here. I didn't dive into investigating the actual differences with caching setup between CI and local environment, I merely was happy to have found an explanation for the flaky test and decided to move on 😆

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@max-nextcloud do you see a problem with adding the delete in the test? It arguably changes what is being tested: updating a file no longer is tested. But do you think it should be tested in the propfind tests?

@mejo- mejo- moved this from 🧭 Planning evaluation (don't pick) to 👀 In review in 📝 Productivity team Aug 10, 2026
…slow

The test often exceeds the default timeout in CI.

Signed-off-by: Jonas <jonas@freesources.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review backport-request tests If you write them we ♥ you

Projects

Status: 👀 In review

Development

Successfully merging this pull request may close these issues.

2 participants