Field notes for quality leaders
Release intelligence, packaged apps, architecture, agentic AI and the pitfalls that slow every test cycle. Filter by topic or search.
End-to-end handoffs: the accrual that never clears
Every module passed its tests, yet the receipt accrual never cleared. Why handoffs between modules and systems go untested, and how chain tests catch them.
Quality has a tool-sprawl problem
Enterprises buy functional, performance, security, test data and other quality tools separately, each with its own model of the same app. The case for one.
Coding agents in the pipeline: tests under policy
Coding agents now run tests to finish their own work. How to give them identity, scope, environment limits and an audit trail without bypassing the gate.
Earned autonomy
How much should AI be allowed to change your tests? A six-level autonomy ladder, why trust has to be earned per scope, and the rules that never relax.
Salesforce release certification for customized orgs
Three releases a year meet years of Flows, Apex, packages and permissions. How to certify each Salesforce release in sandbox preview in a customized org.
The desktop gap in enterprise testing
Packaged apps and custom Windows clients run critical work, yet desktop tooling is thinning out. What the 2027 deadlines mean and how to plan.
Regression suites that only grow
Suites grow because adding feels safe and deleting feels risky. Why tag filters do not fix it, and how to select tests as a plan with a purpose and a budget.
Deterministic execution, AI only at authoring
Where AI sits in a test architecture decides whether results can be reproduced and audited. A design that uses AI to author and a compiled plan to run.
Coding agents need a test gate
Coding agents can now run, edit and heal tests through MCP. Why the test suite needs a policy gate, and why an agent must never approve its own heal.
Cohorts, preview windows and the certification squeeze
Vendor preview windows look generous until they overlap with each other and with close. How to plan certification by cohort and move work out of the squeeze.
SAP S/4HANA upgrade testing pitfalls
Custom code that compiles but behaves differently, Fiori apps replaced by successors, interfaces tested only on stubs: the S/4HANA upgrade pitfalls we see.
Plain English needs a grammar
Natural-language tests drift into ungoverned prose without a schema. Twelve verbs, quoted targets and a parser keep them readable and exact.
Test data bottlenecks in shared environments
Shared test environments turn data into the slowest part of testing. Six provisioning strategies, when each fits, and how to stop tests colliding.
Human approval gates for AI-generated heals
AI can propose test heals quickly. Deciding which heals need which reviewer, what a proposal must show and how to keep the queue moving is the real design.
One app model beats eight tool repositories
Each quality tool keeps its own description of your app, and they drift apart. Why a single shared model makes change, impact and evidence tractable.
The runtime AI tax
Runtime-AI test tools call a model on every step of every run. How that cost compounds, what it hides, and where AI pays for itself.
Workday R1 and R2 regression without the weekend
Workday feature releases come with a preview window that many teams use too late. How to plan R1 and R2 regression so it ends on a weekday.
Delivered-enabled features nobody opted into
Opt-in features get a decision. Delivered enabled changes reach every user on update day with no owner. How to find them, test them and own them.
Flaky tests: classify failures by cause
Flaky is a symptom, not a diagnosis. How to classify every failed check by cause, from data and environment to timing and vendor change, using evidence.
What agentic test automation should and should not do
Agents are good at drafting, exploring and triaging. They should not decide what a test means at run time or approve their own work. Where to draw the line.
Reference architecture: release-aware QE
The parts of a release-aware quality practice: release intake, one app model, rule-based impact, deterministic engines, a signed quality view and CI hooks.
Oracle Fusion quarterly update readiness checklist
A practical checklist for each Oracle Fusion quarterly update, from reading What's New to signing off production, with the evidence to keep at each stage.
Where requirements-to-test traceability breaks
A linked test is not a covered requirement. The five traceability gaps that hide in most matrices.
Reading a vendor release note like a tester
Vendor release notes are written for admins and buyers. How a tester reads them: arrival type, behavior verbs, configuration touchpoints and the gaps.
No articles on this page match. Try another word or category.