tools:tests:index
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| tools:tests:index [2019/01/30 17:47] – created till | tools:tests:index [2020/09/27 12:26] (current) – [Which tool to use] till | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{fa> | + | {{fa> |
| + | ====== Tests ====== | ||
| // | // | ||
| + | |||
| + | <WRAP group> | ||
| + | <WRAP column 32px> | ||
| + | <WRAP column 85%> | ||
| + | * Testing scientific software is highly important, | ||
| + | * Most scientific software is not thoroughly tested\\ or even not tested at all. | ||
| + | * Tests can only prove the existence of bugs, not their absence. | ||
| + | * Testing should be done as early as possible, as often as possible,\\ and as automatic as possible. | ||
| + | * Test automatisation has dramatic impact on the design\\ of the code to be tested (e.g., modularity). | ||
| + | * Test-driven development turns the usual sequence upside down\\ and results in high test coverage. | ||
| + | * High test coverage by automatic tests increases the trust in software. | ||
| + | * Test-driven development leads to tests\\ that document the code and its specifications. | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | |||
| + | ===== Which tool to use ===== | ||
| + | |||
| + | Note: This section is clearly opinionated. There are definitely other tools available. However, this is the tool the author recommends from own experience. | ||
| + | |||
| + | <WRAP group> | ||
| + | <WRAP column 32px> | ||
| + | <WRAP column 76%> | ||
| + | [[https:// | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | |||
| + | \\ | ||
| + | <WRAP half column leftalign>< | ||
| + | <WRAP half column rightalign>< | ||
tools/tests/index.1548866852.txt.gz · Last modified: 2019/01/30 17:47 by till