We released new versions of Marathon and MarathonITE. The major changes are:
1. Added a suite editor using which you can create new test suite files that can be executed in batch mode.
2. Fixed issues with MARATHON_HOME not being set properly in some cases.
3. Fixed issues pertaining to using plain JWindow objects.
4. Fixed recording and playback issues with file chooser and table header.
Detailed change log is available in the distributions.

We released new versions of Marathon and MarathonITE – our Java/GUI testing product – last week. The major changes are:
1. adding support for creating reports in testlink XML format.
2. Support for native-lib directive for WebStartOffline launcher.
3. Upgrading jRuby to 1.7.2 and also couple of support libraries.
4. MComboBox and MTreeNode – stripping of HTML markup in the text.
5. Fixing handling of HeavyWeightWindow on Java7 (more on this later).
More detailed changelog can be read from the ChangeLog in the distribution.
Java7 and HeavyWeightWindow
Java/Swing uses HeavyWeightWindow objects internally to …

We, at Jalian Systems, released a new version of MarathonITE (and Marathon) today. With this release, you can use MarathonITE in a team more comfortably by sharing the object map.
For using a shared object map, follow these steps.

Running omapserver (object map server)
Create a Marathon project using enhanced objectmap lookup strategy (or use an existing project).
In the project folder execute marathonite as follows:
marathonite -omapserver 20101
The 20101 is a port number, …

We released MarathonITE 3.2.6 today.The new version contains some bug fixes and couple of exciting features.

We are happy to announce the immediate availability of MarathonITE – our commercial Java GUI Test Automation tool based, of course, on Marathon. MarathonITE adds some features that are useful for creating Resilient Test Suites.
Our commitment to Marathon is strong as ever. We will be providing enhancements and support through google group.
We hope you like MarathonITE and it is useful to you for achieving success in your test automation projects. A formal press release follows.

(Version 3.2.2)
ObjectMap in Marathon uses component properties to create default names and identity to components that are displayed on the application screen. You can modify the omap-configuration.yaml file in the project directory to let the ObjectMap use different set of properties than that have been used. If you are using Marathonite you can use the Object Map Configuration Editor to modify the properties.
1. Naming Properties are used to name the components in the scripts. The default naming properties give prominence to what is visible on …