Search
Configuring Test Cases
-
Understanding Component Model tab
OverviewDuring each test run, two files are generated: componentResults.jsonl and stateComponentResults.json. These files are primarily used to train maintenance and optimizer models and to serve as inputs for those services. They provide a detailed rec...
-
Handling File Uploads in API Requests (multipart/form-data)
Overview of InquiryUse Case: Sending a JSON file as part of a multipart/form-data request.Context: The API endpoint is for creating builds on the TIBCO Flogo data plane.Technical Example (cURL)The request structure follows the standard multipart/form-da...
-
End-to-End PDF Validation Workflow in Functionize
Validating Dynamically Generated PDFs in FunctionizeFunctionize supports workflows where a unique PDF is generated during each test run, such as during a policy sale. While an Architect cannot directly validate PDFs opened in a browser, you can validate...
-
Verifying System-Generated Alerts in Automated Tests
OverviewSystem-generated alerts, such as browser alerts, cannot be directly read or captured during automated test execution. This is because they block all system interaction until they are accepted, preventing automation tools from validating the aler...
-
Dynamic File Selection for Multiple Environments using TDM
This guide details the procedure for configuring the Test Data Management (TDM) platform to dynamically select and use different data files for distinct environments, such as Quality Assurance (QA) and User Acceptance Testing (UAT).1. Prepare the TDM D...
-
Downloading the Original Data Source File in TDM
Overview This document outlines the process for downloading the original source file for a dataset within the TDM platform. By default, all files are downloaded as .csv. The instructions below allows users to access the file in its originally uploaded f...
-
Recording Browser-Level Security and Privacy Error Pages
OverviewThis document explains the technical limitation that prevents the Functionize Architect from recording or interacting with browser-level security and error screens, specifically Privacy Error screens. This limitation is inherent to the browser's...
-
Context Switching (Tabs, Iframes, Pop-ups)
1. OverviewContext Switching is the process of redirecting automation focus from one browser context (such as a tab, window, iframe, or pop-up) to another. The primary purpose is to ensure the system interacts with the correct element during actions li...
-
'Select Folder' Option Missing When Copying a Test Case Overview
When copying a single test case, the Select Folder option may not appear in the copy dialog. This is expected behavior and depends on where the copy action is initiated in the application.How It WorksCopying from the Test Details PageWhen you copy a te...
-
Verifying Dynamic Element Styles (e.g., Background Color)
Problem: How to Verify Dynamic CSS Properties?In many web applications, elements change style based on user actions or application states—for example, a button turning green after a successful action or an input box showing a red border on error.A Visu...
-
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 SettingsArchitect settings can be configured while using Architect by access...
-
Understanding Test Settings
Functionize’s Test Settings feature allows you to configure every aspect of a test, from basic information such as name and tags, to advanced execution behavior like webhooks, timeouts, cookies, headers, authentication, and alerts. These settings ensure...
-
Understanding Test Action Settings
Each test action in a Functionize test case has its own settings, flags, and options that allow you to fine-tune behavior. Action Settings can be accessed in two ways: via the Test Details page or via the Slider View.Accessing Test Action SettingsMethod...
-
Configuring mTLS for Tests
Mutual TLS (mTLS) is a two-way authentication mechanism that verifies both client and server identities by validating their TLS certificates. Unlike standard TLS, which only authenticates the server, mTLS provides bidirectional verification. This ensure...