Real-World Test Design Workshop

Q: What is real-world test design workshop?

Real-World Test Design Workshop is a key concept in Test Design Techniques. This lesson teaches you to apply multiple test design techniques to realistic software features from scratch, providing practical skills you can apply immediately in your testing work.

Q: How do I apply real-world test design workshop in real projects?

Start by practicing the core techniques covered in this lesson. Specifically, you should make technique selection decisions under time and information constraints. Apply these skills in your current project to see immediate results.

Q: Why is real-world test design workshop important for QA engineers?

Real-World Test Design Workshop is a core skill that employers look for in QA professionals. It directly impacts test coverage, defect detection, and team efficiency. Mastering it strengthens your Test Design Techniques capabilities and makes you more effective at delivering quality software.

Q: What should I know before learning real-world test design workshop?

You should have a basic understanding of software testing fundamentals. Familiarity with test design workshop will help, but the lesson includes review sections for key prerequisites.

Q: How does real-world test design workshop help my QA career?

Knowledge of real-world test design workshop is frequently listed in QA job descriptions and interview questions. It demonstrates expertise in test design workshop, practical test design and shows you can contribute to quality assurance at a professional level. Senior roles especially value this competency.

Yuri Kan

Real-World Test Design Workshop

Put all your test design skills into practice with realistic workshop exercises. Design complete test suites for real-world features using the full range

Quick Answer

Real-World Test Design Workshop covers essential QA skills — after this lesson you can apply multiple test design techniques to realistic software features from scratch.

— Yuri Kan, Senior QA Lead

What You Will Learn

Apply multiple test design techniques to realistic software features from scratch
Make technique selection decisions under time and information constraints
Produce a professional test design document covering technique rationale, test cases, and coverage analysis

Table of Contents

Workshop Introduction

This lesson is a hands-on workshop. You will apply everything you have learned across Module 3 to design test suites for realistic features. Each exercise simulates a real-world scenario where you must:

Analyze the feature requirements
Select appropriate test design techniques
Derive test cases systematically
Document your rationale and coverage

There are no new concepts in this lesson — only practice. Treat each exercise as if you were designing tests for a real project.

Feature Description:

A ride-sharing app calculates fares using these rules:

Base fare: $2.50 Per mile: $1.75 (standard), $2.50 (premium), $3.25 (luxury) Per minute: $0.35 (standard), $0.50 (premium), $0.65 (luxury) Minimum fare: $7.00 (standard), $12.00 (premium), $18.00 (luxury)

Surge pricing:

Demand multiplier from 1.0x to 3.0x
Applied to per-mile and per-minute rates only (not base fare)
Surge does not apply to scheduled rides booked 2+ hours in advance

Discounts:

First ride: 50% off (max $10 discount)
Promo code: fixed dollar amount off final fare
Loyalty discount: 10% off for riders with 50+ rides in past 30 days
Only one discount applies (highest value wins)

Tolls and fees:

Airport fee: $5.00
Bridge/tunnel tolls: passed through at cost
Booking fee: $2.00 (waived for loyalty riders)

Constraints:

Fare cannot be negative (minimum $0)
Maximum fare cap: $500 per ride
Canceled rides: $5 fee if driver already dispatched

Design a comprehensive test suite. Document your technique selection and derive test cases.

Guided Solution Outline

Technique selection:

EP: Vehicle types (standard, premium, luxury, invalid), discount types, surge levels
BVA: Surge boundaries (1.0, 3.0), loyalty threshold (49/50 rides), advance booking (1h59m/2h), minimum fare edges, max fare cap ($500), first-ride discount cap ($10)
Decision tables: Discount priority rules (first ride vs. promo vs. loyalty)
Domain analysis: Distance x time x surge interaction
State transitions: Ride lifecycle (requested → matched → in-progress → completed → rated; or requested → matched → canceled)

Key test cases (abbreviated):

#	Category	Technique	Test
1	Base calc	EP	Standard ride, 5 miles, 15 min, no surge → $2.50 + 51.75 + 150.35 = $16.50
2	Minimum	BVA	Very short standard ride → should be at least $7.00
3	Surge boundary	BVA	Surge at 1.0x (no change), 1.01x (minimal change), 3.0x (max), 3.01x (should cap at 3.0x)
4	Advance booking	BVA	Scheduled 1h59m ahead (surge applies) vs. 2h00m (surge waived)
5	Discount priority	Decision table	First ride + promo + loyalty all qualify → highest value wins
6	First ride cap	BVA	Ride costs $25, first ride = 50% = $12.50 → capped at $10 discount = $15
7	Fare cap	BVA	Luxury, long distance, max surge → should cap at $500
8	Negative fare	BVA	Large promo code on cheap ride → minimum $0
9	Airport	EP	Pickup from airport (+$5) vs. regular location
10	Cancellation	State transition	Cancel after driver dispatched → $5 fee

Workshop Exercise 2: Healthcare Appointment System

Feature Description:

A healthcare portal allows patients to schedule appointments:

Scheduling rules:

Appointments available Monday-Friday, 8:00-17:00, in 30-minute slots
Same-day appointments only if booked before 14:00
Patients can book up to 3 months in advance
Maximum 2 active appointments per patient
Follow-up appointments must be 7-90 days after the original visit

Doctor availability:

Each doctor has a weekly schedule with available/blocked slots
Emergency slots: 2 per day reserved for urgent cases
Buffer time: 15 minutes between appointments (automatic)

Notifications:

Confirmation email immediately after booking
Reminder 24 hours before
Cancellation must be 4+ hours before appointment time

Patient types:

New patient: first visit requires 60-minute slot (double slot)
Returning patient: 30-minute slot
Urgent: can use emergency slots, no advance notice required

Design a complete test suite.

Guided Solution Outline

Techniques:

State transitions: Appointment lifecycle (available → booked → confirmed → completed/cancelled/no-show)
BVA: Time boundaries (8:00, 17:00, 14:00 cutoff), date boundaries (today, 3 months), follow-up (7/90 days), cancellation (4 hours)
EP: Patient types (new/returning/urgent), slot types (regular/emergency)
Decision tables: Booking eligibility (patient type x time x active appointments x day of week)
Combinatorial: Doctor x day x time x patient type x urgency

Key boundary tests:

Book at 13:59 for same-day vs. 14:00 (rejected)
Book exactly 3 months ahead vs. 3 months + 1 day
Follow-up at day 6 (too early) vs. day 7 vs. day 90 vs. day 91 (too late)
Cancel at 3h59m before (too late) vs. 4h00m before (OK)
Third appointment when already 2 active (rejected)

Workshop Exercise 3: Content Moderation Pipeline

Feature Description:

A social media platform processes user-generated content through a moderation pipeline:

Content types: Text posts, images, videos, comments, profile bios

Automated checks (in order):

Spam detection (AI model, confidence 0-100%)
Profanity filter (dictionary + ML, severity: mild/moderate/severe)
Image/video classification (nudity, violence, hate symbols)
Personal information detection (phone numbers, addresses, SSNs)
Copyright check (for images/videos only)

Decision rules:

Confidence >= 95%: auto-reject
Confidence 70-94%: flag for human review
Confidence < 70%: auto-approve
Severe profanity: always reject regardless of confidence
Personal information detected: always flag for review
Appeals: rejected content can be appealed once

Priority queue for human review:

High: content from verified accounts or content with high engagement
Medium: standard content
Low: content from new accounts (< 7 days old)

Design test cases focusing on the decision logic and edge cases.

Guided Solution

Techniques:

Decision tables: Confidence level x profanity severity x content type → action
State transitions: Content lifecycle (submitted → check1 → check2 → … → approved/rejected/review → appealed → final)
BVA: Confidence thresholds (69/70, 94/95), account age (6/7 days)
EP: Content types, check categories, priority levels
Combinatorial: Content type x check result x account type

Decision table for core logic:

Confidence	Profanity	PII Detected	Action
>= 95	Any	Any	Auto-reject
70-94	Not severe	No	Human review
70-94	Not severe	Yes	Human review (flagged PII)
70-94	Severe	Any	Auto-reject (severity override)
< 70	None/mild	No	Auto-approve
< 70	None/mild	Yes	Human review (PII override)
< 70	Moderate	No	Auto-approve
< 70	Severe	Any	Auto-reject (severity override)

Boundary tests:

Confidence exactly 70: review (not approve)
Confidence exactly 95: reject (not review)
Confidence 69.9: approve
Confidence 94.9: review
Account age exactly 7 days: medium priority (not low)
Appeal after rejection: allowed once
Second appeal: rejected

State transition tests:

Content passes all 5 checks → approved
Content fails at check 1 (spam) → appropriate action, checks 2-5 skipped?
Rejected → appealed → human reviews → overturned to approved
Rejected → appealed → upheld → no further appeal allowed

Producing a Professional Test Design Document

For each workshop exercise, your test design document should include:

1. Feature Analysis

Summary of the feature and its key behaviors
Identified ambiguities or assumptions

2. Technique Selection Rationale

Which techniques you chose and why
What each technique is targeting

3. Test Case Table

ID	Technique	Category	Input	Expected Result	Priority
TC-001	BVA	Surge boundary	surge=3.0x	Applied at max	High
TC-002	BVA	Surge boundary	surge=3.01x	Capped at 3.0x	High

4. Coverage Analysis

Requirements covered / total requirements
Structural coverage estimate
Identified gaps and risks

5. Risks and Assumptions

What could go wrong that is not covered
Assumptions made when requirements were unclear

Key Takeaways

Real-world test design requires combining multiple techniques for a single feature
Always start by analyzing the feature and selecting techniques before writing test cases
Document your technique selection rationale — it helps reviewers and future maintainers
Ambiguous requirements are common — document assumptions and test both interpretations when possible
Workshop practice is the fastest way to build test design intuition
A professional test design document communicates not just WHAT you tested but WHY you chose that approach

Knowledge Check

1. When facing a feature with both complex business rules and stateful behavior, what is the recommended approach?

2. A test design document should include which of the following?

3. During a workshop exercise, you realize the requirements are ambiguous. What should you do?

Frequently Asked Questions

What is real-world test design workshop?

Real-World Test Design Workshop is a key concept in Test Design Techniques. This lesson teaches you to apply multiple test design techniques to realistic software features from scratch, providing practical skills you can apply immediately in your testing work.

How do I apply real-world test design workshop in real projects?

Start by practicing the core techniques covered in this lesson. Specifically, you should make technique selection decisions under time and information constraints. Apply these skills in your current project to see immediate results.

Why is real-world test design workshop important for QA engineers?

Real-World Test Design Workshop is a core skill that employers look for in QA professionals. It directly impacts test coverage, defect detection, and team efficiency. Mastering it strengthens your Test Design Techniques capabilities and makes you more effective at delivering quality software.

What should I know before learning real-world test design workshop?

You should have a basic understanding of software testing fundamentals. Familiarity with test design workshop will help, but the lesson includes review sections for key prerequisites.

How does real-world test design workshop help my QA career?

Knowledge of real-world test design workshop is frequently listed in QA job descriptions and interview questions. It demonstrates expertise in test design workshop, practical test design and shows you can contribute to quality assurance at a professional level. Senior roles especially value this competency.

Real-World Test Design Workshop

What You Will Learn

Workshop Introduction #

Workshop Exercise 1: Ride-Sharing Pricing Engine #

Workshop Exercise 2: Healthcare Appointment System #

Workshop Exercise 3: Content Moderation Pipeline #

Producing a Professional Test Design Document #

1. Feature Analysis #

2. Technique Selection Rationale #

3. Test Case Table #

4. Coverage Analysis #

5. Risks and Assumptions #

Key Takeaways #

Knowledge Check

Frequently Asked Questions

Workshop Introduction

Workshop Exercise 1: Ride-Sharing Pricing Engine

Workshop Exercise 2: Healthcare Appointment System

Workshop Exercise 3: Content Moderation Pipeline

Producing a Professional Test Design Document

1. Feature Analysis

2. Technique Selection Rationale

3. Test Case Table

4. Coverage Analysis

5. Risks and Assumptions

Key Takeaways