Catch Bugs Early

The earlier that bugs (which developers like to refer to as "features") are caught in the release cycle, the cheaper they are to fix. Bugs that make it into the live product can be catastrophic, but bugs that are caught as soon as they are created are inexpensive to put right.

Unit Testing

By writing a unit test for each possible use of a Java class, developers can ensure that their code will work first time and will not be inadvertantly broken in the future. If you do not already have a culture of testing, we can help your team integrate testing into their development process.

Continuous Integration

We can install a "Continuous Integration" monitoring tool which will check out your entire Java codebase on a daily, or even hourly, basis and run all the unit tests. This helps identify bugs that have crept into the application as soon as this happens.

Code Coverage

By installing a simple tool to check code coverage, the team has a measure of how effective their unit tests are. At all times, the development team can see the percentage of Java code that is being unit tested, and exactly which functionality is lacking in proper testing. The team then has an aim of moving towards 100% code coverage.

Architectural Design and Package Dependencies

A tangled Java package dependency configuration is a sign that an application may be hard to maintain. We can help you analyse your package dependencies, eliminate disastrous cyclic dependencies, and define an architectural structure that developers should adhere to. We can even go so far as to install tools to prevent developers checking in code that violates the prescribed architecture, if you wish.