This video is very clear and informative. Thanks for the great explanation!

problematic design

잘보고있어요 thank you!

Very helpfull video! In real big project, it is necessary to add more eslint configuration? thanks

Thanks for the amazing tips

Great content🙌 Thanks a lot.

This is gonna help me a lot, one time I lost almost a hour to figure out this problem Thank you bro!!!

Thank you! Great content :)

Thanks for the few more amazing tips!

Thanks for the tip

Always very useful tips! Thank you!

Superb explanation as always, glad you've become a Playwright ambassador

Hi, i have a doubt what if newPage opens after you did some operation on home page and you need send that instance to next page like cart page. How to send that newPage to another fixture.

I would be very interested to see a video specifically on the topic of how to decide whether to use GetByTestid as opposed to the more user-behavior locators like GetByRole

Can I add environment variables at group level through the CLI?

Hi I ran 15 tests in series mode by using 1 worker. All the tests were passed in local environment. But the tests were failed in pipeline and the error shows in pipeline was test timeout of 120000ms exceeded. Can anyone help me?

I was looking for something like this (a mask) thank you for showing it :))

Thank you for great video

Stefan, you're content is always cool!!! Thanks for this one!

Nice clean code, but is it possible to preserve state between tests if you are automatically creating a new instance every time you call it?

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.

Amazing!

Powerful! Handy! Nifty! Elegant!

Imagine to have a big amount of page-objects, it should be really boring to add all of these in the fixture to be exported.. in base.ts is it possible to create the MyFixtures and the export const test dynamically? I mean, like reading all the the pages inside /pom and forEach page add it into MyFixtures and into the test const to export

is it free sir?

You can go even further: wrap all your page objects into UI fixture and use only it in your `test('test-name', async({ui}) => {}` statement. So in your test you'll have statements like `await ui.loginPage.login(EMAIL, PW)` and `await ui.dashboardPage.isReady()` And even further - you can do the same thing for APIs, wrapping all you API objects with CRUD and other methods into API fixture to do things like `await api.user.create(EMAIL, PW)`

Cool new feature and great explanation - thank you! Love Playwright 😇

great videos as always.

Ganz geil, merci 🙂

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!

better then Microsoft

Great content, you should make complete advanced Playwright course! 💪☺️

I am starting falling in love with your concise content on Playwright

that's a wonderful explanation, the best channel to deliver Playwright content

I love your tutorial please create course playwright with TS on udemy 😁

Excellent explanation. Thanks so much.👏

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. 😇

Why is failOnJSError initialised as an array when it's supposed to be a boolean?

Hello! I really appreciate that. Could you please create a video list focused solely on fighting flakiness in testing? This is a critical area for all testers.

Is there a way to evaluate expression in debug mode ?I want to do a click using evaluate expression . How to do that ?Please explain

Can we chain or more than 1

Great Webinar. Very useful !

Great content buddies, I have started using Playwright and I have integrated in CI, however I have two challenges: 1. It is always a challenge to automate production environment for examples if we have an e-commerce platform ww want to make sure that customers can place the orders seamlessly. How this can be done on production environment since we don't want to record dummy orders on prod. Note: There is no delete component 2. How to mitigate the failed step or test cases which cause Playwright to skip the all remaining test cases?

how to use different users contexts in one test? like user1.chat.sendMessage('testmes') user2.chat.checkMessage('testmes')

Finally, Dev guys can enjoy a good night's sleep with the confidence in the code and knowing their applications are being monitored effectively. Great work Checkly team. Congrats.

Hi Brother. Do you have the same sample repo project for PlayWright with BDD frame work java. Do you have a mail id to reach out?

No entendi. Osea yo en mi projecto uso los wait, lo cual no es lo mas productivo pero no le encuentro otra manera. Checkly que sugiere hacer para no usar los wait?

This video is helpful to understand how narrowing works, so thank you for that! However, as an accessibility engineer there is one problem with the example you have used. It can be difficult for users to identify which "Remove" button is associated with which user or racoon in this case. It would be better to continue to use only the getByRole locator and add unique accessible names to each button, so when I'm navigating with a screen reader I know exactly which user's "remove" action I'm on. One way to do this without changing the visible text and/or visual design would be to add an aria-label to each button. The aria-label should contain the visible text but add more description. Ex. aria-label="Remove Ricky Racoon". With this unique accessible name you can then continue to use getByRole and know your interactive elements are uniquely named for screen reader users. Ex. getByRole('button', { name: 'Remove Ricky Racoon' })

Pretty helpful content, thanks!

Thanks, I have a question if I am using test.step() in my tests to organize my navigation and interaction. So, I would have a step to login and check I am on the dashbaord and another step to navigate from dashboard to page1 and then either a aftereach or another step to logout. Is it recommended to have one fixture that instantiates all pages need in a test, or / can we extend the test.step() for each navigation interactions? Currently, I use functions to hide this functionality but would be interested in fixture replacement.