We have lots of end to end test cases to reduce the manual automation work, and the list keeps growing as we add new features.
Now we added this test cases in our development workflow, to automatically run and approve the code merge to master.
But this creates lots of other problems,
- It eats up lots of time in the development release cycle
- The probability of build failures ( so merge failures) are high as there is a high chance of a mismatch between the e2e cases and the new features.
So what is the best practice to do the 'code approval' process,
- To include all the automated test cases or
- To include only the happy path, so the build sanity is guaranteed, and any other issues will be part of QA cycle and raised against the developer