Thank you.
Murat Çorlu

The thing is that a project is a living and changing thing. The requirements and implementation will change. This may not happen with a smaller project but definitely will happen in enterprise. In an agile project, the specs change all the time and you need to be careful not spend more time on updating the mocks and features than on the features :D. A good approach is to get the backend guys to generate schemas for the endpoint(or swagger definitions) against which you can than write if the api changes the test will fail and you will need to fix the changes. It happened a lot that changes were introduced in the backend and since the front end was using mocks it was discovered later in the process and caused a lot of bugs

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.