The Architect is used to create test cases by moving through the site workflow. This solution removes the need for scripting in almost all cases. It creates fully functional cross-browser test suites. Like all systems that use machine learning, it works best when it has as much data as possible to process. It then uses data to interact with the UI successful at execution, resulting in easily built, robust test cases.
Deploying Architect gives you the capability of creating test cases with a few clicks of the mouse and limited technical experience.
Access and Launch Architect
Once logged in, select the project to create the new test case in.
From the Functional Tests page, click on New Test then select Architect from the dropdown menu. *If the Architect option is missing, reach out to Functionize support to get it enabled.
- The Create New Test window will display.
Enter the necessary information for the Test:
- Enter or verify the starting URL.
- Select the I understand... box.
- Select the Start recording automatically if you wish Architect to begin recording the application under test upon opening.
- Configuration options There is typically no need to alter this section, but the user can make changes accordingly to the available options.
- Region: The cloud data center where your test is executed. By default Functionize will select the region. If necessary, you may select the region in which to run your test.
- Device: If multiple browsers and/or mobile devices have been enabled for the project, they can be selected here. If nothing is selected, the test will be available on all enabled browsers and devices.
- Orientation: Select Portrait or Landscape if needed.
- HTTP Auth: Enter the credentials for basic authentication if needed to access the URL under test.
- Select Save Settings if it is desired to save the above credentials for future test creation.
- Click Start to launch Architect.
Please find a video tutorial on getting Started with Architect here >> How to Use Architect
Record and Save a Test in Architect
- Architect will launch with the URL specified in the Create New Test modal. Click the Record button if you did not select "Start recording automatically" earlier.
- If cookies or HML5 storage exist on the browser, Architect will prompt to clear some or all of the cookies. Make the choice that is appropriate for the test case. NOTE: If the cookies are kept, the test will not have those cookies at executions unless specifically injected via custom action.
Select Clear HTML Storage, click Delete All, then click Continue. To record without clearing cookies, click Continue.
- Each test begins with a Pageinit Action in order to record the initial URL under test.
- Perform the actions on your site to be recorded in your test. Once you are finished, click Save.
- Enter a Name for your test. Click Continue.
- Functionize will process your test, then prompt you to select if this is a Test Case or a Page Object. Click Save to be returned to the Functional Tests page without immediately running the test. Click Save & Run Test to execute the test now.
- The Functional Tests page will display gear icons over each each enabled browser's icon to indicate the test is currently running.
Architect Options and Settings
Collapse/Expand: Click the icon in the upper right to collapse the panel when needed. Click the icon again to view the full panel.
Add an Instruction: Type a new instruction in the field at the bottom to build in documentation about what your test is doing while recording.
Insert Action: Click the blue Insert button to open the Action panel. Click the minus icon to close the panel. Learn more about the available Action Types.
Settings: Open the Action panel and click the gear icon to open Settings related to how Architect records your tests. NOTE: If it is preferred to always have cookies/data cleared before starting a new test, toggle "Always clear browsing data" to ON. Learn more about Architect Settings.
Edit an Action: Click the white dot to the left of the Action. The details panel will open with data and settings for that Action.
Reorder an Action: Hover over an Action to drag it to another position in the test.
Delete an Action: Hover over an Action and click the X icon to the right.
Add a Verify: Click the Verify button, then select the element to be verified on the site under test.
Add a Visual Check: Click the Visual Check button, then select the element to be visually verified. Set the necessary match percentage required for the Action to pass. Click Save.
Add a Hover: Click the Hover button, then hover over the desired item and select the element which should appear on hover.
Cancel the Test: Click the X to stop the test. Select one of the four options presented, click Continue.
Pause the Test: Click the red button to pause the test recording. Click the button again to resume recording.
Save the Test: Click the Save button and follow the process as detailed above.
Don't Forget Your Verifications
With AI Assist turned on, a user is unable to save a test without verifications.
Keep in mind a test without verifications is not actually testing anything!
See also Best Practices Using Verifications
Learn more about Architect Test Creation in this webinar.