Hi Luca, that’s a good approach, I think that all the team is accustomed to this flow, is it?
And since you have a dedicated QA team, it’s normal that they use Selenium, after all, it’s a standard nowadays 😉

Some questions of mines:

• do you leverage the NG testing tools testing on JSDOM or in the real browser? (I do not know pretty well the NG testing tools, but I think that the tests with the real browser, is it correct?)
• what kind of bugs usually escape the dev team control? Which are the kind of bug related only to the frontend that usually hits the QA team? Only the ones that come from working with a real backend/data?

In my article, I speak about stubbing the server too (see the “you do not need to simulate strange…” chapter after the video) but I think that I do not give it the right importance or it’s not enough clear 🤔 I think I should re-write it putting more emphasis on the topic, yours is a good feedback 😉

p.s. I know that the NG team was thinking to add Cypress to the official CLI… 😊