data-driven_testing
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| data-driven_testing [2025/09/10 04:40] – plida | data-driven_testing [2025/09/10 04:40] (current) – plida | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| Source: Software Testing course at ITMO university by Kochubeev Nikolay Sergeevich | Source: Software Testing course at ITMO university by Kochubeev Nikolay Sergeevich | ||
| - | ====== Data-based testing ====== | + | ====== Data-driven |
| - | DBT is an approach to [[software_testing|testing]] in which one test function is executed multiple times with different sets of input data. This makes it easy to cover more cases and reduce code duplication.cases. | + | DDT is an approach to [[software_testing|testing]] in which one test function is executed multiple times with different sets of input data. This makes it easy to cover more cases and reduce code duplication.cases. |
| - | ==== Strengths of DBT ==== | + | ==== Strengths of DDT ==== |
| - They eliminate duplication of tests with different input data. | - They eliminate duplication of tests with different input data. | ||
data-driven_testing.1757479237.txt.gz · Last modified: by plida