Hello all 👋 .
For as long as I can remember at my current workplace we've struggled with making test assertions against copy changes that are dictated by a Backend Team.
Since Frontend and Backend teams are disjointed, its very easy for Backend teams to make copy updates without notifying Frontend. This leads to rollbacks at work which are pretty noisey and distract us from getting actual work done.
The reason i'm asking this question is because we've talked about moving towards making assertions against just test-ids instead of copy but there are good arguments for both sides.
For example,
Arguments for making assertions against Backend copy:
Arguments for not making making assertions against Backend copy:
So, I'm pretty curious what others think about this and what solutions ya'll have come up with at your workplaces to mitigate these types of issues.
Thanks in advance for your time 🙏
This thread is trying to answer question "What are your thoughts on making assertions against Backend copy changes and what solutions have you come up with to mitigate these issues?"
Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email [email protected].