Playwright for .NET is now stable

Post by hpaavola » Thu, Jun 10, 2021, 2:03 PM UTC

hpaavola wrote: post #29

rullopat wrote: post #23

Earlier quoted context omitted.

Playwright is fantastic, but having used a lot Robot Framework in the past, I would not recommend it even to my worst enemy. The experience he continuous from string / to string conversions that you need to do with the content of the steps and the orrible structure of the directories and the amount of glue code to share some common methods around, brought me to don't even take into consideration job offers that have…

RF does automatic type conversion based on the typehints in the python libraries used. So no need to change types manually. And there is no dictated directory structure. So, stop doing horrible directory structures and the pain goes away. And there is no glue at all needed to share methods at all. Write function in Python/keyword in Robot framework and take it in use using "Resource" or "Library" statement. Done.

    *** Settings ***
    Library    calc.py


    *** Test Cases ***
    My First Library
        ${sum}    Plus    1    2
        Should Be Equal As Integers    ${sum}    3

    def plus(a: float, b: float):
        return a + b

Post by arjun27 » Thu, Jun 10, 2021, 2:06 PM UTC

inglor wrote: post #22

tnolet wrote: post #6

Earlier quoted context omitted.

This question does come up quite a lot. One thing the remember is that Cypress is "batteries included" testing framework, where Playwright is essentially just the browser automation part of it. I know the Playwright team is "moving up the stack" and adding many specific testing features, but it's not at the same level (yet?) as Cypress.

I think you're thinking of Puppeteer? Playwright has stuff like automatically waiting for elements, selecting by text etc all built in - with modern JavaScript/TypeScript, none of the weird chaining syntax and debugger. There are also tools that give you pretty much any feature Cypress has on top of Playwright. (Not saying which is better - only that they're both sort of the same slot)

Post by inglor » Thu, Jun 10, 2021, 2:19 PM UTC

Scarbutt wrote: post #34

jbgreer wrote: post #25

For those of you wondering at home: Playwright for .NET is the official language port of Playwright, a Node.js based library to automate Chromium, Firefox and WebKit with a single API.

Still requires nodejs though, it is more a wrapper than a port.

Post by worldsayshi » Thu, Jun 10, 2021, 2:26 PM UTC

arjun27 wrote: post #17

worldsayshi wrote: post #10

Earlier quoted context omitted.

I've had some issues with Cypress selectors randomly failing to find matching elements, even though they are clearly present. Like if I run the same script 10 times it goes through ~7 times. I wanted to try Playwright for another application to avoid such issues. And then I was very surprised to get almost the exact same issues with Playwright. Running against a different application with different test cases. Has an…

Were you able to use the DOM snapshots to debug why the selectors did not resolve? Would love to know more.

Post by Scarbutt » Thu, Jun 10, 2021, 2:53 PM UTC

inglor wrote: post #35

Scarbutt wrote: post #34

Earlier quoted context omitted.

Still requires nodejs though, it is more a wrapper than a port.

It's not really a wrapper - it's a client in client/server architecture - the difference is important because it means that .NET is a first-class citizen here (like selenium and unlike tools like puppeteer-sharp) and that updates propagate to all languages automatically. The downside is indeed that you need a "server running".