Search

Understanding Architect Settings

Functionize Architect includes many configurable settings to tune the test creation and execution experience to your requirements for the Application Under Test (AUT).

Architect Settings

Architect settings can be configured while using Architect by accessing the gear icon.

  • Faster Performance
    • What it does: Reduces ML data collection to speed up recording.
    • When to use: Only on very large or heavy pages.
    • Recommended: Off (keep ML data for accuracy).
  • Use Page Init Actions
    • What it does: Reuses recorded init actions (like login, navigation).
    • When to use: If the same flow is repeated across tests.
    • Recommended: On.
  • Coverer
    • What it does: Enables capturing double-click actions.
    • When to use: If your AUT requires double-click interactions.
    • Recommended: On.
  • Keep Tooltips on Verify
    • What it does: Records tooltips during Verify steps.
    • When to use: If validations depend on tooltips.
    • Recommended: On (disable only if not needed).
  • Mouseover
    • What it does: Captures hover-over events.
    • When to use: For hover-based menus or UI actions.
    • Recommended: Off (enable only if AUT requires hover).
  • Mouseout
    • What it does: Captures hover-out events.
    • When to use: For hover menus with exit triggers.
    • Recommended: Off.
  • Focus
    • What it does: Stops AUT from taking focus away from Architect.
    • When to use: If recording gets interrupted by popups or focus shifts.
    • Recommended: On.
  • Long Text
    • What it does: Removes the 250-character input limit.
    • When to use: When testing forms with long text fields.
    • Recommended: Off (enable only if needed).
  • Force 100% Zoom
    • What it does: Forces browser zoom to 100%.
    • When to use: If AUT UI breaks due to zoom level.
    • Recommended: Off (enable only for zoom issues).
  • Enable AI Assist
    • What it does: Provides AI hints during recording.
    • When to use: Always useful.
    • Recommended: On.
  • Disable Service Workers
    • What it does: Prevents caching issues caused by service workers.
    • When to use: For AUTs with aggressive caching.
    • Recommended: Off (enable if caching causes issues).
  • Enable Tab Keypress
    • What it does: Records “Tab” key actions.
    • When to use: For keyboard navigation or tabbing forms.
    • Recommended: Off (enable only if needed).
  • Enable Small SVG Children
    • What it does: Allows interaction with small SVG child elements.
    • When to use: If AUT uses SVG icons or graphics.
    • Recommended: Off (enable only when needed).
  • Automatically Capture Scrolls
    • What it does: Records scroll actions automatically.
    • When to use: For infinite scroll or lazy-loading pages.
    • Recommended: On.
  • Allow Body Target Element
    • What it does: Allows selecting <body> as an element.
    • When to use: Rarely, only for page-level checks.
    • Recommended: Off.
  • Disable Overrides
    • What it does: Prevents Architect from overriding AUT behaviors.
    • When to use: If Architect conflicts with AUT scripts.
    • Recommended: Off.
  • Always Clear Browser Cache
    • What it does: Clears browser cache before recording.
    • When to use: For clean session testing.
    • Recommended: On.
  • Disable Screenshots
    • What it does: Stops taking screenshots.
    • When to use: For very heavy tests where speed matters more than visuals.
    • Recommended: Off (keep screenshots for debugging).
  • Realtime Screenshots
    • What it does: Captures screenshots instantly during actions.
    • When to use: When debugging or verifying UI states.
    • Recommended: On.
  • Remove Sandbox Attribute
    • What it does: Removes iframe sandbox restrictions.
    • When to use: For AUTs that embed content inside sandboxed iframes.
    • Recommended: On (only if iframe issues occur).
  • Enable Pointer Events
    • What it does: Allows clicks on elements with disabled pointer-events.
    • When to use: If AUT uses custom-styled elements that block clicks.
    • Recommended: Off (enable only when required).
  • Collect ML on Keydown
    • What it does: Collects ML data on every keystroke.
    • When to use: When input fields are sensitive or dynamic.
    • Recommended: Off.
  • Always Clear Browsing Data
    • What it does: Clears cookies and storage each run.
    • When to use: If old session data interferes.
    • Recommended: Off (enable only when needed).
  • Max Download Interval (2000 ms)
    • What it does: Maximum allowed time for downloads.
    • When to use: Increase if AUT downloads are slow.
    • Recommended: 2000 (default).
  • Max Pending Data
    • What it does: Sets the size of the ML data queue.
    • When to use: For large/complex AUTs.
    • Recommended: 20.

ML Deep Analysis

Functionize continuously collects data during test creation and execution to fuel its self-healing engine, known as ML Deep Analysis.

  • Enabled by default in Architect v1.1.71+.
  • Can be toggled in Architect’s settings (gear icon → ML Deep Analysis = ON).
    • Note: Turning this setting off is not recommended, but may help diagnose performance issues on very complex sites. Even if disabled during creation, the engine still pulls the same data during execution as long as the test runs successfully.

Performance Management Tips

If you notice slowdowns while creating tests in Architect:

  1. Clear browser cookies and relaunch the Architect – this prevents lag from stale sessions or heavy storage.
  2. Break long workflows into modular tests instead of recording a single large test.
  3. A stable internet connection is essential – avoid recording on slow networks.
  4. Close other tabs — low browser memory impacts performance.
    • If other tabs are required, make sure the tab where Architect is recording is the first in the window.
  5. Restart the browser with only Architect open.
  6. If you need to switch pages or tabs during recording, pause the recording first, then switch.
  7. Check Chrome Task Manager (More Tools → Task Manager) to spot heavy memory use.
  8. Temporarily disable unnecessary extensions.
  9. Toggle the Faster Performance setting to on.
  10. As a last resort, toggle ML Deep Analysis OFF.

If issues persist, submit a support ticket with logs for review.