Link Azure DevOps pull requests to work items without closing work too early
Require Azure Repos pull requests to link work items while keeping code merged, tested, deployed, and accepted as separate lifecycle states.
Read articleQaCockpit field notes
Ideas for turning test data into quality intelligence.
Practical thinking about TestOps, automation health, failure diagnosis, release evidence, and using better quality understanding to improve the business.
Test automationCI/CD & pipelinesRelease readinessQuality intelligenceRequirements & traceabilityQaCockpit product
Latest thinking
Operate quality with more context.
39 articles
No articles match these filters. Try a broader search or clear the filters.
Test design, automation, and execution coverage are different
Separate test design, automation, execution coverage, and pass rate in Azure DevOps so every percentage keeps a visible denominator and scope.
Read article
How to associate automated tests with Azure DevOps Test Cases
Associate pipeline test results with Azure DevOps Test Cases while preserving logical identity, framework constraints, and exact execution context.
Read article
Requirement-based test suites in Azure Test Plans: what they actually trace
Use requirement-based suites in Azure Test Plans without confusing planned test coverage, automation association, execution, and release evidence.
Read article
How to write acceptance criteria Azure DevOps can trace
Write stable, testable acceptance criteria in Azure DevOps and preserve their identity from requirement review through tests and execution evidence.
Read article
Faster Azure DevOps test feedback starts before the first test
Get reliable Azure DevOps test feedback sooner by reviewing access setup, preconditions, test scope, flaky-test handling, and the limits of parallel execution.
Read articleAzure DevOps traceability from work item to production
Build practical Azure DevOps traceability across work items, code, test pipelines, artifacts, deployments, and production feedback without imposing one process.
Read article
Azure DevOps pipeline health: why a ready deployment is still waiting
Trace Azure DevOps deployment delays across shared agents, test reruns, schedules, image builds, and dependencies before optimizing the wrong pipeline.
Read article
Why Azure DevOps cannot natively calculate acceptance-criteria coverage
Separate native Azure DevOps requirement traceability from acceptance-criteria coverage across test design, automation, execution, and results.
Read article
Azure DevOps test reporting: pipeline state, test results and JUnit evidence
Understand Azure DevOps pipeline state, published test results, retained JUnit files, diagnostic artifacts, and missing evidence without mixing their roles.
Read article
What should an Azure DevOps quality dashboard show?
Design an Azure DevOps quality dashboard around project health, Test Sources, evidence freshness, failures, release scope, and actionable drill-down.
Read article
How to organize regression testing across multiple Azure DevOps pipelines
Organize one Azure DevOps regression across UI, API, integration, and smoke-test pipelines while preserving scope, attempts, and missing evidence.
Read article
Release readiness in Azure DevOps: are you testing the version you plan to ship?
Review release readiness in Azure DevOps by tracing exact test runs to the intended application versions, environment, and retained evidence, with a worked example.
Read articleWhen an Azure DevOps pipeline succeeds but test evidence is missing
Troubleshoot a successful Azure DevOps pipeline with no usable test results by separating execution, publication, intake, and expected scope.
Read articleQaCockpit for Azure DevOps is now available on the Visual Studio Marketplace
Install QaCockpit for Azure DevOps from the Visual Studio Marketplace and start a 60-day organization evaluation without a card or automatic renewal.
Read articleHow to monitor automated test results across multiple Azure DevOps projects
Create an organization-level Azure DevOps quality view that preserves project health, source freshness, missing evidence, and actionable drill-down.
Read article
How to review test results across multiple Azure DevOps pipelines
Build one defensible Azure DevOps quality view across multiple pipelines without losing missing results, required scope, or exact execution traceability.
Read article
Release readiness report template: an evidence-based go/no-go review
Copy a practical release readiness report template, work through a filled example, and record exact test evidence, missing results, risks, owners, and a go/no-go decision.
Read article
Automated test reporting across teams and pipelines
Learn how automated test reporting can connect exact CI/CD runs, results, scope, failures, logs, and artifacts across teams without manual status collection.
Read article
Playwright JUnit reporting across CI/CD
Configure Playwright JUnit reporting, retain diagnostic artifacts on failed CI runs, and turn exact browser-test evidence into cross-team release context.
Read articleHow to know if your software is ready to ship
Use a practical release readiness checklist to collect cross-team pipeline, test, scope, and failure evidence before making a software go/no-go decision.
Read article
Share automated test reports without spreadsheets
Create audience-specific, versioned test reports from exact execution evidence, then deliver the same reviewed snapshot as PDF, email, or an expiring link.
Read article
A release readiness dashboard that shows its evidence
A trustworthy release readiness view exposes pipeline status, result intake, test outcomes, freshness, and the exact evidence behind every warning.
Read article
Can GitHub Projects replace a TestOps platform?
GitHub Projects and Actions can build powerful release boards. See where a finished TestOps product still saves custom automation and manual coordination.
Read article
When pass rate improves while failures increase
A regression pass rate can rise while failed tests increase and reported scope shrinks. Learn how to review the full campaign delta instead of one percentage.
Read article
Software quality is a competitive advantage—not a reporting task
How better quality understanding supports faster decisions, more focused engineering work, more predictable releases, and stronger customer trust.
Read article
How to Build a Cross-Project Quality View in Azure DevOps
Build a cross-project Azure DevOps quality view with native queries, dashboards, Analytics, or Power BI while preserving scope and source evidence.
Read article
Azure DevOps Dashboards vs QaCockpit: Same Data, Different Decisions
Compare Azure DevOps dashboards and QaCockpit using the same quality evidence, scope, and first-minute decision instead of counting widgets.
Read article
Azure DevOps Dashboards: Pros, Cons, and When They Stop Helping
Use Azure DevOps dashboards well, recognize when configuration loses decision context, and turn widgets into an explicit quality review path.
Read article
How much testing is enough? Use risk-based evidence for release decisions
Use risk-based testing, explicit release scope, and residual risk to decide when testing is sufficient without relying on one coverage target.
Read article
Requirements traceability matrix or live Azure DevOps links?
Choose when a requirements traceability matrix is useful and when live Azure DevOps links provide better evidence for daily delivery decisions.
Read article
Build a test catalog from CI results across repositories
Turn imported JUnit evidence into a persistent test catalog with source context, history, ownership, health signals, and linked failures.
Read article
From failed tests to a Failure Inbox
A Failure Inbox turns repeated failed test results into owned investigation work with transparent clustering, classification, context, and evidence.
Read article
Test scope drift: know when tests disappear from CI
A passing report can still be incomplete. Learn how exact test identities and versioned baselines expose added, removed, and repeatedly changed CI scope.
Read article
The hidden cost of fragmented test automation
Fragmented automation costs more than reporting time. It creates repeated diagnosis, missing evidence, unclear ownership, and slower quality decisions.
Read article
Measure time to diagnosis—not just pass rate
Pass rate describes test outcomes. Time to diagnosis reveals how efficiently a team turns failure evidence into owned, focused quality work.
Read article
Introducing QaCockpit: turn test automation into quality intelligence
Why we are building a TestOps layer that connects existing automation and turns distributed execution evidence into clearer quality decisions.
Read articleA green pipeline is not enough
A passed workflow can still hide missing tests, skipped scope, and weak evidence. Learn what a dependable regression signal needs to preserve.
Read article
Regression campaigns without replacing your CI/CD
How a lightweight campaign model coordinates existing CI/CD workflows while keeping execution, secrets, and test code in customer repositories.
Read articleApply the thinking