Functional Testing: Ensuring Correctness, Completeness, and Suitability

1. Correctness

Definition: Verify that the software implements every requirement specification accurately; output results, state changes, and data calculations must fully match the expected behavior.

Test focus: Input/output validation (valid inputs must produce exact expected outputs), business‑logic verification (process flows, state transitions, decision branches), calculation accuracy (algorithms, formulas, financial calculations). Common test methods include equivalence class partitioning, boundary‑value analysis, and decision‑table testing.

2. Completeness

Definition: Assess whether the functional scope covers all explicit and implicit requirements in the specification, ensuring “nothing is missing.”

Test focus: Functional‑point coverage (match each requirement item with test cases), scenario completeness (all key user scenarios and end‑to‑end flows are supported), uncovered requirements (including performance or security impacts on functionality). Techniques such as requirement‑traceability matrices, functional decomposition diagrams, and scenario‑based testing are used.

3. Suitability

Definition: Evaluate whether the implemented functions are appropriate for users, helping them accomplish their tasks; it examines practicality, reasonableness, and alignment with user goals.

Test focus: Functional value (does the feature solve a real user problem?), interaction rationality (does the workflow match user habits and mental models?), redundancy or missing steps (are there unnecessary features or missing essential steps?). Methods include user reviews, usability testing, and expert walkthroughs.

Relationship diagram : Correctness → precise technical implementation; Completeness → full requirement coverage; Suitability → fulfillment of user goals. A high‑quality feature must satisfy all three.

Case Study: E‑commerce “User Coupon” Feature

Specification (simplified): Users can view coupons in “My Account,” select applicable coupons at checkout, and coupons have conditions such as minimum spend, applicable product categories, and expiration dates. Only one coupon may be used per order.

Testing Correctness

TC1: User has a “Spend 100, get 20 off” coupon, cart total 120 ¥ → coupon selectable, final payment 100 ¥.

TC2: Cart total 90 ¥ → coupon not selectable.

TC3: Coupon expired → coupon unavailable regardless of cart total.

TC4: User holds a category‑specific coupon (electronics) and a general coupon; adds a book (non‑electronics) to cart → category coupon not selectable, general coupon selectable.

Analysis: These cases precisely verify business rules (discount calculation, expiration, category limits) are executed correctly by the system.

Testing Completeness

Requirement checklist review reveals hidden or ambiguous items:

Requirement 1: Support viewing coupons by status (unused, used, expired) – an implicit need.

Requirement 3: Whether special‑price items are excluded or first‑time‑purchase only – a potential omission that must be confirmed with business owners.

Requirement 4: Enforce “no stacking” rule – explicitly stated.

Scenario completeness checks include multi‑device login synchronization of coupon status and automatic coupon return when an order is cancelled. Analysis shows that uncovering such gaps leads to additional test cases, guaranteeing full functional coverage.

Testing Suitability

User goal analysis: Users want to save money easily.

Suitability review questions:

Usability: Does the checkout page automatically recommend the optimal coupon, or must users manually compare a long list? If the latter, the feature, though correct, is “unsuitable” and harms experience.

Logic: When multiple coupons are eligible, can the system preview and compare the final discount amounts? Absence of this capability makes decision‑making difficult for users.

Reasonableness: The “one coupon per order” rule may conflict with simultaneous “full‑reduction” and “free‑shipping” coupons during big promotions, potentially degrading user experience.

Analysis: Suitability testing can reveal that a function, while technically correct and complete, fails to meet user expectations efficiently, prompting feedback to product managers for optimization.

Conclusion

In functional testing, correctness is the foundation (software must not err), completeness provides breadth (software must not miss any required behavior), and suitability adds height (software must be truly useful). Excellent test engineers should not stop at verifying correct implementation; they must adopt a user‑value perspective and evaluate the feature across all three dimensions. The coupon example demonstrates that only when accurate discount calculation, full scenario coverage, and effortless user experience are achieved does the feature qualify as high‑quality.

The ultimate testing goal is not merely defect detection but ensuring the delivered product is correct, complete, and genuinely suitable for user needs and expectations.