CI/CD pipeline guides — integrate automated testing into your deployment pipeline and ship with confidence.
CI/CD
Mypy is Python's most widely used static type checker. It catches type errors before runtime — wrong argument types, missing attributes, incorrect return types — the kind of bugs that slipped through Python's dynamic typing for decades. Integrating Mypy into CI transforms it from a developer convenience into
LLM Testing
The hardest thing about deploying LLM-powered features isn't building them — it's knowing whether they're getting better or worse. Prompt tweaks, model upgrades, retrieval changes: each one can improve performance on some inputs while degrading it on others. Braintrust gives you the infrastructure to
Deployment
Blue-green deployment reduces downtime risk by running two identical production environments — blue (live) and green (new). The switch happens at the router level, and rollback is instant: flip traffic back to blue. The testing challenge is making the cutover decision confidently: is green actually ready? The Blue-Green Testing
Security
OWASP ZAP is the benchmark for open-source web application security scanning. Most teams use it for baseline scans — but ZAP's real power is in its API, authenticated scanning, and deep CI/CD integration. This guide covers the complete picture. Active vs Passive Scanning Understanding the difference determines
Security
Nuclei is a fast, template-based vulnerability scanner from ProjectDiscovery. Unlike ZAP or Burp, Nuclei runs predefined YAML templates — thousands of them for CVEs, misconfigurations, exposed panels, and default credentials. The template model makes it easy to write custom checks for your application's specific security requirements. Why Nuclei
Security Testing
Dependency vulnerability scanning is table stakes for modern CI pipelines. A new critical CVE can drop at any moment, and without automated scanning, your pipeline will happily ship code with known exploitable vulnerabilities. Three tools dominate this space: Grype, Trivy, and OSV-Scanner. Each has different strengths, and the right
Test Reporting
JUnit XML is the lingua franca of test reporting. Originally a JUnit (Java) format, it's been adopted by every major test framework across every language. GitHub Actions, GitLab CI, Jenkins, CircleCI, and most other CI platforms can parse and display JUnit XML natively. Understanding how to generate and
Game Development
Godot 4 runs headlessly with --headless — no display required in CI. Combined with GUT's CLI runner, you can run your full test suite in GitHub Actions on every push. This guide covers setting up the CI pipeline, caching the Godot binary, running GUT tests, and reporting results. Key
Testing
OAuth2 integrations are painful to test in CI because the authorization code flow requires a browser and human interaction. This guide covers how to test OAuth2 without browser automation: mocking the token exchange, testing the callback handler, validating token storage, testing refresh flows, and running full browser-based auth tests
Testing
AI agent pipelines need CI/CD just like any software — but standard pipelines don't account for LLM non-determinism, evaluation costs, or model-level regressions. This guide covers building CI/CD pipelines specifically for AI agent systems: fast deterministic checks, LLM evaluation gates, model upgrade workflows, safety guardrails,
Test Reporting
Running tests is table stakes. Understanding what the results mean over time — that's where teams actually improve their quality practice. Test trend analysis is the discipline of reading patterns from test result history: which tests are reliable, which are lying to you, which parts of the codebase have
Test Reporting
A test report that no one reads is noise. A test failure that doesn't create a Jira ticket gets forgotten. A CI build that breaks but doesn't alert anyone in Slack lets bugs sit for days. Integrating test reports into the tools your team already uses