The Alactic library

Practical guides for customer operations

From a better WhatsApp conversation to a clearer team handoff. Find a specific decision, a useful checklist or a workflow your business can put into practice.

1,030 articles

Automation testing

Inject Failures at Action Boundaries to Find Partial Completion

A failed run may still leave an updated record, an open task, or an accepted notification. Use isolated boundary tests to identify what survived and decide what to retain, reverse, or reconcile before retrying.

10 min read
Automation testing

Test Human Review Gates for Rejection, Delay, and Changed Inputs

An approval test is incomplete if it only proves that “approve” works. Use a filled decision table to test rejection, silence, repeated decisions, and changes to the record before a consequential action.

9 min read
Automation testing

Verify That Stop Conditions Still Work After a Run Starts

A workflow that starts correctly can still act on outdated eligibility. Use this checkpoint checklist to test cancellation, exclusions, waits, retries, and the evidence that proves an action was suppressed.

9 min read
Automation testing

Test Simultaneous Triggers Against the Same Record

Use controlled overlap tests to uncover conflicting updates, duplicate tasks, and actions that survive cancellation—with a filled worksheet and clear acceptance rules.

9 min read
Automation testing

Test Event Sequences That Arrive in the Wrong Order

A passing event test does not prove a safe workflow. Use a filled sequence matrix to expose stale overwrites, accidental reopening, and actions that survive after their trigger state is superseded.

10 min read
Automation testing

Distinguish Duplicate Events from Legitimate Repeat Requests in Tests

Use paired tests to check that duplicate prevention blocks accidental replays without losing genuine new requests. Includes a filled comparison table and an independently reset test procedure.

9 min read
Automation testing

Check That Repeated Events Do Not Repeat Business Actions

A successful first run does not prove an automation handles repeats safely. Use this filled test script to check immediate repeats, delayed repeats, and recovery after a partially completed run.

10 min read
Automation testing

Test Time Boundaries Without Waiting Through the Whole Workflow

Test deadline crossings, date rollovers, time-zone differences, and late events with a controlled clock strategy—and record what each shortcut does and does not prove.

10 min read
Automation testing

Test Both Sides of Every Numeric Threshold

A rule can pass ordinary tests and still fail at its cutoff. Use a filled boundary worksheet to settle inclusive limits, decimal precision, rounding order, and units before rollout.

10 min read
Automation testing

Test Missing, Blank, and Unknown Values as Different Cases

A missing field, empty string, whitespace, and an explicit unknown can take different automation paths. Use a filled decision table to test the outcome, side effects, and authorisation boundary for each.

10 min read
Automation testing

Define Expected Results Before Running an Automation Test

A run is not successful just because something happened. Use a filled expected-results ledger to define permitted changes, forbidden side effects, evidence requirements, and verdicts before execution.

10 min read
Automation testing

Build Synthetic Records That Exercise Real Workflow Decisions

Realistic-looking records can miss the conditions that control an automation. Use this filled fictional test pack to build deliberate field combinations, known starting states, and traceable branch expectations without copying customer data.

10 min read
Automation testing

Choose Synthetic Test Cases by Business Consequence

Stop expanding the happy path while consequential failures remain untested. Use a filled risk-to-test worksheet to select a small, defensible test set based on harm, reversibility, and how easily a failure could go unnoticed.

10 min read
Automation design

Design a safe default path for cases no workflow branch covers

An unmatched case should not disappear or trigger a convenient catch-all action. Use an explicit fallback contract to preserve context, stop unauthorised actions, and route unresolved work to a named owner.

10 min read
Automation design

Write a workflow diagram in prose that two teams can interpret the same way

Turn a clear-looking flowchart into a shared operating specification with explicit authority, deadline rules, version control and terminal outcomes.

9 min read
Automation design

Decide what happens to active workflows when rules change

A revised workflow does not settle what happens to work already in progress. Use a continuation record to resolve wording, eligibility, sequence and deadlines without repeating completed actions.

9 min read
Automation design

Keep manual overrides from being immediately undone by automation

A manual change needs more than a new field value. Define what automation must leave alone, for how long, and under which release conditions—with a filled worksheet for three common override types.

10 min read
Automation design

Choose when to split a large workflow into smaller workflows

Split workflows around distinct decisions and independently verifiable outcomes. Use this filled worksheet and withdrawal trace to keep context, authority, and unfinished work clear.

9 min read
Automation design

Design the next step when only part of a workflow completes

Use a partial-completion decision table to preserve valid work, hold dependent steps, assign review, and authorise specific compensating actions without restarting everything.

9 min read
Automation design

Prevent competing workflows from making conflicting changes

When separate workflows can change the same business state, reasonable actions can collide. Use an authority map and a filled conflict matrix to decide which workflow waits, yields, stops, or requests review.

10 min read
Automation design

Decide when a completed record may enter the same workflow again

Separate genuine new work from incidental edits. Use a filled re-entry decision table to decide which completed, cancelled, expired, and manually stopped workflow instances may start a new cycle.

11 min read
Automation design

Resume a workflow after human review without using stale approval

Bind approval to a specific proposal, distinguish proposal revisions from internal edits, and route changed or expired cases back to the right check or decision.

9 min read
Automation design

Choose which workflow decisions require human review

Put human review before decisions that create meaningful commitments, resolve material uncertainty, or exceed delegated authority—not in front of every exception.

10 min read
Automation design

Define stop paths that cancel future work cleanly

A workflow is not stopped just because its main branch ends. Define what happens to queued actions, timers, reviews, and completed work, then record the outcome with a filled stop-path checklist.

10 min read

Turn a guide into a working customer journey.

Explore the tools and services behind the operating process.

Explore Communications