Search
Managing Extensions
-
Understanding Extensions
Functionize Extensions, or microservice endpoints, open up test executions to almost unlimited possibilities. Extensions open the Functionize platform to be fully programmable by exposing our runtime object mod...
-
Creating Extensions
Functionize Extensions, or microservice endpoints, provide limitless control over test executions by exposing the runtime object model. Users can manipulate input values, files, and more, allowing customization...
-
Mapping Extensions
Once the extension is created, it must be mapped to an action to be used. Extensions can be mapped to an action via the Architect recording, on the Test Detail page or Slider View.There are 2 types of mappings ...
-
Using Post-Test and Post-Orchestration Extensions
Functionize offers the ability to attach an extension to run after it ends. Post-hook extensions are used at the end of a test to integrate with test management platforms or other services while having access ...
-
Understanding the Extension Object Model
Functionize Extensions expect an HTTPS POST request with a JSON payload as the function input:{ "orchestrationRunId": "", "testId": "903915", "TDMdataSetId": "", "orchestrationId": "0", "step": {...
-
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 i...