E2E Testing: One Term, Two Perspectives Sammy @Voicy Inc, | QA Leader 

What comes to mind when you hear "E2E test"? 

Two Perspectives on E2E Testing Developer Goals • Quick feedback • Minimize test run time • Reduce CI failures QA Goals • Lower test execution cost • Simulate real user behavior • Find regression risks Tension Point • Same term, different expectations • Misaligned priorities • Communication gaps 

Why We Started E2E test Automation Manual regression became painful More features = more test cases Needed automation to keep up Explored mabl, MagicPod, Autify 

The First Step Login Flow Test Most common user action Implemented in MagicPod Easy-to-use test automation tool First Success! Test passed consistently 

Then Came the Hard Part... Purpose Definition Fast bug detection? Lower test cost? Test Scope Integrate modules? Integrate all products? Ownership Debate Who owns maintenance? QA or Dev? Execution Trigger Merge to master? Before release? 

Two Types of E2E — One Word, Two Meanings 

E2E Testing: One Term, Two Perspectives Purpose Definition Lower test cost Test Scope Integrate all products Ownership QA supported by Dev Execution Trigger Weekly at first 

Lessons from Our E2E Journey Align First Set expectations before implementation Start Small Build gradually and iterate Focus on Reliability Build trust with consistent results 

Thank you If you're just starting E2E, don't aim for complete coverage. Aim for shared confidence. Let's Connect Share your E2E experiences X : @AWorkingholiday LinkdIn: masami-morita-8a7023237 Questions? Happy to discuss after Thank You Appreciate your attention