Skip to content
academia.sh
tr
Log in

Course Intermediate

The Testing Process and Automation Infrastructure

By the end of this course

Start course

01

Planning

Deciding where limited time goes: writing down scope, entry and exit criteria, and responsibility, prioritizing by the order that risk's product of likelihood and impact produces, structured free-form testing finding defects the scripted test cannot see, turning the definition of done into acceptance criteria, and user acceptance testing's scope and feedback management.

  1. 01 Test Plan Dividing a limited release budget among the test suite written across four courses: listing the inventory together with its cost quantities, tying entry and exit criteria to a number, letting responsibility determine how many tests actually run, and comparing four plans on the same defect set by escaped defect and feedback time.
  2. 02 Risk-Based Prioritization Distributing the same budget across five different orders: class risk derived from the product of likelihood and impact, the density order that emerges from dividing risk by minutes, comparison against random, cheapest-first, and most-components-first orders, the estimate error's sensitivity, and the order's twenty-release return.
  3. 03 Exploratory Testing Turning testing whose script is not written in advance into a budget item: dividing the session's charter between width and depth, the defect class the scripted set cannot see becoming visible only through depth, the rate at which a found defect converts into a script, and measuring escaped defect and net cost across a twenty-release horizon.
  4. 04 Acceptance Criteria Writing the definition of done as a data structure: the acceptance criterion's subject, measure, and limit slots, the reopened-work count and discovery phase that change with who fills a slot and when, the product side's attention being a limited budget, and a criterion written at closeout only confirming observed behavior.
  5. 05 User Acceptance Testing Managing end-user verification as a distribution decision: splitting acceptance scope four ways across user tasks, separating the returning feedback into defect, request, and misunderstanding, each class's cost measured in minutes, and why feedback volume is not a quality measure.

02

Automation Infrastructure

Placing tests into a pipeline and turning a result into a decision: the trade-off staged test gates strike between feedback time and escaped defects, the cost of environment variety, secrets and data safety in the test environment, making results readable for the team, interpreting escaped defects together with rework and cycle time metrics, and tracing recurring defects to their source.

  1. 01 Testing in Continuous Integration Placing the tests left behind by four courses into a pipeline: the trade-off staging and gating strikes between feedback time and escaped defects, fail fast's effect on the run budget, the wait cost of nightly and release gates, and tying quarantine to the gate decision.
  2. 02 Management of Test Environments Adding the environment dimension to the previous lesson's gate arrangement: the visibility limit an environment tier gives a team, a shared environment's queue time, a reserved environment's idle cost, and the escaped defects eight environment arrangements produce on the same defect set.
  3. 03 Secrets and Data Management The distribution of secrets entering the test environment: leak points measured in run artifacts, least privilege's effect on exposure surface, the manual step count a time-limited privilege leaves behind, and the escaped defects seven authorization arrangements produce on the same defect set.
  4. 04 Reporting Making a run's result readable for the team: measuring the same nightly run across four reporting arrangements in lines read, steps opened, and noise items, comparing time-to-decision against the attention budget, an unresolved root turning into an escaped defect, and scanning the flaky section's culling threshold together with its source.
  5. 05 Quality Metrics Computing escaped defects, rework, and cycle time from the same event set: measuring a single pipeline-cheapening decision across two periods, scanning six metrics' thresholds together with their sources, counting which metric changes a decision, and the attention cost of a metric that changes none.
  6. 06 Root Cause Analysis Tracing a recurring defect class to its source: building the causal chain as a data structure, comparing the intervention that fixes the symptom with the one that fixes the cause on the same defect set, coverage growing while applicability drops with depth in the chain, and the review threshold's source.

Start typing to search.

↑↓ ↵ Esc navigate · open · close