A CI/CD Workflow with FAST

If you integrate FAST into a CI/CD workflow, several extra steps will be added to the existing CI/CD workflow. These steps can be either part of an existing CI/CD job or part of a separate job.

The exact extra steps will differ depending on the test run creation scenario in action. Possible scenarios are:

  1. Deployment and configuration of the FAST node by the Wallarm API (such a workflow will be referred to as “Deployment via API” throughout this guide).

    The Wallarm API is employed to manage test runs.

    See this document for details on how FAST integration is made in this case.

  2. Deployment and configuration of the FAST node in CI mode (such a workflow will be referred to as “Deployment with CI mode” throughout this guide).

    The FAST node consequently switches between the recording and testing modes via manipulation of the CI_MODE environment variable.

    See this document for details on how FAST integration is made in this case.

A note on CI/CD workflow stages

The exact order of the aforementioned steps and the node's lifecycle depend on several factors, such as

  • The CI/CD tool and the CI/CD workflow in use.
  • The internal structure of the request source and the target application.

    It is crucial to maintain the selected order of these steps in alignment with the execution order for the parallel processes of recording, testing, and security testing.

results matching ""

    No results matching ""