Task description

The aim of this task is to practise unit tests creation with JUnit.

Coding Conventions

Sun Microsystems Java Coding Conventions http://java.sun.com/docs/codeconv/index.html

Only english words can be used to name classes, field, methods etc. Fields and variables are nouns, where methods are verb phrases:

• setters are setXXX. If a given value is boolean then use to complementary methods instead of one with a boolean argument.
  Example:
  private boolean readonly = false;
public void setReadOnly() { readOnly = true; }
public void setReadWrite() { readOnly = false; }

• geters are getXXX. If a returned value is of type boolean then the metod name is isXXX e.g. isReadOnly.
• Methods performing time consuming calculations start with calculateXXX
• Methods adding to a collection starts with addXXX.
• Methods removing from a collection are removeXXX

Bad smells

Avoid bad smells in unit tests presented on the Unit Testing lecture. Files should be placed in separate directories for source and tests. Avoid duplicated code in your tests. testXXX method should contain only one test case. Do not put absolute paths in your tests. All tests should run not only on authors' machine.

One should also avoid the following improper code constructs:

Long Method (more information can be found here)

• long methods > 20 LOC
• cramped methods e.g. complex expressions - it is better to extract them to a separate method and give that method a descriptive name
• complex methods > 4 cyclomatic complexity

Data Class (more can be found here)

• public fields
• improper collection encapsulation
• data structure - class containing only get/set methods
• get/set methods that are never used

Technical documentation

Unit tests should be self documenting, so technical documentation is optional.

Task

One should test GeometricSeries class. Reading from file, throwing exceptions, and private methods should also be tested. How to test private methods can be found here.

Evaluation

One should deliver test suite with test cases. Occurrence of at least one bad smell lowers a grade by 1. Occurrence of two smells lowers a grade by 2. Violations of Java Coding Conventions and/or faults in javadoc lower a grade by 0.5. Improper behavior of the program lowers a grade by 0.5. Program that has compilation errors will not be evaluated.