I realy enjoy your release shows, great work as always! The past developments are realy great. Even if our company currently using Selenium and Cypress, its time to show my folks at office what a powerful tool playwright have become!
Well done on the expect extend pattern. This makes typesafety so much easier to achieve, and much clearer how the extension happened. Cypress went with the singleton registry approach with interface augmentation in typescript, which I was never a fan of.
same here, this would might be a hard fact switching to playwright from an other tool because debugging on custom functions or pom actions is realy hard
Would have been really useful to see how order of operations works in merging test fixtures! Does it call everything from each fixture before the `await use`? Does it follow the order they're specified in the merge?
It depends, the most of the PO doesn't have such technical knowledge of testing. I would like to see high-level testcaces(eg. specflow type) written in Jira or whatever you use for sprints. It is better than to ask PO to use another tool. You can show these during sprint demo/review if you think it is neccesary.
In Python we don’t have this as a feature, since everything is assert keyword/pytest based there, we recommend creating a helper function. To have it boxed, you can use tracebackhide see here: docs.pytest.org/en/7.1.x/example/simple.html#writing-well-integrated-assertion-helpers
I realy enjoy your release shows, great work as always! The past developments are realy great. Even if our company currently using Selenium and Cypress, its time to show my folks at office what a powerful tool playwright have become!
Seriously each of these features are amazing! Already planning to use these in my tests! Great work
At first I thought you hired Macaulay Culkin 😀
Well done on the expect extend pattern. This makes typesafety so much easier to achieve, and much clearer how the extension happened. Cypress went with the singleton registry approach with interface augmentation in typescript, which I was never a fan of.
Amazing features, thanks.
amazing, great job!
Wait a second, you are not Andrey and Noel!..
Where are they?
Max is a legend in test automation open source
The 'box' feature is amazing, it was a huge pain before
same here, this would might be a hard fact switching to playwright from an other tool because debugging on custom functions or pom actions is realy hard
I don't like it... sounds way more confusing then before
Oh man this makes the code so much more complex!😢
Seriously, I don't like it at all...
fwiw I record all traces (pass or fail) in CI, storage is cheap and having a good trace to compare to is amazing. I think it should be encouraged.
ArigaThanks.
Very intresting, but very complex for me. Need to get a new level in TS/JS
Great update ! :)
Thank you anymore videos coming ?
Looks like something many Java projects could use.
Would have been really useful to see how order of operations works in merging test fixtures!
Does it call everything from each fixture before the `await use`? Does it follow the order they're specified in the merge?
This is awesome
Box feature sounds more confusing than before, especially in complex situations.
I will update after trying though.
Pretty cool
For trace viewer, would it be ideal for a product owner to view to do uat testing/ reviewing test cases?
It depends, the most of the PO doesn't have such technical knowledge of testing. I would like to see high-level testcaces(eg. specflow type) written in Jira or whatever you use for sprints. It is better than to ask PO to use another tool. You can show these during sprint demo/review if you think it is neccesary.
Hi, how can we use custom expect matchers with python? An example would be beneficial (cannot find anything in the official docs) Thx
In Python we don’t have this as a feature, since everything is assert keyword/pytest based there, we recommend creating a helper function. To have it boxed, you can use tracebackhide see here: docs.pytest.org/en/7.1.x/example/simple.html#writing-well-integrated-assertion-helpers