fixture
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| fixture [2025/09/09 19:22] – plida | fixture [2025/09/09 19:24] (current) – plida | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| It is useful because of: | It is useful because of: | ||
| - | |||
| * The reuse of the arrangement code. | * The reuse of the arrangement code. | ||
| * A single initial state for a group of tests. | * A single initial state for a group of tests. | ||
| * Simplification and reduction of tests. | * Simplification and reduction of tests. | ||
| + | |||
| + | ==== Best practices ==== | ||
| + | - The fixtures should be minimal — just what is needed for the tests. | ||
| + | - Use SetUp/ | ||
| + | - In Python and Go, it is convenient to use yield/defer to free up resources. | ||
fixture.1757445773.txt.gz · Last modified: by plida