6.4Working with DevOps

CI/CD Pipeline Collaboration

QA and DevOps share a common goal: fast, reliable, automated feedback. The CI/CD pipeline is the shared infrastructure that makes this possible.

Where QA and DevOps Collaborate

Area	QA Responsibility	DevOps Responsibility	Shared
Test execution in CI	Write and maintain tests	Configure pipeline stages and runners	Test stage configuration
Test environments	Define what environments are needed	Provision and maintain environments	Environment health monitoring
Test data	Define data requirements	Automate data provisioning	Data refresh scripts
Artifacts and reports	Generate test reports and screenshots	Store and serve artifacts	Report integration with dashboards
Pipeline optimization	Identify slow or flaky tests	Optimize runner allocation and caching	Execution time targets

Common QA-DevOps Friction Points

Problem: "The pipeline is too slow because of QA tests." Solution: Work together to parallelize tests, optimize test data setup, and implement smart test selection (run only tests affected by the change).

Problem: "The test environment is always broken." Solution: Treat test environments as infrastructure-as-code. Version them, automate their provisioning, and add health checks that alert before QA discovers the environment is down.

Problem: "QA needs a new tool installed in CI." Solution: Propose it with context: "We need Playwright installed in the CI image. Here is the Dockerfile change. It adds 200MB to the image but saves 15 minutes per run because we won't need to install it dynamically."