The code in the Job classes could be split into more semantically named methods, like for instance populateBook(String html), and thereby more efficiently unit-tested. (This thought is based on SearchJob but I would guess it's applicable to other job classes as well.)
The code in the Job classes could be split into more semantically named methods, like for instance populateBook(String html), and thereby more efficiently unit-tested. (This thought is based on SearchJob but I would guess it's applicable to other job classes as well.)