unit_test
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| unit_test [2025/09/09 19:20] – plida | unit_test [2025/09/10 07:04] (current) – plida | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ====== Unit tests ====== | ====== Unit tests ====== | ||
| - | Unit tests check individual units of software (be it functions, methods or classes) in isolation from the rest of the system. The goal is to ensure that every module works as intended. | + | Unit tests check individual units of software (be it functions, methods or classes) in isolation from the rest of the system. The goal is to ensure that every module works as intended. They' |
| ==== Concepts ==== | ==== Concepts ==== | ||
| Line 13: | Line 13: | ||
| [[property-based_testing|Property-based testing]] is an approach to testing in which we test the properties of a function rather than individual examples. | [[property-based_testing|Property-based testing]] is an approach to testing in which we test the properties of a function rather than individual examples. | ||
| - | [[fixtures|Fixtures]] is a defined and reliable context for the tests. | + | [[data-driven_testing|Data-driven testing]] is an approach in which one test function is executed multiple times with different sets of input data. |
| + | |||
| + | [[fixture|Fixture]] is a defined and reliable context for the tests. | ||
| ==== Benefits ====== | ==== Benefits ====== | ||
unit_test.1757445608.txt.gz · Last modified: by plida