You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

DelftShell is becoming a framework in which desktop applications throughout Deltares can be embedded. For this to happen the quality of the framework should meet high standards. In order to achieve these high standards we need sourcecode that is well tested. To achieve this goal we would like to suggest the following improvements to the test procedure

Committed testers
make sure we have committed testers, that are a member of the team. Testers should attend planning sessions, cool down sessions and should work side by side with developers. It would also be good if they could attend the morning sessions. Often a tester could sit next to a developer so the developer can make small changes on the fly and identify larger issues for review of the product owner.

Unit test coverage
Unit test coverage of DelftTools and DelftShell are now at about 32%. This number should be raised to at least 70% for DelftTools and maybe 50% for DelftShell. Each member of the team should write some unit tests for DelftShell or DelftTools classes that are being used in the code he is currently modifying. It is recommended to install testdriven.net or ncover so the developers can see areas of sourcecode that are not sufficiently tested.

  • No labels