CAMP — Amplify your Configuration Tests
Give us feedback! Please take 5’ of your time to fill in this quick questionnaire.
This is important for us. As a recognition for your feedback, you will receive a limited edition “STAMP Software Test Pilot” gift and be recognized as a STAMP contributor.
This campaign will close on November 30, 2019. You will be contacted individually for a customized gift and for contribution opportunities.
CAMP (Configuration AMPlification) takes as input a sample testing configuration and generates automatically a number of diverse configurations. The generation is guided by predefined features and constraints, and utilizes a set of reusable pieces. The current version of CAMP is focused on the Docker environment, and the input and output configurations are specified as Dockerfiles or docker-compose files.
If you try CAMP, feel free to:
-
Checkout the online documentation;
-
Ask questions on our mailing list;
-
Post issues or feature requests on the issue tracker.
Running CAMP on your project
To set CAMP on your project. There are two prerequisites:
-
Your project should be dockerised.
-
New configuration of the project can be achieved by:
- By substituting the FROM statement of a Dockerimage file
- By substituting an image of a docker-compose file
- Or by doing substitution in any file you
ADDin your Dockerfile
Further, we need to identify variation points of your configuration, e.g., java versions. We fill out feature.yml with this information. We also need to define building rules which are used to build new docker files. This information is filled in images.yml file. This allows generating various docker files which are various possible configuration of your application. If we need to generate various docker-compose file, we need to fill in compose.yml. However, this is optional.