A GUI comparison tool that automates diffs detection between versions. You can record and play scenarios on two different releases of the same app (in sequential or parallel mode); jDiffChaser compares both screens and shows you the differences.
Be the first to post a text review of jDiffChaser. Rate and review a project by clicking thumbs up or thumbs down in the right column.
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.9 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 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. AWT applications are supported. And some refactoring, code cleaning, and so on...
The latest version of this automated GUI comparison software, a developer tool to avoid rendering regressions. You can now add additional zones to ignore during GUI comparisons in external files, use the comparison file editor to edit scenarios, exit the local player using a key shortcut you define, you don't need to add a getFrame method in your code anymore, you can use the Frame Identifier tool to launch jDiffChaser on an application you don't have the code anymore, you can accelerate automated moves, skip animations, you can locally launch a suite of scenarios to test... and you have a better looking report with a new style.
Be the first person to add a text review.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?
Thanks for your review!
Get credit for your review by logging in via OpenID. Click your account provider: