41–50 of 66 posts
Earlier quoted context omitted.
So what's the point of it then? Why add more layers of unnecessary abstraction? Why don't just use the node.js library then?
Because for some teams it's easier to write tests in plain C# with NUnit/xUnit libs.
Earlier quoted context omitted.
Because for some teams it's easier to write tests in plain C# with NUnit/xUnit libs.
But why? Why shoehorn everything into a single technology? Is it so that certain people never have to learn anything else in their entire life anymore?
Earlier quoted context omitted.
Because for some teams it's easier to write tests in plain C# with NUnit/xUnit libs.
But why? Why shoehorn everything into a single technology? Is it so that certain people never have to learn anything else in their entire life anymore?
Personally, I work with both C# and JavaScript, and I'd happily use the C# version of Playwright to write and run UI tests.
Oh, I didn't know this existed. Definitely going to try this. I'm currently using Puppeteer Sharp ( https://github.com/hardkoded/puppeteer-sharp ) and something like: > await page.GotoAsync(" https://playwright.dev/dotnet "); > await page.ScreenshotAsync(new PageScreenshotOptions() { Path = "screenshot.png" }); Is broken, if you have background images in CSS the screenshot happens after Page Load is completed but bef…
you need to put this before the Screenshot ? await page.WaitForLoadStateAsync(LoadState.NetworkIdle);
Earlier quoted context omitted.
Because for some teams it's easier to write tests in plain C# with NUnit/xUnit libs.
But why? Why shoehorn everything into a single technology? Is it so that certain people never have to learn anything else in their entire life anymore?
Also regardless of keeping it in a _single_ language or tool, one might prefer to write tests in a .net language instead of js or python.
Earlier quoted context omitted.
Because for some teams it's easier to write tests in plain C# with NUnit/xUnit libs.
But why? Why shoehorn everything into a single technology? Is it so that certain people never have to learn anything else in their entire life anymore?
Earlier quoted context omitted.
Same guy does playwright sharp, he should really have more supporters
OH WOW! I had no idea! Yeah he does deserve more support. I still donno why MS can't contribute to projects directly. But I'm happy there's another possible solution to my problem.
Oh, I didn't know this existed. Definitely going to try this. I'm currently using Puppeteer Sharp ( https://github.com/hardkoded/puppeteer-sharp ) and something like: > await page.GotoAsync(" https://playwright.dev/dotnet "); > await page.ScreenshotAsync(new PageScreenshotOptions() { Path = "screenshot.png" }); Is broken, if you have background images in CSS the screenshot happens after Page Load is completed but bef…
I'm using Playwright right now, migrating horrendous Selenium tests at work and it's a real breeze of fresh air. It just works, it comes battery included with superb debugging tools (step by step execution directly in the browser, trace dumping for further analysis, reliable interactions recorder with pretty decent code generation ...). It's an amazing piece of software for a domain that was kept on the side of the r…
Earlier quoted context omitted.
But why? Why shoehorn everything into a single technology? Is it so that certain people never have to learn anything else in their entire life anymore?
Well, a pretty good reason is that C# is statically typed, which a lot of developers prefer. It's arguably a much more powerful language than JavaScript too. Personally, I work with both C# and JavaScript, and I'd happily use the C# version of Playwright to write and run UI tests.