Use builder pattern instead of a custom constructor to map a BookEntry
Remove custom constructor as its signature is ambiguous and can lead to errors
Refactor BookEntry into Person to describe better what we are mapping
Push up gender related properties into a base class so that we can have a lighter object that maps the row if we are only interested in the gender
Create a mapper for the simpler BasicPerson BO
Switch configuration of spring application to start using annotations
Autowire the fieldset mappers to be used in the configuration
Find male entry using lighter BO
Add an explanation what this test does
Add new test to see if we are failing correctly
When testing a method which is being mocked we need to instruct to use the actual method implementation
Fixed bug where we weren't comparing the values correctly
Add more unit tests
Exceptions should be handled within the test
Remove duplicate code