This matching exercise pairs fundamental black-box testing techniques with their specific methods for selecting test inputs, particularly for negative or error-handling test cases.

• State-Based Analysis focuses on testing the system's behavior as it moves between different states. A key aspect is to provide an unexpected or invalid input for a specific state (a known condition) to ensure it is handled gracefully without causing a system failure.
• Equivalence Class Analysis divides all possible inputs into partitions or "classes." The most robust test plans select representatives from each valid and invalid partition. Selecting an input that falls outside any defined partition tests the system's default error-handling capabilities.
• Decision Table Analysis is ideal for testing complex business rules governed by multiple conditions. It maps combinations of inputs to specific actions. Testing invalid or impossible combinations is crucial to verify that the system's logic correctly identifies and rejects them.
• Boundary Value Analysis is a technique based on the principle that errors often occur at the edges or boundaries of input domains. Therefore, test cases are designed specifically using values at the minimum and maximum limits of a valid range.

Ammann, P., & Offutt, J. (2016). Introduction to Software Testing (2nd ed.). Cambridge University Press.

Boundary Value Analysis: "Boundary value analysis (BVA) is based on a simple observation: programmers often make mistakes on the boundaries of input and output domains." (Chapter 4, Section 4.2, p. 77). This directly supports matching BVA with selecting inputs at the external limits.

Equivalence Class Partitioning: This source describes creating partitions for both valid and invalid inputs. The concept of selecting an input outside all partitions is an extension of testing invalid classes to check default error conditions. (Chapter 4, Section 4.1, pp. 74-75).

Jorgensen, P. C. (2013). Software Testing: A Craftsman's Approach (4th ed.). CRC Press.

Decision Table Testing: "The real value of decision tables for testing is that they deal with combinations of inputs." The text further explains creating test cases for each column (rule), which inherently includes testing invalid or contradictory combinations to ensure proper error handling. (Chapter 8, Section 8.2, pp. 201-205).

State-Based Testing: "We can ask what happens if an invalid event occurs in a state... This is a standard test for robustness." This confirms that testing with unexpected inputs (invalid events) for a given state is a core part of State-Based Analysis. (Chapter 9, Section 9.4, p. 235).

Koomen, T., van der Aalst, L., Broekman, B., & Vroon, M. (2006). TMap NEXT: For result-driven testing. Addison-Wesley Professional.

This industry-standard text outlines these techniques in practice. It describes State-Transition Testing (State-Based Analysis) as involving the creation of test cases for invalid transitions (p. 288), Decision Table Testing for combinations of conditions (p. 286), and Boundary Value Analysis for the "outermost values of equivalence classes" (p. 284).