Difficulty: Beginner
Estimated Time: 15 minutes

In this scenario, you will smoothly deploy and configure a Continuous Integration toolchain to run the Xtesting samples. All the test results will be published in your own test result database and all the test artificats in your own s3 repository. A statuspage will quickly highlight the overall results.

More XtestingCI-based playbooks can be found at https://github.com/collivier/ansible-role-xtesting

Try Run CNTT Kubernetes Based Reference Conformance and Deploy the toolchain in your Kubernetes cluster, you will love them.

Many other public XtestingCI playbooks listed in README would be continously added in this series.

Stay tune!

Deploy your first Continuous Integration toolchain

Step 1 of 4

Xtesting and XtestingCI in a nutshell

Xtesting is a simple framework to assemble sparse test cases and to accelerate the adoption of automation best practices. It mainly allows the tester/developer to work only on the test suites without diving into Continuous Integration which would require additional skills. By managing all the interactions with the toolchain components, Xtesting guarantees a uniq and simple way to execute the test case, to publish all test results in a common test result database and to share all test reports in a common artifact repository.

XtestingCI leverages the common test case execution proposed by Xtesting. Thanks to a simple test case list, this tool deploys anywhere plug-and-play Continuous Integration toolchains in a few commands. It supports multiple opensource components such as Jenkins and Gitlab CI/CD and multiple deployment models such as all-in-one (in Docker or in Kubernetes), centralized services (e.g. OPNFV toolchain) or a mix of both.

During this scenario, you will deploy your own clone of the OPNFV toolchain which has been in-use every day to verify OpenStack and Kubernetes deployments for 5 years. But from a tester state point, switching from Jenkins to Gitlab CI/CD becomes as simple as writing 2 Boolean values in a text file via XtestingCI.