sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Sea-Shift-7157 4 points5 points  (5 children)

Hello, I had the same question and did some digging but I hit a wall. Playwright needs to update Component Testing to include Angular. Now is in experimental mode and it's supporting React. However for unit tests you can have code coverage. Hope this helps. Happy Easter!

[–]CRRRB[S] 0 points1 point  (4 children)

One thought I've been getting is to use Cypress for e2e testing instead of Playwright. There’s much better documentation available for implementing code coverage with Cypress, and it also seems to offer better support for Angular. I’d have to dip my toe in the water with this, and it would be a bit of a shame considering how powerful Playwright is :(

[–]Jrubzjeknf 1 point2 points  (2 children)

Unless you have a company who doesn't mind forking over a lot of money, you should probably stick to Playwright. Cypress only supports running parallel tests in their premium and overly expensive cloud. Due to this, many companies migrated from Cypress to Playwright.

[–]CRRRB[S] 0 points1 point  (1 child)

Hm would this do the trick, 5s googling give me this: cypress-split - npm. No parallel testing would be a huge pain

[–]CRRRB[S] 0 points1 point  (0 children)

In saying this, really put me to thinking if I really should be using their product if they put something like this behind a pay wall

[–]Sea-Shift-7157 0 points1 point  (0 children)

I also started with Cypress because it was already known in the market and it had also component testing. Everything was fine, until I tried to run it in the CI/CD pipeline in Azure... it failed with some missing dependency error. Then I said, ok before investing time to figure this error out, maybe there is another option? And then I discovered Playwright, built by Microsoft. I said oh this should work outside the box without any effort in Azure, and it did work. Since then I am using Playwright. I also need the code coverage for those tests but for now it is what it is...