Design your test architecture
Plan your test architecture with guides on repository configuration and test suite structure.
Last updated
Plan your test architecture with guides on repository configuration and test suite structure.
Moving from your first test to a full-scale automation suite requires shifting your focus from "how to write a command" to "how to design a system." A well-architected Maestro suite ensures that your tests stay fast, reliable, and easy to maintain as your application evolves.
To build this system, you need to address two distinct layers:
Where your tests live
How they are structured
To help you navigate these layers, you can explore the best practices into the following specialized guides:
Repository configuration: Learn where to store test files or choosing a high-level organization model (User Journeys vs. Features). It will help you decide on your folder structure and repo strategy, preventing refactoring later.
Structuring your test suite: Check this guide if you are ready to write YAML files and want to know the rules for naming, sub-folders, and using tags to filter execution. Learn the "Maestro Way" of writing modular, tagged, and parallel-ready tests.
Last updated