playwright

Do check out https://github.com/microsoft/playwright - Node.js library to automate Chromium, Firefox and WebKit with a single API

Cypress uses bluebird for their promise implementation which are A+ spec. [1] Also (nearly) every command in Cypress is a promise which allows you to make them then-able. [2] I don't agree with using Cucumber for anything. The way most teams implement Cucumber makes it such a pain to write a test. I do like the suggestion of puppeteer tho. If you haven't heard of playwright [3] I'd look into that. From the same creator as puppeteer but was hired to work on playwright full time. They have the advantage of being to test on gecko, chromium, and webkit browsers which is really nice because IME anything Apple becomes such a pain to setup to properly test. [1] https://docs.cypress.io/api/utilities/promise.html#Syntax [2] https://docs.cypress.io/api/commands/then.html#Yields [3] https://github.com/microsoft/playwright

I really like Playwright, there is less magic and it simply works: https://github.com/microsoft/playwright Especially with this test runner: https://github.com/microsoft/playwright-test

I've found playwright more useful: https://github.com/microsoft/playwright It's an alternative to Cypress and from what I remember, it has a much better API.

Indeed I missed that. So playwright is definitely more interesting. What is surprising is the linked site is quoting the FAQ of playwright that has been removed a couple of months ago: https://github.com/microsoft/playwright/pull/1930/files That FAQ seems to be giving a lot of perspective on the subject. Wondered why it was removed.

Playwright looks promising if you’re OK with a narrower range of browsers: https://github.com/microsoft/playwright

@mherrmann What would be the comparison / difference with SeleniumBase https://github.com/seleniumbase/SeleniumBase ? I'm always on the lookout for browser automation using Python so excited to try this framework. I was a big fan of https://github.com/miyakogi/pyppeteer but it doesn't seem to be maintained anymore. There is another project by microsoft called playwright, though it's js-only for now. They don't have plan for Python bindings for now https://github.com/microsoft/playwright/issues/1043

Hey! I definitely remember you :) It’s always satisfying to run into the same folks across different projects, over the course of multiple years. I’m glad to hear the examples worked out of the box! We’ve been iterating on the docs and API quite a bit (based on feedback), so don’t hesitate to let us know if/how they can be improved: https://github.com/microsoft/playwright.

Playwright allows you to connect to existing browser instances, but it currently requires you to get the “debug URL” of the browser instance first: https://github.com/microsoft/playwright/blob/v0.11.1/docs/ap.... I’d love to hear a bit more about the scenario you have in mind, since that might help inform some improvements we can make. Thanks!

Out of curiosity: why does the fact that Playwright is a Microsoft-sponsored OSS project discourage your interest? The team is working very hard to be open/transparent/available (https://github.com/microsoft/playwright), and we’re very excited to build a better automation stack with the help of the community. I only ask since I’d love to hear any feedback for how we could improve the way we run/position the project. Thanks!

As part of our goal to enable better developer ergonomics, we’re very keen to explore “better”/higher-level APIs and additional extensibility points. For example, we allow you to define custom “selector engines” (https://github.com/microsoft/playwright/blob/master/docs/sel...), which is just one example of the kinds of customizations we want to enable. Out of curiosity: are there any specific extensions from puppeteer-extra that you’ve used and/or would be interested to see?

Great! Let us know if you end up having any questions/comments/feedback: https://github.com/microsoft/playwright.

Awesome! Please don’t hesitate to let us know how we can improve. We want to make web automation not only more reliable, but also more enjoyable. So we’re keen to hear how we can continue to push that goal forward :) https://github.com/microsoft/playwright

Each of the page operations (e.g. click) automatically wait for the specified element to become visible before being performed. That way, your automation code is declarative about what you want to do, and to what element(s), and you can allow the Playwright framework to handle any “waits” on your behalf (without having to rely on time as a pseudo event). To make the act of selecting elements more resilient to change, Playwright also supports a collection of “selector engines” that allow you to choose the best strategy for selecting elements (via CSS selector, xpath, text content). Additionally, you can author entirely custom selector engines, and compose them together with the built-in types. This is still somewhat experimental, but we think this can enable another level of robustness to test automation: https://github.com/microsoft/play