How to build API mock and make frontend developers happy

Typical development of a feature for web projects looks like this: Planning -> Backend -> Frontend -> QA -> Release. At the beginning of the sprint, the backend starts working, the frontend waits for working staging and documentation on the new contract, and a QA waits for both of them and tries to have time to test everything within the sprint. 

I'll talk about an approach to change engineering practices and bring testing closer to development. We'll talk about how QA can start testing in parallel with developers, how to abstract from the data provider and organize mocking.