Thank you team, Amazing Feature added. Testing community is going to thank you for years. 😊 And Thank you Debbie for explaining the functionality with such details. Super like from me👌👍 I will be including this functionality into My upcoming video.
Currently moving from cypress to playwright and i am so surprised how seamless and powerful playwright is, especially on the CI. Thank you for the new update.
Great product! Love it! I've even persuaded a few people to drop their beloved Cypress, Puppeteer and other frameworks and use Playwright. I wonder any plans to integrate with Cucumber in the future.
I have found that the test generator doesn't always choose the best locators, are there any plans to configure it so if x locator is not available you can set it to look for b. For example before there was no good locators so test generator was giving me back an xpath we know xpath can be flaky. A dev ads a testid but the locator that is chosen is still an xpath
This should not be the case. In that scenario please file a bug on GitHub with your HTML structure, the element you are trying to get a locator for. Happy to look into it!
@@PlaywrightdevI will log an issue on GitHub, I just thought it was a limitation of code generator as the documentation says it's not ideal to use ids or testids
Great feature! But using Playwright 1.42.1 and the tool bar is shown in the browser, but the icons not. Have to wait for the tooltips to show to be able to choose the right tool :)
Can Playwright works on older firefox browser? I have a legacy system which works on firefox v36.0.4, wonder it will work with that browser (assume I test using firefox as a profile)?
Playwright versions are bound to a fixed version of Firefox. So if you use latest Playwright, you test latest Firefox. Testing on such old versions is not supported.
@@Playwrightdev One more question. What if I have a web page that requires user to authenticate using his fingerprint, is there a way that I can trigger wait for user to take action before resume the rest of the test? can this be done?
I see test automation anti-patern here :) If you record tests with a recorder and, let's say, you wrote a 100 of tests and then devs change a design a bit (e.g getByRole cannot find some button because the name of the button was changed) you would need to modify a lot of lines in every affected test. So, the right approach is - selectors should be reusable. Assertions are cool but recording is not.
Question. I want to use the recoder BUT I need to add a header to give myself some authorization. Whats best way to do this? I tried with setextraheader in the config but no result.
You can launch codegen via page.pause() as per here: playwright.dev/docs/codegen#record-using-custom-setup Before that you can set your custom launch/context options, interact with the page etc.
Can't find in the docs how to setup linting - I struggle with figuring out how to configure .eslintrc.,cjs with a tsconfig (which isn't in the project?)
I never use test generator, there is always a better way to find an element than its suggesting it. For complex page objects of course... Test generator works only with simple structures
It's sad to see Playwright go the route of Telerik Test Studio or Selenium IDE from over 10 yrs ago. RnP tools are a fool's folly. This is what ends up lumping together SDETs w/ manual testers into the same category of "programming rejects 'cause they can't code". Also, test automation is coding...why would you NOT lint it and format it!? It's still just code!
outputDir should work. Make sure to specify it in your top-level object in your config: playwright.dev/docs/api/class-testconfig#test-config-output-dir Otherwise feel free to file a bug.
I love how with each release cypress falls further and further behind :D
Massive improvement. Thank you team. Well done for consistently bringing high-value features. It was great even before this version!
Assertion recording for the test generation is crazy!! amazing work
Thank you for this mind blowing update🤯!
The tips are very helpful too.
Keep up the amazing work!
The little tip for eslint no floating promises is such a game changer, thank you.
This is fantastic and makes my automation journey even smoother. Thanks a ton for your hard work and continuous improvement.
Playwright a powerful automation tool with powerful features and thanks for keep adding more and more feature which makes it very special
I remember starting in test automation back in 2003 and QTP had the code generation abilities. I’m glad it’s been modernized!
Great job, guys! I'm so excited to see that amazing progress moving us all forward in our possibilities of automation testing. Thank you so much!
Awesome! Thank you for making Playwright better and better ❤
Great feature, another big step I think :) And very nice demo, I found Debbie's enthusiasm very helpful to stay focus on a video, thanks a lot :)
Thank you team, Amazing Feature added. Testing community is going to thank you for years. 😊
And Thank you Debbie for explaining the functionality with such details.
Super like from me👌👍
I will be including this functionality into My upcoming video.
Currently moving from cypress to playwright and i am so surprised how seamless and powerful playwright is, especially on the CI. Thank you for the new update.
Great product! Love it! I've even persuaded a few people to drop their beloved Cypress, Puppeteer and other frameworks and use Playwright. I wonder any plans to integrate with Cucumber in the future.
just for comparison purpose, which testing libraries also give you the "Record" function that will give you the line of code 2:50
Really amazing. Thanks for the new features!
Really nice feature for the assertion recording! I never expect this will happen, thank you playwright team!
Wonderful, as usual. Thanks a lot.
Amazing update ! ;)
Incredible work !
Is there any way we can use the debugger tool when using playwright in docker?
Thanks for your hard work 🎉
I am a bit worried about Andrey Lushnikov. May I ask why he stopped appearing in these videos? Is he still in charge of Playwright?
When are you planning to add visual comparison capability to .NET flavour of Playwright?
Nice update. Will UI mode come to Python as well?
I have found that the test generator doesn't always choose the best locators, are there any plans to configure it so if x locator is not available you can set it to look for b. For example before there was no good locators so test generator was giving me back an xpath we know xpath can be flaky. A dev ads a testid but the locator that is chosen is still an xpath
This should not be the case. In that scenario please file a bug on GitHub with your HTML structure, the element you are trying to get a locator for. Happy to look into it!
You could always edit the code after to get the right locator, no?
You can, kinda defeats the purpose of using the code generator which is why I was saying it's not the greatest...lol.
@@PlaywrightdevI will log an issue on GitHub, I just thought it was a limitation of code generator as the documentation says it's not ideal to use ids or testids
What about the "eslint-plugin-playwright"? Is it recommended?
Where's Andrey?
Great feature! But using Playwright 1.42.1 and the tool bar is shown in the browser, but the icons not. Have to wait for the tooltips to show to be able to choose the right tool :)
Can Playwright works on older firefox browser? I have a legacy system which works on firefox v36.0.4, wonder it will work with that browser (assume I test using firefox as a profile)?
Playwright versions are bound to a fixed version of Firefox. So if you use latest Playwright, you test latest Firefox. Testing on such old versions is not supported.
@@Playwrightdev One more question. What if I have a web page that requires user to authenticate using his fingerprint, is there a way that I can trigger wait for user to take action before resume the rest of the test? can this be done?
Amazing work and Demo. Playwright is such an awesome tool. Highly recommended
I see test automation anti-patern here :) If you record tests with a recorder and, let's say, you wrote a 100 of tests and then devs change a design a bit (e.g getByRole cannot find some button because the name of the button was changed) you would need to modify a lot of lines in every affected test. So, the right approach is - selectors should be reusable. Assertions are cool but recording is not.
is it possible to run the recorder without vs code or the extension?
Yes, "npx playwright codegen" will also open the Inspector / Recorder. See the docs if you are using a different language binding.
Thanks so much, this will be a real time saver!@@Playwrightdev
how can i disable incognito mode when i use playwrite test cases with angular?
I can't really find the fix for this problem since a while
I recommend filing an issue on GitHub why Playwright's default mode does not work for you.
Question. I want to use the recoder BUT I need to add a header to give myself some authorization. Whats best way to do this? I tried with setextraheader in the config but no result.
You can launch codegen via page.pause() as per here: playwright.dev/docs/codegen#record-using-custom-setup
Before that you can set your custom launch/context options, interact with the page etc.
Do you have ambassador with python knowledge? I would be happy to have a dedicated "What'n new" editions with her/him, speaking about only python...
Can't find in the docs how to setup linting - I struggle with figuring out how to configure .eslintrc.,cjs with a tsconfig (which isn't in the project?)
I hope that helps! typescript-eslint.io/rules/no-floating-promises/
Great update
awesome stuff
This is Amazing !!
This is really good
Amazing!!
Awesome
nice! Thanks!
more updates for the python version
this update works for python too. check the python docs on test generator for more details
🙌Nice@@Playwrightdev
I never use test generator, there is always a better way to find an element than its suggesting it. For complex page objects of course... Test generator works only with simple structures
very cool
It's sad to see Playwright go the route of Telerik Test Studio or Selenium IDE from over 10 yrs ago. RnP tools are a fool's folly. This is what ends up lumping together SDETs w/ manual testers into the same category of "programming rejects 'cause they can't code". Also, test automation is coding...why would you NOT lint it and format it!? It's still just code!
Я так понял русский разрабытвают Playwrith ))
Is it possible to change default "test-results" directory location?
tried outputDir: './reports/end2end', but did not work.
outputDir should work. Make sure to specify it in your top-level object in your config: playwright.dev/docs/api/class-testconfig#test-config-output-dir Otherwise feel free to file a bug.