State of the Implementation

Jester uses a simple text-based find-and-replace-style approach to modifying the original source code. This was simple to implement and has proved adequate so far. However, if Jester were to use a parsed representation of the source code (either using a parser on the source code or possibly working on class files), more sophisticated modifications, and better reporting of its modifications, would be easier to implement. Using a parsed representation would, for example, enable Jester to remove complete statements from methods and to report its changes per method rather than by character index/line number.