I use VisualAge-Java, so line numbers are hard to determine. Could the reports print the method name where the mutation failed? - MarkWindholtz. OliBye suggests using ctrl-g in the class source view, this will jump to a line number. (IvanM - as line numbers are now printed, and I use VAJ3.5 which has the class source view, I won't be doing this story for a while)
Done:
When Jester mutates public final constants this often doesn't cause the expected errors because when the JUnit testing code was compiled references to those constant values were inlined. It would be nice to be able to force a recompilation of the JUnit testing code in these circumstances. considered done in Jester 1.22 because now you can use Ant to do the compilation, and that correctly recompiles dependent files (see jester.sf.net/hintsAndTips.html)
When running tests at startup, time them and set a timeout on mutation tests based on it (for instance, first tests take 30 seconds, mutations time out (and assume failure) at 300 seconds) - this should help the 'mutation causes infinite loop' problem. done in Jester 1.20
New mutation: < to <= (and vice versa, and same for >). this and the following are done (or easy for user to do) because mutations are configurable in Jester 1.14
Mutate constant strings ("abc" becomes "cab" or somesuch).
Mutate && and ||
Mutate -- and ++ Done in Jester 1.07 - rolled back in 1.08 - see JesterChanges108
Change ! to ' ' (note: vice versa won't compile)
I'd like the line number of a change to be printed, rather than the less-than-useful character numbers. Done in Jester 1.13
New option for setting the compiler (and its command line args) to use (mutations would run faster with jikes, for instance) Done in Jester 1.12
Properties file for the 'RemoveComment?' option and future ones Done in Jester 1.10
Mutate == and != Done in Jester 1.07
It'd be nice to have a score at the end ("took 7 minutes, 12 mutations survived out of 53"). Done in Jester 1.07
I'd like it to try changing if statements around, i.e. the true branch and false branch swapped around. Jester 1.05 does the equivalent by having "always true" and "always false" what about code that's reached by a true then false branch? -- OliBye
I'd like it to keep going rather than stop if it changes the source such that it won't compile any more (i.e. change the code back to how it was and stop trying to change that class but continue with the next class etc). Fixed in Jester 1.05
It seems to me that Jester would be much more useful to me if it stopped reporting that it had tried changing code inside of comment blocks and noting that lo and behold, no tests were broken as a result ;-). Option available in Jester 1.05
I'd like JesTer to work with the latest version of JUnit (at time of writing, 3.5). Fixed in Jester 1.05
JesterStories