Interface Testing Guidelines

(1) Test external component calls with parameter values at the extreme ends of their ranges

(2) Always test interfaces with null pointer parameters where pointers are passed

(3) Design tests that deliberately cause components to fail when called through procedural interfaces

(4) Use stress testing in message-passing systems to generate many more messages than expected

(5) Vary the order in which components using shared memory are activated

Explanation

The five interface testing guidelines are: (1) test with extreme parameter values at both ends of valid ranges; (2) test with null pointers where pointers are passed across interfaces; (3) deliberately cause component failure to test failure assumptions; (4) stress test message-passing systems with excessive message loads; (5) vary activation order for shared-memory components to reveal implicit ordering assumptions.