Very clear explanation, thanks for that. I just tried various options and tests started to fail and the tests that didn't, were not really much faster. I have to admit that they also spend time here in making sure the website is fast. So if this saves a lot of time on your project, go for it. But for me it was not enough of a time save to even look into why some failed. I just left it to the default and all 85 tests work in under a minute anyway.
Thanks Mark. :) Thanks for sharing your experience and happy to hear that you're firing 85 tests running in under a minute. 💪 The primary focus of this video was to explain what `page.goto` waits for while pointing out that many applications have hydration issues. Of course, if things work for you (and are fast enough), go for it, too! 💙🦝
Thank you so much for your content so far. Can you do a series where you use Playwright to automate a real-life production app? This would be greatly appreciated.
Great tip as always!! Love your work! How do you write tests if you MUST handle situations where the developers use bad-form lazy loading which allows users to interact when they shouldn't be able to? As you mentioned, this is a common problem. It would be good to get some tips/tricks on that!
Thank you for wonderful explaination video about page.goto. 👏👏 Could you please share your test report tool shown in 07:44 minutes. Pls consider a video about your tool. 😇
That is Checkly - our tool. 🫣 You can find more info about it on checklyhq.com. In a nutshell and very brief: Checkly enables you to run and schedule your Playwright scripts to receive timely alerts when something's off with your prod site. :) And we have more videos about it here on the channel. :) 👇 th-cam.com/play/PLMZDRUOi3a8M95AwN8fWKL8VA5OJ73kJc.html
7:02 also prefer progressive enhancement. Your login form doesn’t need to wait for JavaScript to be ready to work (unless you use some spam protection which you could also do server side). In Next use a server action to submit the form via the action attribute.
That's right. 💯 If you're building with progressive enhancement you're not running into these problems in the first place. :) This section explicitly calls out ways to deal with poor hydration patterns when you rely on JS.
I am starting falling in love with your concise content on Playwright
Thanks! 💙 Happy it's been valuable!
that's a wonderful explanation, the best channel to deliver Playwright content
Thank you! 💙
Very clear explanation, thanks for that. I just tried various options and tests started to fail and the tests that didn't, were not really much faster. I have to admit that they also spend time here in making sure the website is fast. So if this saves a lot of time on your project, go for it. But for me it was not enough of a time save to even look into why some failed. I just left it to the default and all 85 tests work in under a minute anyway.
Thanks Mark. :) Thanks for sharing your experience and happy to hear that you're firing 85 tests running in under a minute. 💪
The primary focus of this video was to explain what `page.goto` waits for while pointing out that many applications have hydration issues.
Of course, if things work for you (and are fast enough), go for it, too! 💙🦝
Great content, you should make complete advanced Playwright course! 💪☺️
Absolutely, he is playwright expert and it would be handy.
Maybe one day. 😊 But for now you can expect all the Playwright content to show up here on the Checkly YT channel. :)
Superb explanation as always, glad you've become a Playwright ambassador
Thanks. Yeah, I've been an ambassador for quite a while but missed showing it in the videos. 🫣
Thank you so much for your content so far. Can you do a series where you use Playwright to automate a real-life production app? This would be greatly appreciated.
Great staff, thank you for your effort!
Stefan, you're content is always cool!!! Thanks for this one!
Thanks for the kind words! 💙
Thanks, this was implemented so long ago, so now you saved me time in my runs. Interested in other tips, hard to keep up with all these tweaks.
Excellent explanation. Thanks so much.👏
Happy it's been valuable. 💙
great videos as always.
Glad you like them! 😊
better then Microsoft
Great tip as always!! Love your work! How do you write tests if you MUST handle situations where the developers use bad-form lazy loading which allows users to interact when they shouldn't be able to? As you mentioned, this is a common problem. It would be good to get some tips/tricks on that!
It's a tricky problem to solve for sure. When I really MUST work around I tend to rely on `toPass` -> th-cam.com/video/8g7FvoRToGo/w-d-xo.html
Ganz geil, merci 🙂
Thank you for wonderful explaination video about page.goto. 👏👏 Could you please share your test report tool shown in 07:44 minutes. Pls consider a video about your tool. 😇
That is Checkly - our tool. 🫣 You can find more info about it on checklyhq.com.
In a nutshell and very brief: Checkly enables you to run and schedule your Playwright scripts to receive timely alerts when something's off with your prod site. :)
And we have more videos about it here on the channel. :) 👇
th-cam.com/play/PLMZDRUOi3a8M95AwN8fWKL8VA5OJ73kJc.html
7:02 also prefer progressive enhancement. Your login form doesn’t need to wait for JavaScript to be ready to work (unless you use some spam protection which you could also do server side). In Next use a server action to submit the form via the action attribute.
That's right. 💯 If you're building with progressive enhancement you're not running into these problems in the first place. :) This section explicitly calls out ways to deal with poor hydration patterns when you rely on JS.
I love your tutorial please create course playwright with TS on udemy 😁
Thank you! Mayb i'll do that one day, but for now the Playwright content will stay here on the Checkly YT channel. :)