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.
Simply stated: deploying the Architect gives the user the capability of creating test cases with a few clicks of the mouse and limited technical experience.
To Access and Launch the Architect:
- Go to the Functionize app
- From the Projects tab , hover over a project then select View Project
- Once in a project, select the Create New Test drop-down and then select Architect.
- If the Architect option is missing, reach out to Functionize support to get it enabled.
A new window will pop open. Before starting the test:
- Enter or verify the starting URL
- Select the I understand box
- Configuration options – there is typically no need to alter this section, but the user can make changes accordingly—simply select the down arrow to open and display the configuration options and make selections as needed.
Select Start Test
Once the test is started, a new tab will open and redirect to the starting URL. The Architect will appear in the top right corner of the browser window.
Select the Record button to deploy the Architect.
A box may pop open if any additional cookies need to be cleared before running the test scripts. If cookies or HML5 storage exist on the browser, the Architect will ask if to clear some or all of the cookies. Make the choice that is appropriate for the test case, however, remember that if the cookies are kept the test will not have those cookies at executions unless specifically injecting the cookies into the test case as a custom action. For example, if the user is logged into an app and do not include login actions in the test case or use a page object to log the user in, that would prevent the test from executing successfully because the machine in the cloud doesn’t have the cookies that the machine does.
To clear the cookies, select the checkbox(es) then select Continue. To run the Architect without clearing cookies, simply select Continue. After selecting Continue the page will refresh and launch the Architect.
NOTE: If it is preferred to always have cookies/data cleared before starting a new test, then go to Settings in Architect, and toggle "Always clear browsing data" to ON.
The Architect will then load and the first action will automatically populate, which is a page-load of the current URL.
Additionally, various buttons and controls will appear that allows the user to complete desired actions.
Verify: click the flag and click an element to verify it exists in its current state.
Hover: Hover actions are most often required when dropdown menus do not require a left-click to activate.
Plus icon: Access all advanced action types such as Navigate, Email, Wait, API, File Viewer, DB Explorer, and Page Variables.
Type instructions: Build test documentation by typing the instructions in the Architect.
Drag and Drop: After actions have been added, the order can be changed by dragging and dropping the actions and inline test documentation into the preferred order.
Save, stop, pause: Allows the test creation process to be stopped, started and controlled at a high level. Up arrow: At the top right side of the Architect is a small arrow that collapses the Architect to free up space.
Up arrow: At the top right side of the Architect is a small arrow that collapses the Architect to free up space.
*Troubleshooting Test Case Creation in Architect*
- Switching tabs while recording a test with Architect can cause screenshot issues. We advise opening a new window if a user is multi tasking.
- Switching to a new tab while recording a test case with Architect (specifically a Functionize tab) will lose the test case and close Architect
Learn more about Architect Test Creation in this webinar.