End to End Testing: How to test frontend?

Transcript

1. End to End Testing: How to test frontend? Prashast Mehra (Finn Travel)
3. Motivation? • Why should you even test the frontend? • Whats the worse that could happen? • I have unit tested my js code and api’s. So I don’t need this, right?
6. Benefits • A simple integration test will make sure that you never break existing features while making new stuff. • You won’t be scared to update npm dependencies. • You will have more confidence in your production app. • Developer experience will be quite smooth. Etc…
8. Cypress The web has evolved. 
 Finally, testing has too. Fast, easy and reliable testing for anything that runs in a browser.
10. What have we achieved? • Full confidence over our frontend* • UI is consistent 99% of the time* • Upgrade design system changes with confidence*
11. Complexities • Whitelabel • In-app browser • IE
16. • Visual Regression Testing • API Testing • Javascript Testing • Test Runner • Build Artifacts What this talk is all about
17. Visual Regression Testing
18. Upgrading Troika?
19. Screenshot Diff: After upgrading troika Before After Diff
24. Testing API’s
26. Testing Javascript
31. Test Runner
34. Build Artifacts
37. What exactly went wrong in this build:
39. – Anonymous (or maybe me) “If you don’t like testing your product, most likely your customers won’t like to test it either.”
40. Thank you