-
Signed-off-by:
Jason Krause <jason.krause@darkwolf.co>
Signed-off-by:
Jason Krause <jason.krause@darkwolf.co>
Testing
There are multiple phases of testing for an application to get into a customer environment
Types of Changes
- New Iron Bank Image
- Changes to Manifests for deployments
- Helm Chart Tests to verify operation within the cluster
- Newly supported configurations of application
Testing Platform
Big Bang Applications will leverage GitLab Runners to execute these common BigBang Pipelines. Each Big Bang application is required to use the Big Bang Pipelines, whose functionality is outlined here.
A detailed description of the pipelines and how to execute the testing process on a local system is described in the README.md in https://repo1.dso.mil/platform-one/big-bang/pipeline-templates/pipeline-templates.
Application Testing
When a Big Bang application developer submits changes to a particular Big Bang application, the application needs to be tested to ensure functionality, as well as compliance with core Application Requirements.
A core feature of all testing capabilities is its ability to be run locally by developers using their own environment, or by other teams looking to test proposed changes to the application (e.g. IronBank as part of container creation). The GitLab pipelines will be simple wrappers around these common testing and deployment tools.