>> Only if you run pure server side applications that’s simple. End to End testing is less about "making the front end do all the work" and more about being fr

>> Only if you run pure server side applications that’s simple. End to End testing is less about "making the front end do all the work" and more about being free of mocks and synthetics. Just because the front end exercises my server, does not mean server devs get a pass on testing API down. The tests I write should inform the data your sending and receiving, they should function as an example of inputs and outputs of what to expect in the system. Those timing issues are either a real front end problem, or a server problem (and my own tests should have noted that I did not meet the SLA).