Getting Started with Architect

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 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:

  1. Once logged in, select the project to create the new test case in.

  2. 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.

mceclip0.png

The Create New Test window will display:

mceclip1.png

  1. Enter or verify the starting URL.

  2. Select the I understand... box.

  3. Select the Start recording automatically if Architect should begin recording the application under test upon opening.

  4. 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.

  5. Select Save Settings if it is desired to save the above credentials for future test creation.

  6. Otherwise click Start to begin Architect test case recording.

Once the test is started, a new tab will open and redirect to the starting URL.  Architect will appear in the top right corner of the browser window.

VIDEO ALERT! Please find a video tutorial on getting Started with Architect here >> How to Use Architect or continue below:

Getting_Started_1.png

Click the Record button  to deploy Architect and start recording.

mceclip0.png

*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, Architect will prompt 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. 

To clear cookies, select Delete All and Clear HTML Storage then select ContinueTo run the Architect without clearing cookies, simply select Continue. After selecting Continue the page will refresh and launch the Architect. 

mceclip1.png

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.

  mceclip2.png

The page will refresh and Architect will then load the first action as a pageinit for the starting url.

mceclip3.png

Additionally, various buttons and controls will appear that allow the user to complete desired actions.

Flag.png Verify: click the flag and click an element to verify it exists in its current state. 

Pointer.png HoverHover actions are most often required when dropdown menus do not require a left-click to activate. 

ADV.png Advanced toggle: Advanced mode can be used in two ways. The first is to perform an advanced verification of dynamic data using the Attribute EditorSecondly, it can be used to access the Element tab which is where advanced users can script custom JavaScript, walk the DOM, override outcomes, find desired target elements using specific selectors, or override outcomes entirely.

Plus.png 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 Architect.

Drag_and_drop.png 

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.png 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.png 

 

Saving a Test Case in Architect

Once the test case is complete, the user can save the test case.  To do so,

1. Click Save in Architect.

2. Save the Test Name, then click Continue.

*Remember to add verifications in the test. See also Best Practices Using 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 AI Assist below: 

mceclip3.png 

3. The user will be routed back to the Functionize dashboard once the completed test case has been saved. Note: Project Details will pop up, asking the user to identify the test type.  Please select Test Case or Page Object, then click Submit.

Learn more about Architect Test Creation in this webinar