r/javascript • u/xcodebeast • 5d ago
Flashwright: the fastest e2e testing framework, up to 4x faster than Playwright
https://flashwright.dev/If you're interested in the details, here's a blog post: https://codebeast.io/blog/flashwright
67
Upvotes
39
u/Recoil42 5d ago
TLDR:
16
u/fireatx 5d ago
seems cool, similar to vitest's
isolate: falseconfig option, but i feel like this could probably just be a PR on the playwright repo adding a new config option. does this need to be an entirely new package?19
u/Positive_Method3022 5d ago
The strategy can lead to false positives/negatives. Sandboxing test execution by context is a must.
12
u/OpiumOpossum 5d ago edited 5d ago
Not sure but this seems like it could have memory leaks if you use listeners, network interceptors or logging. Otherwise, I am pretty sure this is a similar way to how Vitest optimizes their test runner.
3
u/Discordbothost 5d ago
there's an isolation: 'strict' option for a fresh context per test. default recycling is per worker, so the concern is state leaking into the next test on that worker, not parallel workers sharing one context. https://github.com/xcodebeast/flashwright#differences-from-playwright
3
u/LukaRozman27 5d ago
beware if you rely on Playwright's built-in tracing, Flashwright skips it entirely to hit those speed claims.
3
u/DarkGhostHunter 5d ago
Tested with Pest and the gains are… negligible. Barely 5%, margin of error.
2
u/tomByrer 5d ago
Neat! How well does it work vs headless browsers, esp LitePanda & co? Much improvement there?