top of page

Practical Automation

Automation should support development, not slow it down. Frameworks should start small, focus on core workflows and scale intentionally

Framework Focus

  • MVP-first approach: Build to Learn phase , instead of spending a year building every possible feature, you focus on core value proposition by launching the smallest viable product that still solves the problem.
​
  • Maintainable structure: Organization of code and folders to ensure that when new team members join and have a good understanding of everything within fast by keeping logic, code and UI in separate organized layers 
​
  • Clear Definition: Before the development of code knowing what an application does as well as what an application does not do. Allowing for scope creep to be prevented.
​
  • Reusable Components: Utilization of reusable components that will reduce the amount of time it would need to build something from scratch. 

Tech Stack

  • Playwright for modern browser and web application automation 
  • Cucumber for readable behavior-driven tests 
​​​
bottom of page