Page Objects & Orchestrations
Page Objects
Often, users have a series of steps that are repeated across test cases. For example, a number of tests for a web app might need to login or log out of an application. Rather than copy and paste the same lines in each test case, you can use those repeated lines to create a resusable element or "Page Object" . Page Objects allow automation testers and engineers to employ the DRY principle (Don't Repeat Yourself).
Furthermore, Page Objects facilitate maintenance by making your test cases object oriented. For example, imagine that you have a test suite of 500 test cases, 200 of which need to login and log out with each use. What would happen if your login flow changed slightly and needed a new line or two? Without Page Objects, each test would have to be manually updated, creating opportunities for human error and wasting lots of time. In Functionize, with Page Objects, you can update the login set of steps in one place and have that flow automatically updated into each test case that uses the Page Object.
Watch Page Object Creation via Architect.mp4 (Duration 2:35)
Read Architect Page Object Creation
Read Adding an Existing Page Object During Test Case Creation in Architect
Read Set a Page Object in an Existing Test Case
Read Page Object Creation & Usage in NLP
Read How to Edit a Page Object
Orchestrations
Orchestrations in Functionize allow the user to execute multiple test cases within multiple projects. It allows for continuous testing where test cases can be grouped and then executed with a single click. Orchestrations also integrate with CI/CD, and shorten the actual development life cycle, releasing code faster. Other benefits include:
- Ability to set a test execution run order.
- Kick off tests automatically using APIs from a company's existing CI/CD or overall system.
- Better organization of test groups/types.
Watch Create an Orchestration.mp4 (Duration 1:28)
You are now ready to move on to Training Session 4 - TDM, Settings & Integrations