Page Objects & Orchestrations
The functionality of Page Objects is highly advantageous. Their purpose is to improve the maintainability, reusability, and readability of test cases.
Often, users find themselves dealing with a series of steps that are repeated across multiple test cases. For instance, numerous tests for a web application might necessitate actions like logging in or logging out. Instead of resorting to copying and pasting the same lines into each individual test case, the option exists to utilize these recurrent lines in the creation of a reusable element referred to as a 'Page Object' within a Functionize test case. These Page Objects serve as a means for automation testers and engineers to adhere to the DRY principle (Don't Repeat Yourself).
Moreover, Page Objects contribute significantly to the ease of maintenance by lending an object-oriented structure to your test cases. For instance, visualize a scenario where you are dealing with a test suite encompassing 500 test cases, out of which 200 demand a login and logout process for each run. What if the login sequence undergoes a slight alteration, necessitating the addition of a new line or two? In the absence of Page Objects, every single test case would mandate manual updating, thereby introducing opportunities for human error and consuming a substantial amount of time. However, within Functionize, thanks to Page Objects, the process becomes streamlined. A modification in the login steps can be made at a single location, automatically propagating the updated flow to each test case utilizing the respective Page Object.
Functionize offers the capability to execute multiple test cases across various projects, providing the option to establish a test execution run order and enabling improved organization of test groups and types. These orchestrations can encompass 10s, 100s, or even 1000s of test cases, accessible from anywhere globally, and compatible with any browser or emulated mobile device. Functionize empowers users to create both single and group orchestrations.
In the case of a Single Orchestration, a 'bucket' can be created containing a group of tests intended to be executed either in parallel or sequentially. Test cases can be selected using filters such as projects, tags, and folders.
On the other hand, a Group Orchestration allows for multiple 'buckets,' similar to the single orchestration scenario described above. With group orchestrations, however, there exists greater granularity in organizing the orchestration for enhanced control.
Orchestrations within Functionize enable users to execute multiple test cases across various projects. This feature facilitates continuous testing by allowing test cases to be grouped and executed effortlessly with a single click. Furthermore, Orchestrations seamlessly integrate with CI/CD pipelines, contributing to the reduction of the development lifecycle, resulting in faster code releases.
Additional benefits include:
- The ability to establish a run order for test executions
- The option to schedule orchestrations and generate logs
- Automated initiation of tests through APIs, utilizing a company's existing CI/CD or overall system
- Enhanced organization of test groups and types
- Watch Create an Orchestration.mp4 (Duration: 9:31)
- Read Create an Orchestration
You are now ready to move on to Training Session 4 - TDM, Settings & Integrations