starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #2227] Playwright tests are flaky #644

New issue

Closed

opened 2026-02-26 18:47:53 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 18:47:53 +03:00

Owner

Originally created by @mKoonrad on GitHub (Nov 20, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2227

Issue Description

I noticed that Playwright tests randomly flakey due to some issues. The same correct code could be marked as failed. This can be frustrating and confusing if you commit good code.

Steps to Reproduce

Go to actions/workflows/e2e-tests.yml
Analyze last actions to see many errors caused by random parts of code, unrelated with PR commits.

Expected Behavior

Playwright tests should be fixed or removed if they do not fulfill their purpose.

Current Behavior

Currently all E2E actions are failure, even from Documenso team.

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

N/A

Browser [e.g., Chrome, Firefox]

N/A

Version [e.g., 2.0.1]

v2.0.14

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @mKoonrad on GitHub (Nov 20, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2227 ### Issue Description I noticed that Playwright tests randomly flakey due to some issues. The same correct code could be marked as failed. This can be frustrating and confusing if you commit good code. ### Steps to Reproduce 1. Go to [actions/workflows/e2e-tests.yml](https://github.com/documenso/documenso/actions/workflows/e2e-tests.yml) 2. Analyze last actions to see many errors caused by random parts of code, unrelated with PR commits. ### Expected Behavior Playwright tests should be fixed or removed if they do not fulfill their purpose. ### Current Behavior Currently all E2E actions are failure, even from Documenso team. ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] N/A ### Browser [e.g., Chrome, Firefox] N/A ### Version [e.g., 2.0.1] v2.0.14 ### Please check the boxes that apply to this issue report. - [x] I have searched the existing issues to make sure this is not a duplicate. - [x] I have provided steps to reproduce the issue. - [x] I have included relevant environment information. - [ ] I have included any relevant screenshots. - [x] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:47:53 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:47:54 +03:00

Author

Owner

@Mythie commented on GitHub (Nov 20, 2025):

Don't run the contents of that zip file it was malware.

We're aware of the tests being flakey and are frustrated by it internally too. There will be some work shortly to get these back to being consistent.

Majority of the flakiness comes from auto saving that can desync due to the speed in which playwright uses the app

@Mythie commented on GitHub (Nov 20, 2025): Don't run the contents of that zip file it was malware. We're aware of the tests being flakey and are frustrated by it internally too. There will be some work shortly to get these back to being consistent. Majority of the flakiness comes from auto saving that can desync due to the speed in which playwright uses the app

kerem commented

2026-02-26 18:47:54 +03:00

Author

Owner

@mKoonrad commented on GitHub (Dec 16, 2025):

Seems to be fixed since #2280

@mKoonrad commented on GitHub (Dec 16, 2025): Seems to be fixed since #2280

kerem referenced this issue

2026-02-26 19:31:49 +03:00

[PR #644] [MERGED] feat: cache getServerComponentSession calls #1097

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#644

No description provided.

Rows
Columns