Test Author is a one-stop web application that allows you to automate your end-to-end business use case by using Conga Product APIs as well as third-party custom APIs without writing a single line of code. You can use this no-code API automation tool to create and execute end-to-end flows in the environment of your choice and get reports for the same. All of this and more can be done using the Test Author UI.

To get started, you can use the Conga Repository which contains the Conga API templates. These are ready-to-use API templates for out-of-the-box Conga product features. You can use these API templates to create a test step, stitch multiple test steps to create a test case, test the standalone test case, or add multiple test cases to a test suite and trigger execution for the entire test suite. To test these APIs you need to create an environment record where you can point and test the APIs. Similarly predefined test steps and test cases are available in Conga Test Step and Conga Test Case. You can test them and clone them to further customize as per your requirements.

All details that an API offers (Request Type, Headers, Request Body, Path Param, Query Param, etc.) are captured in the template. An API template is a reusable component you can create multiple test steps, which is nothing, but a different variation of the same API as required for different business flows. You can also create customized API templates (for Conga custom APIs as well as any third-party APIs) and then use them to create test steps and test cases. Before you get started with the test step creation, you must create an environment record for testing purposes.

Using the API template, you must create a test step. A test step is a variation of the API template. You can create as many variations as you want, as per the business flow requirements, using the Conga API Template, or your API template created using Test Author. For example, you can build an "Add line items to a cart" API with variations like add standalone product to cart, add bundle product to cart, add bundle with options to cart, add multiple products to cart, etc. You can parameterize the arguments passed in a test step using an expression builder so that every API call can send unique data.

A test case is an end-to-end business use case. It is created by stitching test steps in the required sequence and generating a user flow. You can extract and use values from one API in the flow to another API. You can put verification checks on each test step's responses to assert expected values and you can insert a wait between two test steps. After creating a test step or a test case, you can run them individually. For that, you must have an environment record already created and an access token generated. This token, once generated, is valid for one hour. After creating an API template and a test case you can run a test to check the response.

A test suite comprises multiple test cases added in a required sequence and grouping to generate an execution flow.

The Test Execution Dashboard lists the test suite executions in progress in the Active tab and those scheduled for a later date in the Scheduled tab. Details such as execution, execution category, status, suite, environment, total test cases, description, and execution start time are shown in the Active tab. Job name, active/inactive, suite name, environment, frequency, description, and user details are shown in the Scheduled tab. You can trigger test suite execution from the Active tab or use the Schedule tab to schedule test execution with email recipients to receive execution result via email on completion of the execution. The email contains an execution history link from where the execution result can be downloaded. The email also includes a ZIP file containing the complete report in HTML format. Ensure that the email recipient is not blocked by the IT department from receiving email from Test Author.

The Execution History tab shows details of all past test executions.

The Compare Reports tab also lists all the executions and you can compare the completed executions for further analysis.

The File Store feature lets you upload files under different Conga Product categorizations, which can be used in the request body (form-data files only) under the API template and test step. Files up to 20 MB are supported.

Use the Backup feature to backup all the existing records of Environment, API Templates, Test Step, Test Case, and Test Suite.

When you log in to Test Author, you are directed to the home page, which consists of two panels. The panel on the right has shortcuts to Test Author's features, whereas the panel on the left lets you navigate to the same set of features. All the workflow operations mentioned above, except access token generation, have a shortcut in the right panel.

The administrative tasks that need to be performed to enable the features and functionality of Conga Test Author can be done in the Admin UI.

Translation support: Test Author supports nine locale, where English (United States) is the default language and others are English (United Kingdom), French (France), German (Germany), Italian (Italy), Spanish (Spain, International Sort), Portuguese (Portugal), Dutch (Netherlands), and Swedish (Sweden). However, the fields where users enter the values, are not translated.