|User Guide / Projects and project items|
A TestArchitect project is a container for all assets required for your testing efforts relating to a specific project. A project is included in a repository, and may coexist with other projects in that repository.
Test procedures are authored in the test modules and actions. Test modules provide the more generalized business logic, with actions offering the lower-level "building blocks" of the test implementation. This modularity provides for faster development of tests, improved division of labor, re-usability of test components, and rapid adaptation to changes in AUT (application under test) versions and platforms.
With the use of data sets, test data can be completely isolated from the test procedures. This renders tests more manageable. It also provides for the flexibility of allowing new sets of test data to be introduced at will, with no modification of test procedures required.
Test modularity, as well as readability, is further enhanced through the presence of TestArchitect interfaces. These versatile project items map application-specific identifiers of windows and controls to logical names of your choosing. This allows user-friendly names to be used to reference GUI elements of the AUT within your actions and test modules. The major benefit is that test procedures can be isolated from changes to the user interface of a tested application, further reducing maintenance overhead.
Picture checks are reference images, also referred to as baseline pictures. They are used to verify the correctness of pictures and graphics displayed by the AUT during testing.
Finally, for each test run, TestArchitect generates a report containing the results of the automated test.