A black-box Software testing technique used to test systems with complex business logic.
- Methodologien: Maschinenbau, Produktdesign, Projektmanagement
Decision Table Testing

Decision Table Testing
- Agile Methodik, Prozessverbesserung, Prozess-Optimierung, Qualitätssicherung, Qualitätskontrolle, Qualitätsmanagement, Qualitätsmanagement-System (QMS), Software-Prüfung, Testmethoden
Zielsetzung:
Wie es verwendet wird:
- A tester creates a table that lists all possible combinations of input conditions and the corresponding actions or outcomes. This ensures that every combination of business rules is tested systematically.
Vorteile
- Provides a systematic way to test complex business rules, ensuring full coverage; helps to identify gaps or contradictions in the requirements; easy to understand.
Nachteile
- The number of combinations can become very large and unmanageable if there are many input conditions; it does not test the sequence of events.
Kategorien:
- Maschinenbau, Qualität
Am besten geeignet für:
- Systematically testing complex business logic by creating a table of all possible input combinations and expected outcomes.
Decision Table Testing is particularly beneficial in sectors such as finance, telecommunications, healthcare, and software development where intricate business rules govern transactions or processes. For instance, in the insurance industry, a decision table can encompass various factors, including customer age, policy type, and claim history, thereby allowing underwriters to clarify how different combinations affect premium calculations or claim approvals. This methodology is particularly effective during the testing phase of product development, where stakeholders such as business analysts, quality assurance testers, and software engineers collaborate to evaluate business logic implementation. By systematically listing input combinations with their expected results, teams can monitor and refine edge cases that might not surface during traditional testing. This aids in identifying not only gaps in logic but also overlaps, ensuring that business rules align with project specifications. Using tools like spreadsheets or specialized software can further enhance collaboration among team members, allowing for efficient updates to tables with increasing project complexity. Consequently, the visual nature of decision tables enhances communication clarity among team members and stakeholders, supporting better decision-making and accelerating the testing process without sacrificing thoroughness.
Die wichtigsten Schritte dieser Methodik
- Identify input conditions relevant to the business rules.
- List all possible combinations of these input conditions.
- Define the expected actions or outcomes for each combination.
- Create a decision table that organizes input combinations and corresponding outcomes.
- Review the table for completeness and correctness against requirements.
- Execute test cases derived from the decision table.
- Analyze results to determine if actual outcomes match expected outcomes.
- Identify any missing combinations or discrepancies and adjust the table as needed.
Profi-Tipps
- Incorporate boundary Werte Analyse into the decision table to validate edge cases that may not be covered by standard combinations.
- Use automated tools to manage and generate decision tables, which can minimize errors and expedite the testing process over time.
- Periodically review and revise decision tables as business rules evolve, ensuring they remain relevant and comprehensive against changing requirements.
Verschiedene Methoden lesen und vergleichen, Wir empfehlen die
> Umfassendes Methoden-Repository <
zusammen mit den über 400 anderen Methoden.
Ihre Kommentare zu dieser Methodik oder zusätzliche Informationen sind willkommen auf der Kommentarbereich unten ↓ , sowie alle ingenieursbezogenen Ideen oder Links.
Verwandte Artikel
Fragebögen zu muskuloskelettalen Beschwerden
Multivariate Tests (MVT)
Mehrfache Regressionsanalyse
Motion-Capture-Systeme
MoSCoW-Methode
Moods Median-Test