Tests for Integrates's url paths changes

Problem to solve

We need to enforce the way we test url paths by extending it so we cover all paths. If we introduce an url change it could damage some parts if we've made a minor mistake.

Intended users

Integrates's users.

User experience goal

No wrong urls provided to the users.

Proposal

We should check url paths consistency for avoid commiting changes to production that affects some of the platform functionality.

What does success look like, and how can we measure that?

If we commit changes in Integrates's paths with any missed change or typo, tests fails.