| A minimum test coverage level that must be met has been defined. |
|
|
|
|
0.1 |
0.3 |
0.5 |
0.8 |
0.8 |
| Continuous integration is supported – tests are automatically run whenever the source code changes. |
|
|
|
|
|
0.3 |
0.6 |
0.9 |
1.0 |
| For GUIs, project uses automated GUI test frameworks. |
|
|
|
|
|
0.2 |
0.5 |
0.8 |
0.8 |
| Project has automated tests to check conformance to coding standards. |
|
|
|
|
|
0.3 |
0.6 |
0.9 |
1.0 |
| Project has automated tests to check test coverage. |
|
|
|
|
0.1 |
0.3 |
0.5 |
0.8 |
0.8 |
| Project has integration tests. |
|
|
|
0.1 |
0.1 |
0.3 |
0.6 |
1.0 |
1.0 |
| Project has scripts for testing scenarios that have not been automated (e.g. for testing GUIs). |
|
|
|
|
|
0.2 |
0.6 |
1.0 |
1.0 |
| Project has unit tests. |
|
|
|
0.1 |
0.1 |
0.3 |
0.6 |
1.0 |
1.0 |
| Project recommends tools to check conformance to coding standards. |
|
|
|
|
0.1 |
0.3 |
0.5 |
0.8 |
0.8 |
| Project recommends tools to check test coverage. |
|
|
|
|
0.1 |
0.3 |
0.5 |
0.8 |
0.8 |
| Project specifies how to set up external resources e.g. FTP servers, databases for tests. |
|
|
|
|
|
0.3 |
0.6 |
0.8 |
0.8 |
| Test results are e-mailed to a mailing list. |
|
|
|
|
|
0.2 |
0.4 |
0.6 |
0.6 |
| Test results are visible publicly. |
|
|
|
|
|
0.1 |
0.5 |
1.0 |
1.0 |
| Test results are visible to all developers/members. |
|
|
|
|
0.1 |
0.3 |
0.6 |
1.0 |
1.0 |
| Tests are automatically run nightly. |
|
|
|
|
0.1 |
0.3 |
0.6 |
0.9 |
1.0 |
| Tests create their configuration own files, database tables etc. |
|
|
|
|
|
0.1 |
0.3 |
0.6 |
0.6 |
| There is an automated test for this minimum test coverage level. |
|
|
|
|
0.1 |
0.3 |
0.5 |
0.8 |
0.8 |
| This e-mailing list can be subscribed to by anyone. |
|
|
|
|
|
0.2 |
0.4 |
0.6 |
0.6 |