Well, I'd normally recommend stubbing any volatile endpoints, but if they change frequently maybe that isn't your best course of action If your team also has ownership of this volatile data source, it sounds more like a question of visibility and responsibility. If the team makes a change, they should also be aware that their changes could break the e2e tests. Give them a way to easily see the tests. Even better if they are able to fix the tests as they go