Skip to main content

Test Composer Guide

The API Fortress Composer offers unparalleled flexibility and ease-of-use with everything at your fingertips to build tests in minutes and eliminate many duplicate tasks. Users of all skill levels may begin using the Composer with little or no training to quickly generate sophisticated functional tests. These tests may easily be reused as end-to-end integration tests and load (stress) tests. In turn, load tests may easily be reused as monitors for performance testing.

Learn more about End-to-End Tests / Integration Tests

Read the following page to learn more about Integration / Multistep Testing

Visual vs. Code View#

Begin using the Composer by selecting from two versions in terms of views. With either Visual or Code view, easily make calls and add assertions for testing your APIs, and insert variables wherever needed.

  • Visual - The Visual Composer does not require coding expertise, and provides real-time suggestions via predictive text to help you create ideal API tests for your needs.

    Test Composer Visual View Pic
  • Code - The Code view is for users who are more comfortable working in code rather than a visual UI.

    Test Composer Code View Pic
API Testing Best Practices

For more information, visit our Sauce School API Testing course to research best practices and find detailed guidance.

Test Composer UI#

Use the following image as a reference for the numbered items listed below:

Test Composer Page Annotated
  1. Add Request / Assertions: This button displays all available components. If a component is not valid for the operation you are conducting, it will not be made available to help avoid mistakes. For instance, if you don’t add a POST first, you cannot add a POST Body or POST Param.

    Test Components

    NOTE: Free accounts do not give you access to all available components.
    Read descriptions of each component in the Reference section of API Fortress Documentation.

  2. Transform Component: This button allows you to easily transform an existing component into another component of the same type.

  3. Delete Component: This button allows you to delete a selected component from the test while using visual mode.

  4. Invoke Snippet: This button allows you to use a previously created code snippet stored in The Vault.

  5. Export Snippet: This button allows you to export a selected code snippet to the vault in order to be re-used later, or in another test.

  6. Save Test: This button saves your progress.

  7. Run Test: This button executes a test.

  8. Input Sets: This button displays the Input Set view where you can store input data sets to reuse across all your tests. There are two types of input data sets you can use:

    • Global Parameters - variables that are available across all tests in the project. Reference these variables simply by calling it within the test using the convention “${VARIABLE}”.
    • Input Sets- group of input variables representing a scenario. The test will be executed once for each input set, overriding the variable values into your test.
    Input Set Code ViewInput Set Visual View
    Input Set Code ViewInput Set Visual View
  9. Unit View: This button toggles back and forth between the Input Set and Unit Test Composer view.

  10. Code and Visual View: This button toggles back and forth between the Visual and Code Test Composer view.

Additional Topics#