Testing a constructor
To test that a constructor does its job (of making the class invariant true), you have to first use the constructor in creating a new object and then test that every field of the object has the correct value. Yes, you need need an assertEquals call for each field.
Since the fields of a class are (usually) private, in order to test that a field has the correct value, you have to call a getter method to get the value of the field. Thus, testing that a constructor does its job automatically tests the getter methods; you don't need more tests for the getter methods. But the main focus is on testing the constructor.
We give an example of this below. To the left, you can see that class Time has two fields, hr and min, and that there are getter methods for them. To the right, procedure testConstructor1 creates a new local variable t and stores a new Time object in it; then, two assertEquals calls check the values in the fields.