Looking for advice:

I am an #angular developer seeking for the best way for implementing #e2e #tests. What do you recommend? Playwright or Cypress? Why?

Any opinion will be appreciated!

PD: a17 and angular.dev rock.

@josep Either, they are both good.

@josep

Unusual-for-angular setup here:
gherkin > cucumber > playwright

Was difficult to set up, but now even our non-dev‘s write tests 🎉

@zyklop Interesting. I like unusual setups. I used cucumber + capybara like 10 years ago, in RoR. What has been the hard part in your setup: connecting cucumber with playwright maybe?
@josep
Yes. I can’t really describe it as i have set up once some time ago and there were only one or two example repos that came close to what I needed.

@josep

Now it looks odd, how a instance of a browser gets initiated by #playwright and passed to the global #cucumber scope - but it somehow works. And the benefits are huge. We are like ‚how could we live without’⁉️
¯\_(ツ)_/¯

I also try to achieve a as-usual-as-possible setup but when I implemented that into our project there was no ‘usual setup’ for something that includes #gherkins into a #Angular project.

I don’t know if there is one nowadays.

@josep Personally I'm partial to #WebDriverIO since it actually uses the #WebDriver specification and is a little more future-proof as a result IMHO. Also comes with #Angular integration!

```
$ ng add @wdio/schematics
```

https://webdriver.io/

WebdriverIO · Next-gen browser and mobile automation test framework for Node.js | WebdriverIO

Next-gen browser and mobile automation test framework for Node.js

@develwithoutacause I did not know about WebDriverIO. I will definitely have to try it before making a decision. The API looks clean. Thank you!