Search
Managing Extensions
-
Integrating Postman Collections in Functionize Tests
OverviewFunctionize allows you to execute Postman API collections directly within a test case. This enables workflows where you can perform an API action, such as creating a deal, and then capture a value from the API response, like a deal number. This ...
-
Passing Inputs to Custom Extensions in Test Cases
OverviewFunctionize Extensions provide powerful, reusable logic that can be integrated directly into your test cases as pre/post-action hooks or as a standalone Extension Action. A common use case is creating an extension that requires dynamic inputs du...
-
Parameterizing cURL Commands in Extension Actions
OverviewFunctionize supports parameterized cURL commands using variables, which allows for dynamic and reusable API requests within a test. This can be achieved using the cURL Extension step combined with Test Data Management (TDM) or Page Object (PO) p...
-
Using the Extension – cURL Action
OverviewcURL (short for Client URL) is a command-line tool used to transfer data over various network protocols. It communicates with web or application servers by specifying a URL along with the data to be sent or received.The Extension – cURL Action i...
-
Using an Extension to Modify Extracted Values Before Input (Uppercase Scenario)
OverviewThis guide explains how to leverage a Functionize Extension as a pre-hook to modify a value extracted from a webpage, specifically to convert it to uppercase, before it is used in a subsequent input step.Goal: Read a value from the local variabl...
-
Understanding Post-Hook and Pre Hook Mapping for Extensions on Download Actions
OverviewTests that include the file like XMLtoTEXT extension may fail if the extension is incorrectly configured on a Download action. When the extension is set to run before the file is downloaded, it has no file to process. As a result, the converted ...
-
Understanding Extensions
Functionize Extensions, also known as microservice endpoints, expand the possibilities of your test executions by making the Functionize platform fully programmable. Extensions expose our runtime object model, allowing you to manipulate and interact wit...
-
Creating Extensions
Functionize Extensions, or microservice endpoints, provide powerful flexibility and control over test executions by exposing the runtime object model. Extensions enable users to manipulate runtime values such as input data, uploaded/downloaded files, sc...
-
Mapping Extensions
Once an Extension is created, it must be mapped to a test action, test case, or orchestration before it can be used. Extensions can be mapped at different points of execution and can be configured directly in Architect, on the Test Detail page, or in S...
-
Using Post-Test & Post-Orchestration Extensions
Functionize provides the ability to run Extensions after a test or orchestration completes. These post-hook Extensions are often used for integrations—such as pushing results into a test management system, updating dashboards, or notifying downstream se...
-
Understanding the Extension Object Model
Extensions in Functionize expect an HTTPS POST request with a JSON payload as the function input. This payload provides complete context about the current test case, orchestration, variables, and step being executed. Example Input Structure{ "orchestr...
-
Additional Extension Samples
Below are sample .json objects that may be passed into an Extension with these particular Action Types. In addition to the current action information, previous action data will also be sent so that multi-step information can be processed within the Exte...