Understanding Functional Testing: Correctness, Completeness, and Suitability

Core Characteristics of Functional Testing

Functional testing verifies that software behavior conforms to the functional requirements specification. The evaluation focuses on three dimensions:

Correctness – ensures every requirement is implemented accurately; output, state changes, and calculations must match expectations. Test focus includes input/output validation, business‑logic verification, calculation accuracy, and methods such as equivalence partitioning, boundary‑value analysis, and decision‑table testing.

Completeness – checks that the functional scope covers all explicit and implicit requirements, guaranteeing no missing features. Test focus includes functional‑point coverage, scenario completeness, and uncovering omitted performance or security‑related functional impacts, using traceability matrices, functional decomposition diagrams, and use‑case scenarios.

Suitability – assesses whether the implemented functions are useful and aligned with user goals. It examines functional value, interaction rationality, and potential redundancy or missing steps, employing user reviews, usability testing, and expert walkthroughs.

Relationship Diagram

Correctness (Do it right) → Precise technical implementation

Completeness (Do it all) → Full requirement coverage

Suitability (Do it well) → User goals satisfied

Case Study: Coupon Feature in an E‑Commerce Platform

The simplified requirement states that users can view and apply coupons under specific conditions such as minimum spend, product category, and expiration date, with a limit of one coupon per order.

1. Testing Correctness

TC1: User has a "¥100‑off‑¥20" coupon, cart total ¥120 – verify coupon is selectable and final payment is ¥100.

TC2: Cart total ¥90 – verify the coupon is not selectable.

TC3: Expired coupon – verify it is unusable for any amount.

TC4: User has a category‑restricted coupon (electronics) and a universal coupon; adding a book to the cart should make the category coupon unavailable while the universal coupon remains selectable.

These cases precisely validate business rules such as discount thresholds, expiration handling, and category restrictions.

2. Testing Completeness

Requirement traceability checks reveal additional implicit needs:

Support for viewing coupons by status (unused, used, expired).

Potential exclusion rules like "no discount on promotional items" or "first‑purchase only" that may be missing.

Confirmation that coupons cannot be stacked, as explicitly stated.

Scenario completeness questions include whether coupon state synchronizes across devices and whether cancelled orders automatically restore the coupon.

3. Testing Suitability

User goal analysis shows the primary objective is to save money easily.

Usability issue: Does the checkout page automatically recommend the optimal coupon, or must the user manually compare a long list?

Logic issue: When multiple coupons are eligible, can the user preview and compare the final discount amounts?

Rationality issue: Does the "one coupon per order" rule conflict with simultaneous promotions like free‑shipping coupons, potentially harming the user experience?

Suitability testing may uncover that, although the feature is technically correct and complete, it does not deliver the most efficient or user‑friendly experience, prompting feedback to product managers for improvement.

Conclusion

Effective functional testing requires addressing all three dimensions: correctness ensures the software does not err, completeness guarantees no required functionality is omitted, and suitability confirms the feature truly serves user needs. The coupon example demonstrates how each dimension contributes to delivering a high‑quality, user‑centric function.