Good Practices When Creating E2E Tests at Skeelo
Article Summary
Skeelo's QA team built a scalable E2E testing framework using Python + Appium. Here's the architecture that keeps their mobile tests maintainable as the app grows.
Lucas Castro from Skeelo Engineering shares their battle-tested approach to mobile test automation. The team chose Python for its low learning curve and Appium for cross-platform support, then built a structure that actually scales.
Key Takeaways
- Page Object Model centralizes UI changes in single classes for easier maintenance
- Triple A pattern (Arrange, Act, Assert) keeps test code clean and self-explanatory
- Clear folder structure separates pages, tests, utils, and config responsibilities
- Each page class encapsulates elements and actions using object-oriented principles
- Slack webhook integration notifies team of test pass/fail status automatically
Combining Page Object Model with Triple A pattern creates E2E tests that can keep pace with rapid mobile development without becoming a maintenance nightmare.
About This Article
As Skeelo's mobile app grew, their E2E test code became harder to maintain. UI changes were scattered across multiple test files, which meant updates had to happen in several places at once.
Lucas Castro's team adopted the Page Object Model pattern. They created dedicated page classes that encapsulate UI elements and actions, so maintenance for each screen happens in just one location.
Skeelo combined POM with the Triple A pattern structure to build test automation that keeps pace with rapid mobile development. Their Python and Appium framework now scales better and costs less to maintain.