Continuous Integration & Automated Testing

Automated Testing

Automated testing is important as it allows us to easily test code quickly and repeatedly.

This usually exercise all the methods in the public interface of an isolated, independent class.

There is no strict definition for a unit, however it could be:

A method in a class working in isolation.
A flow of control when calling a method which covers a given set of paths.
- This is what you would use the cyclomatic count for.
A class.

In object oriented programs, the unit test should be at least 1 class in isolation.

In Java you can use JUnit to write unit tests.

Integration testing ensures that multiple units produce the correct output when they are working together.

You can also use JUnit to write integration tests.

This ensures that the whole system behaves as expected.

This can also be called acceptance testing, to verify, for the customer, that the system is complete.

There is no universal acceptance testing tool as it depends heavily on what system you are developing.

These are functional testing tools, specifically for web interfaces. You can:

There are several web testing frameworks:

These testing frameworks have the following issues:

There are two main performance testing frameworks for Java:

JUnitPerf:
- Does unit performance testing.
- It decorates existing JUnit tests so that they fail if running times are exceeded.
JMeter:
- Provides functional performance testing:
  - Can measure web server response times.
- Is site agnostic.
- Can’t run JavaScript.

This is the automatic process of building the complete system for ever commit. This has the advantages of:

Ant is a build tool for Java that makes:

possible in a single command that can be automated.