Version 0.9.1

● Now you can open a scenario (or a comparison layer file) to see the zones it ignores
during comparisons, and you can edit this zones set, adding or removing some areas.
● The Local Scenario Player (you use to locally test your scenario) can now open and
play a list of selected scenarios. So you can test scenarios' sequences.
● Fixes the following 0.9 bug: when finishing test suite using an empty directory, the
test result comments (versions numbers displayed on report) were null.
● The report uses a new style

Version 0.9b

● You're not constraint anymore to add the getFrame() static method in your frame
code to “DiffChase” it, you can use the java awt Component.setName() method or
event detect the main frame name of application you don't have the code using the
FrameIdentifier
● Choose to display or not the comparisons animations to speed up a little
computations. (-Dskip.animation=true system property)
● Now you can exit the LocalPlayer (when checking your scenario correctness) using
the default Alt-Q key shortcut. If Alt-Q is a shortcut already used in your tested
application, you can override it by using the -Dexit.key and -Dexit.key.modifier
system properties.
● Creation of the realtime-mode attribute for gui-test and test-suite tags from the test
suite xml configuration: now some tests can be accelerated.
● When “DiffChased” GUI has changed between two versions, with too many ignored
zones that had moved, you can create files containing new zones to ignore. Then you
put those files in directories parsed by the controller when playing scenarios, it then
ignores the newly defined zones.
● Automatic restart of the tested swing application now keeps jvm properties you have
specified (e.g. The forced look and feel, etc...)
● Better logging for jDiffChaser controller and remote servers: one file per process.
● You can debug the remote launch process using the -Ddebug.restart property set to
true (to see the logs generated by the forked process). Only for debugging purpose.
● The “back to report” link (in a screenshot page) now sends you back to the location
you were in the report.
● You're no longer restricted to Swing Apps, AWT apps are now supported.
● And some refactoring, code cleaning, and so on...

Version 0.8.1

● Key events capture (was gone in 0.8 after having worked ok in 0.5)

Version 0.8

● Full screen capture (allows multiple window applications to be tested, window
moves to be tested,...)
● Delay before screenshot (if needed, 0 sec. delay is the default one)
● No need of bsh anymore to build jDiffChaser using ant
● Fix of a focus bug when having the end-of-recording dialog displaying
● Some waiting dialogs added in order to give some better UI feedback to the user.
● Frames and dialogs moves are handled
● Native libraries are only used when using java < 1.5 on Windows in order to have
always on top dialogs (Remote Control frame and waiting dialogs). Consequently,
OS X and probably other java-enabled platforms are now supported through java
1.5+ (Note that we need feedback from Linux users as we still didn't do some tests
with it)
● Report details: when clicking on an image, now allows to browse the three images of
the scenario (first one, second one and diffs one) with previous/next buttons
● Needs jdk 1.5+ to build a jar file that you can use either on hosts running Windows
with 1.4.2 java or any OS with 1.5+ java
● Fixes an OSX application restart bug that occurred when playing gui scenarios
suites
● Remote Control frame can be translucent: useful when recording full screen
applications scenarios