3 ms·
This is a great idea! Even better: write a Playwright/Codegen[1] test and have that execute continuously (or put a button in the IDE to trigger it). That way yo
by 0xbadcafebee 4y ago
This is a great idea! Even better: write a Playwright/Codegen[1] test and have that execute continuously (or put a button in the IDE to trigger it). That way you can iterate on multiple code files but see how it impacts one end-to-end test in real time! (I'm developing a feature right now where I'm doing that manually and it would be nice to automate)
[1] https://playwright.dev/docs/codegen-intro https://playwright.dev/docs/codegen-intro
- _cfl0 4y agocollab w/ me ;)
- hudixt 4y agoWe have built something along these lines, Crusher [1] (demo [2]) is an e2e framework, you can trigger test with click of a button. It's built on top of playwright. We’re thinking of adding watch mode in the coming months - running tests continuously in real-time. Sending you an email to exchange ideas. P.S.- there might be few typos. It’s work in progress. [1] https://www.youtube.com/watch?v=Nc-TlgeKBSE https://www.youtube.com/watch?v=Nc-TlgeKBSE [2] https://github.com/crusherdev/crusher https://github.com/crusherdev/crusher