DO400 – Red Hat DevOps Pipelines and Processes: CI/CD with Jenkins, Git, and Test Driven Development — Lesson 2: Automated Testing, Unit and Integration Tests, TDD, and Quality Feedback

Learning Objectives

• Configure the principal services, objects, workflows, and controls for test strategy, unit testing, and integration testing.
• Apply test-driven development and quality feedback while preserving reviewable technical evidence.
• Recognize and correct the condition where a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect.

Detailed Topics

• test strategy: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• unit testing: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• integration testing: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• test-driven development: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• quality feedback: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.

Instructor Demonstration

The instructor demonstrates automated testing, unit and integration tests, tdd, and quality feedback by tracing architecture, commands, configuration, system messages, and evidence. The walkthrough tests how a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect and explains how to isolate the cause without masking related issues.

Hands-On Exercise

Implement the core workflow for Automated Testing, Unit and Integration Tests, TDD, and Quality Feedback and add the verified result to the Git-based application repository, automated test suite, Jenkins pipeline, deployment evidence, and support guide.

1. Confirm scope, versions, access, dependencies, assumptions, and acceptance criteria.
2. Perform the workflow while recording commands, configuration, output, events, and decisions.
3. Test the normal path and one course-specific exception or boundary condition.
4. Retest the correction and document rollback, ownership, and follow-up actions.

Scenario Analysis

• Identify which dependency most strongly influences test strategy in the stated scenario.
• Compare two approaches for test-driven development and explain the security, reliability, performance, and support trade-offs.
• Decide what evidence must be retained in the Git-based application repository, automated test suite, Jenkins pipeline, deployment evidence, and support guide before operational acceptance.

Troubleshooting Guidance

Begin with the first observable difference from the expected result. Check configuration, permissions, sequence, connectivity, and functional behavior separately, then correlate logs, events, commands, metrics, and configuration history. Treat the assumption that a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect as a hypothesis until a reproducible retest confirms the cause.

Validation Checklist

• The required configuration, permissions, sequence, connectivity, and functional behavior were checked and recorded.
• The normal path and a course-specific exception were tested.
• The Git-based application repository, automated test suite, Jenkins pipeline, deployment evidence, and support guide links conclusions to commands, configuration, logs, metrics, or other objective evidence.
• Corrective actions, rollback, ownership, and handover notes are complete.

Lesson Outcome

Learners can apply Automated Testing, Unit and Integration Tests, TDD, and Quality Feedback, explain the observed platform behavior, and support the result with a reviewable Git-based application repository, automated test suite, Jenkins pipeline, deployment evidence, and support guide.