QDO-2.2.6 K3 Apply
Apply quality assurance and testing knowledge to implement a CI/CD pipeline
Implementing a CI/CD pipeline should follow an incremental approach with the following steps as defined by (Humble; Farley, 2010).
1. Model the value stream from commit to release and create a walking skeleton
The value stream mapping (VSM) technique maps the part of the value stream from code check-in to release (see ( ISTQB® CT-ATLaS , v2.0) for details on VSM). Then the mapped steps are implemented without detailed content in the CI/CD pipeline. When the predefined quality gates are met, this triggers the next step of the mapped process, and the output of a step becomes an input for others (e.g., build artifacts and test databases).
The CI/CD pipeline code is usually stored in the same repository as the application’s source code. However, with more complex projects, workflows can be reused throughout repositories.
A walking skeleton shows the flow and connects the steps before adding details.
2. Automate build and deployment process
The CI toolset should trigger a build on every check-in. The build process takes source code as its input and produces programs as outputs. After the build the output is automatically deployed to a test environment and tests are executed.
Provisioning of an environment and test data should be fully automated and reproducible. IaC, virtualization and containerization technology support this step (see Section 4.2.3 and Section 4.2.9 respectively). Operations roles are usually involved in developing this automation (see Section 1.2.1 and Section 1.2.2 ). Test environments are deployed the same way as production environments.
3. Automate commit stage
The next step is implementing a full commit stage (see Section 2.2.2 ), running static analysis and unit tests, and including a selection of component tests, integration tests and system tests on every commit. In this stage, vulnerability scanning and dependency scanning implement security practices. It is common to implement a quality gate to check if the build needs to be stopped if agreed upon thresholds are not met (e.g., not enough code coverage or test execution time is too long). Once the commit stage gets too long (e.g., over five minutes), it makes sense to split it into parallel jobs.
4. Automate acceptance stage
Implementing the acceptance stage (see Section 2.2.2 ) should start with automating a few test cases from all different test types in the CI/CD pipeline and growing the test suites incrementally, instead of trying to automate the majority of the test cases of one test type before moving on to the next one.
Tests run sequentially or in parallel, each in their own environment to optimize feedback. However, consider resource availability, cost, and sustainability goals.
5. Automate the release
Automating this process requires understanding the way the release decision is made during the release process (see Section 4.2.2 ), and it requires collecting information to make this decision, whether it is automated or manual. Feature management tools can support decision makers to manage their decisions (e.g., updating feature toggles in code) (see Section 4.2.4 ). Automating incrementally applies to these release activities, too.
The implemented process should follow the agreed deployment and release strategy, support fast rollback, and provide an audit trail on all activities for compliance.
6. Evolving the CI/CD pipeline
Implement the CI/CD pipeline incrementally. As the project gets more complex, the value stream will evolve. Measure the efficiency of the CI/CD pipeline using agreed upon metrics (e.g., lead time of any given activity). Continuously evolve and improve the CI/CD pipeline in line with lean principles and systems thinking (e.g., splitting long test executions into parallel jobs, or removing non-value added jobs). See ( ISTQB® CT-ATLaS , v2.0) and ( ISTQB® CTAL-TM , v3.0) for continuous improvement practices.
The learning objectives explained by the sections found for this search, in the same order.
Apply quality assurance and testing knowledge to implement a CI/CD pipeline
None of the sections found for this search explains a learning objective.
No learning objectives match the current filters.
Business outcomes whose code or wording matches your search, with the learning objectives linked to each.
No business outcome matches this search.
No business outcomes match the current filters.
Keywords that the syllabi list at the start of a chapter — ISTQB Glossary keywords and domain-specific keywords — matching your search. Definitions are the ISTQB Glossary's.
No chapter keyword matches this search.
No keywords match the current filters.
Questions from the published sample exams that match your search — in the question, its answer options, or the objective or keyword it tests.
You are reviewing a CI/CD pipeline where the build, test, and deployment processes are automated. When the build and test pipeline ends, deployment is triggered. Developers are reporting frequent failures in the test environment due to missing configurations…
No sample exam question matches this search.
No exam questions match the current filters.