tools:tests:index
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
tools:tests:index [2019/01/30 18:09] – [Tests] till | tools:tests:index [2019/01/30 18:10] – [Tests] till | ||
---|---|---|---|
Line 9: | Line 9: | ||
<WRAP column 85%> | <WRAP column 85%> | ||
* Testing scientific software is highly important, | * Testing scientific software is highly important, | ||
- | * The largest part of scientific software is not thoroughly tested or even not tested at all. | + | * Most scientific software is not thoroughly tested\\ or even not tested at all. |
* Tests can only prove the existence of bugs, not their absence. | * 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. | + | * 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 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 leads to high test coverage. | + | * 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. | * High test coverage by automatic tests increases the trust in software. | ||
- | * Test-driven development leads to tests documenting | + | * Test-driven development leads to tests\\ that document |
</ | </ | ||
</ | </ |
tools/tests/index.txt · Last modified: 2020/09/27 12:26 by till