js for sure

we’ve come around from writing playwright tests in cljs

the playwright is tooling is just too nice, the recorder etc

@U5H74UNSF Do you mean that you used to write cljs and now write js, or that you currently write in cljs?

we’ve previously written them in (squint) cljs, now just plain js

Is the interop too much of a hassle?

we’re using the ui tests to only drive the browser, so no interop is needed. Made some endpoints which the tests call to get data for forms also return plain json but that was it.

Ah, well, I mean the interop between CLJS and the playwright objects or whatever the nomenclature is

I guess if the code is really minimal and generally just calling Playwright functions, there's no reason as such for it to be CLJS over JS

Thank you for sharing 🙂

that was exactly why we switched it over, yes

npx playwright codegen is just too convenient to ignore

Or

npx playwright codegen --save-har="10_05_2023.har" --save-har-glob="**/api/**" 

for recording all network traffic to an api and later replaying it when you run your tests

I heard a rumor that @U5H74UNSF will do a talk about this, and some other pieces) that are very useful for testing, one of these days 🙂

Very nice @ULA8H51LP!

Looking forward to it @U5H74UNSF 😄