Getting Started with Architect

Functionize Architect Overview

The Architect is used to create test cases by navigating through the site workflow. This solution eliminates the need for scripting in almost all cases. It generates fully functional cross-browser tests. Like all systems that utilize machine learning, it performs best when it has access to as much data as possible for processing. It then leverages this data to interact with the UI successfully during execution, resulting in easily built, robust test cases.

Deploying Architect gives you the capability of creating automated test cases with a few clicks of the mouse and limited technical experience.

 

Access and Launch Architect

  1. Once logged in, select the Project to create the new test case in
  2. On the Test Case Listing page, click on the New Architect Test button
    Note: If the Architect option is missing, reach out to Functionize Support to get it enabled.


  3. The Create New Test pop-up window will display


  4. Enter the necessary information for Functional Testing tab:
    • Enter or verify the starting URL
    • Select the I understand… checkbox
    • Select the Start recording automatically checkbox if you wish the Architect to begin recording the application under test (AUT) upon click Start button - this is necessary if your AUT has a URL redirect with the initial starting URL
    • 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, but if necessary, you may select the Google data center region in which to run your test
      • Orientation: Select Portrait or Landscape, if needed
      • Desktop/Mobile: If the particular project is enabled for creating test cases on both the Desktop and Mobile platforms, then select the Desktop/Mobile option accordingly, by default, Desktop is selected
      • HTTP Auth: Enter the credentials for basic authentication if needed to access the URL under test
  1. Select Save Settings, if it is desired to save the above credentials for future test creation
  2. Click Start to launch the AUT and Architect

Please find a video tutorial on getting Started with Architect here >> How to Use Architect

 

Record and Save a Test in Architect

  1. Architect will launch with the URL specified in the Create New Test pop-up, then click the Record button - if you did not select Start recording automatically setting earlier


  2. If Cookies or HTML5 Storage exist in the browser, Architect will prompt to clear some or all of the cookies. Make the appropriate choice for the test case
    Note: If the cookies are retained, the test will not have those cookies during executions unless specifically injected via a custom action.
  3. Select Clear HTML Storage and Clear indexedDB Databases, click Delete All, then click Continue - if you want to record without clearing cookies, just click Continue


  4. Each test begins with a Pageinit Action in order to record the launch of the initial URL under test


  5. Walk through the test flow on the site to be recorded for the test, once finished, click Save
  6. Enter a Name for the test and click Continue


  7. Functionize will save the test to the Tester's account in the cloud, a prompt will appear to select Test Type if this is a Test Case or a Page Object, click Save to be returned to the Test Listing page without immediately running the test 


  8. The Test Listing page will display gear icons over 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 and click the icon again to view the full panel


  • Add an Instruction: Type a new instruction in the Type Instruction field at the bottom to build in documentation about what the test actions are doing while recording


  • Insert Action: Click the blue Insert button to open the Architect Actions sidebar panel and click the Minus button  to close the Architect Actions sidebar panel - learn more about the available Action Types



  • Settings: Open the Architect Action sidebar panel and click the gear icon to open Settings related to how the Architect records your tests
    Note: For example, 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 Architect Action Details sidebar panel will open with data and settings for that Action that the Tester can update and click Save in the Architect Action Details sidebar panel


  • 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 icon to the right


  • Add a Verify Action: 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, select the Visual Check Type to 'Baseline Comparison' or 'Step Comparison,' set the necessary Visual Match Requirement % for the Action to pass and click Save in the Visual Check pop-up



  • Add a Hover: Click the Hover button , then hover over the desired item and click on the element which should be hovered on during test execution


  • Cancel the Test: Click the button to stop recording the test, select one of the four options presented and click Continue


  • Pause the Test: Click the red button to Pause the test recording and click the red button again to resume recording




  • Save the Test: Click the Save button and follow the process as detailed above


Don't Forget Your Verifications

If the AI Assist setting is turned on under Architect settings



A Tester is unable to save a test without at least one verification


Keep in mind a test without verifications is not actually testing anything!

 

Please find additional details on Verifications here >> Best Practices Using Verifications

Please learn more about Architect Test Creation in this webinar