GUI Test Automation for Java/Swing Applications With Marathon and MarathonITEGUI Test Automation for Java/Swing Applications With Marathon and MarathonITE | Marathon

Released: Marathon and MarathonITE 3.3.2

admin — Wed, 24 Apr 2013 10:59:42 +0000

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.

The post Released: Marathon and MarathonITE 3.3.2 appeared first on GUI Test Automation for Java/Swing Applications With Marathon and MarathonITE.

Marathon and MarathonITE 3.2.9.2 release

admin — Mon, 11 Mar 2013 09:27:51 +0000

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 display combo box lists, dropdown menus etc. Uptill Java6, the HeavyWeightWindow constructor was setting a name to these windows that start with ‘###’ and Marathon ignores these windows by using the names. In Java7, a Window#Type enum is introduced. Window#getType returns a Window#Type enum that is either one of NORMAL, POPUP or UTILITY. And also Java7 doesn’t set the name for the window. Unfortunately, none of our testcases have a case where a HeavyWeightWindow is used for Menu/Combo popups – so we missed it. So if you find Marathon recording menu clicks with no title windows, upgrade to 3.2.9.2 and it should fix the problem for you.

The post Marathon and MarathonITE 3.2.9.2 release appeared first on GUI Test Automation for Java/Swing Applications With Marathon and MarathonITE.

MarathonITE 3.2.9 is released with object map sharing support

admin — Fri, 28 Dec 2012 11:32:00 +0000

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, you can give any other port number for the server.
MarathonITE client
Create a Marathon project and use remote objectmap as lookup strategy.
Give the IP address/hostname and the port number in the fields.

From now onwards, MarathonITE uses the object map from the server. You can edit the shared object map from the server and the changes will be available to all the MarathonITE instances using this server.

The post MarathonITE 3.2.9 is released with object map sharing support appeared first on GUI Test Automation for Java/Swing Applications With Marathon and MarathonITE.

Step by Step: Using ObjectMap (enhanced) with test devlopment mode

admin — Thu, 13 Dec 2012 11:41:26 +0000

» marathonite only

Using MarathonITE you can choose a object lookup strategy that suits your project needs. If you decide to use Object Map as your lookup strategy, select ‘Use Object Map (enhanced)‘ instead of the standard ‘Use Object Map‘.

The enhanced object map strategy can be used in two modes. When developing tests, use ‘Test Development Mode’. In this mode, whenever MarathonITE is unable to choose a component due to conflict in the recognition properties it uses a fallback mechanism to choose a closest match. MarathonITE also provides feedback as to why the recognition failed – using which you can update the object map.

When you want to run the tests in production environment, disable the ‘Test Development Mode’. MarathonITE uses strict matching for the component recognition.

Steps

Step One: Start MarathonITE.
Step Two: Configure Project tab.
Step Three: Select Test Development Mode.
Step Four: Configure Application tab.
Step Five: Select the Enhanced Object Map Lookup Strategy.
Step Six: Select a Scripting Language.
Step Seven: Save the Project Settings.
Step Eight: Check for a Log Messages.
Step Nine: Check for the Description and Suggestion.
Step Ten: Select the Object Map Editor.
Step Eleven: Modify the Object Map entry for the Component.
Step Twelve: Create a New Fixture(If needed).
Step Thirteen: Select a object lookup strategy.

Step One: Start MarathonITE.

Launch MarathonITE. You can either use the batch file or executable to launch MarathonITE.
ITE." />

MarathonITE displays Select Directory dialog. You can either select a project to work with from this dialog or create a new project. The Project Directory combo box displays the most recently used projects. If this is the first time you are launching MarathonITE, the Project Directory combo box will be empty.

Step Two: Configure Project tab.

In the Select Directory dialog click on New button.
Project tab." />

MarathonITE opens the Configure dialog. The project configuration dialog is split across multiple tabs. In this article, we will be using only the Project, Application and Language tabs. Check the user guide for using the other tabs.

When the Configure dialog is opened, the Project tab is selected. Give a name to your project in the Name field. Click on the Browse button and select a directory to create the project. If the given directory does not exist, MarathonITE creates the directory when you save the project.

Optionally you can type some information as description of the project in the Description text field.

Some java applications uses Command key on Mac OSX and Control key on other platforms. You can select Use platform specific… option to make MarathonITE use a different command key while playing the tests. Note that the recording still records Command/Control keys. This option effects only playing the scripts.

Step Three: Select Test Development Mode.

Under Project tab click on the Use test development mode check box.

When Enhanced Object Map Strategy is used with the test development mode it provides a fallback mechanisms to handle the MarathonITE object recognition in a unique way. Otherwise MarathonITE through an Exception when component recognition properties are matched.

Step Four: Configure Application tab.

Click on the Application tab and select any Application Launcher from Launcher drop down.
Application tab." />

MarathonITE provides more ways to launch Java applications. Select Application Launcher as per your application is bundled – either an executable, applet or webstart etc.

With Command Line Launcher, Click on the Browse… button to select the batch script of your application. You can select a working directory by clicking Browse… button attached to the working directory field.

The Command Line field should contain the full path to the batch/executable file and any parameters that need to be passed to it while launching from a shell prompt.

Step Five: Select the Enhanced Object Map Lookup Strategy.

Click on the Object Lookup tab. Select the Use ObjectMap (enhanced) from Object lookup strategy ComboBox.

The enhanced object map strategy includes fallback mechanisms when a component could not be found in the object map. When this option is selected, MarathonITE uses intelligent match algorithms to find a closest match for a component. The fallback mechanisms are used only in the test development mode.

Step Six: Select a Scripting Language.

Click on the Language tab. Select the Script drop down list to choose a language that is to be used for recording test scripts.

For each scripting language supported by MarathonITE you will see an entry in the ‘Script’ combo box. MarathonITE extends the standard script models to provide additional functions. If you are using MarathonITE select an entry that ends with for MarathonITE.

Step Seven: Save the Project Settings.

Click on Save button to save the project. The newly created project is selected in the Project Directory combo box. Click on Select button to open the MarathonITE Main window.

By selecting ‘default.rb‘ a script file we can see that a selected Object lookup strategy is ObjectMap (enhanced) lookup strategy.

Step Eight: Check for a Log Messages.

Start recording the Test case by selecting Start recording button from the task bar. Once the recording is done click on the Record & Playback Log tab in the bottom pane.

Record & Playback Log tab shows the warnings occurred due to matched recognition properties of a components or no components matched during Recording & Playing the Test case.

Step Nine: Check for the Description and Suggestion.

Select the message in the Record & Playback Log tab. Click on the Show message icon to see the description even Double clicking on a row displays the complete message in a window.

The problem is there are two components that are equally good and MarathonITE is unable to identify one. MarathonITE searches for a closest match and update the object map, to make a unique recognition.

Step Ten: Select the Object Map Editor.

Click on the Modify the recognition properties for objects on the toolbar or select «Object Map» → «Edit Object Map» from the menu or press Control+Shift+O to open Object Map Editor.

you can see the Object Map updated with a closest match.

Step Eleven: Modify the Object Map entry for the Component.

Click on the desired component in the left pane to edit its properties. Select the matched recognition property in the top part of the right pane and click on the Remove button.

Once the matched recognition property is removed click on Add button to add a closest Recognition Property to the selected component.

Finally click on the Ok button.

You need to provide some unique recognition properties for the components for MarathonITE to work properly.

Step Twelve: Create a New Fixture(If needed).

Object lookup strategies are related to a Fixture so even though with the default Fixture default.rb with ObjectMapNamingStrategy MarathonITE allows you to create a multiple Fixtures with different Object lookup strategies.

Select «File» → «New» → «New Fixture» from the menu bar.

MarathonITE opens the Create New Fixture dialog.

Give a name to your Fixture in the Name field.

Optionally you can type some information as description about the Fixture in the Description text field.

Step Thirteen: Select a object lookup strategy.

Click on the Object Lookup tab. Select the Lookup strategy from Object lookup strategy ComboBox.

Click on the OK button. MarathonITE creates a new Fixture and opens it in the editor. The Fixture with a newly selected Object lookup strategy is saved under Fixture folder under project directory.

The post Step by Step: Using ObjectMap (enhanced) with test devlopment mode appeared first on GUI Test Automation for Java/Swing Applications With Marathon and MarathonITE.

Step by Step: Selecting Object Lookup Strategies

admin — Thu, 06 Dec 2012 09:04:04 +0000

» marathonite only

MarathonITE provides multiple mechanisms of object recognition. MarathonITE object naming and recognition is handled by a pluggable interface. MarathonITE ships with two strategies Use Object Map and Create names using properties. Later versions of MarathonITE shall support other strategies as well.

Steps

Step One: Start MarathonITE.
Step Two: Configure Project tab.
Step Three: Configure Application tab.
Step Four: Select a object lookup strategy.
Step Five: Select a Scripting Language.
Step Six: Save the Project Settings.
Step Seven: Create a New Fixture(If needed).
Step Eight: Select a object lookup strategy.

Step One: Start MarathonITE.

Launch MarathonITE. You can either use the batch file or executable to launch MarathonITE.
ITE." />

MarathonITE displays Select Directory dialog. You can either select a project to work with from this dialog or create a new project. The Project Directory combo box displays the most recently used projects. If this is the first time you are launching MarathonITE, the Project Directory combo box will be empty.

Step Two: Configure Project tab.

In the Select Directory dialog click on New button.
Project tab." />

MarathonITE opens the Configure dialog. The project configuration dialog is split across multiple tabs. In this article, we will be using only the Project, Application and Language tabs. Check the user guide for using the other tabs.

When the Configure dialog is opened, the Project tab is selected. Give a name to your project in the Name field. Click on the Browse button and select a directory to create the project. If the given directory does not exist, MarathonITE creates the directory when you save the project.

Optionally you can type some information as description of the project in the Description text field.

Some java applications uses Command key on Mac OSX and Control key on other platforms. You can select Use platform specific… option to make MarathonITE use a different command key while playing the tests. Note that the recording still records Command/Control keys. This option effects only playing the scripts.

Step Three: Configure Application tab.

Click on the Application tab and select any Application Launcher from Launcher drop down.
Application tab." />

MarathonITE provides more ways to launch Java applications. Select Application Launcher as per your application is bundled – either an executable, applet or webstart etc.

With Command Line Launcher, Click on the Browse… button to select the batch script of your application. You can select a working directory by clicking Browse… button attached to the working directory field.

The Command Line field should contain the full path to the batch/executable file and any parameters that need to be passed to it while launching from a shell prompt.

Step Four: Select a object lookup strategy.

Click on the Object Lookup tab. Select the Lookup strategy from Object lookup strategy ComboBox.

Create Names using Object Properties uses unique properties of each object to identify the component and to name it. This strategy is useful when source code can be modified to set unique properties to components using Component#setName or labeledBy properties.

Using Object Map provides more flexibility to change the name of a component or its recognition properties.

Step Five: Select a Scripting Language.

Click on the Language tab. Select the Script drop down list to choose a language that is to be used for recording test scripts.

For each scripting language supported by MarathonITE you will see an entry in the ‘Script’ combo box. MarathonITE extends the standard script models to provide additional functions. If you are using MarathonITE select an entry that ends with for MarathonITE.

Step Six: Save the Project Settings.

Click on Save button to save the project. The newly created project is selected in the Project Directory combo box. Click on Select button to open the MarathonITE Main window.

By selecting ‘default.rb‘ a script file we can see that a selected Object lookup strategy is ObjectMapNamingStrategy.

Step Seven: Create a New Fixture(If needed).

Object lookup strategies are related to a Fixture so even though with the default Fixture default.rb with ObjectMapNamingStrategy MarathonITE allows you to create a multiple Fixtures with different Object lookup strategies.

Select «File» → «New» → «New Fixture» from the menu bar.

MarathonITE opens the Create New Fixture dialog.

Give a name to your Fixture in the Name field.

Optionally you can type some information as description about the Fixture in the Description text field.

Step Eight: Select a object lookup strategy.

Click on the Object Lookup tab. Select the Lookup strategy from Object lookup strategy ComboBox.

Click on the OK button. MarathonITE creates a new Fixture and opens it in the editor. The Fixture with a newly selected Object lookup strategy is saved under Fixture folder under project directory.

The post Step by Step: Selecting Object Lookup Strategies appeared first on GUI Test Automation for Java/Swing Applications With Marathon and MarathonITE.

Step by Step: Creating a Project with Web Start Offline Launcher

admin — Thu, 06 Dec 2012 05:54:23 +0000

» marathonite only

Java Web Start is a mechanism for program delivery through a standard Web server. You start a webstart enabled Java application by using a JNLP file – a XML file that contains information needed to start the application. Due to the network traffic involved, launching a webstart application consumes time which might not be suitable for running tests. MarathonITE includes a offline launcher for webstart applications. When used, MarathonITE downloads all the jar files supporting your application into a cache folder. During testing of your application, MarathonITE will use these downloaded jar files instead of connecting to the remote server.

Here are the steps to follow for creating a MarathonITE project using the Webstart Offline launcher.

Steps

Step One: Start MarathonITE.

Launch MarathonITE. You can either use the batch file or executable to launch MarathonITE.
ITE." />

MarathonITE displays Select Directory dialog. You can either select a project to work with from this dialog or create a new project. The Project Directory combo box displays the most recently used projects. If this is the first time you are launching MarathonITE, the Project Directory combo box will be empty.

Step Two: Configure Project tab.

In the Select Directory dialog click on New button.
Project tab." />

MarathonITE opens the Configure dialog. The project configuration dialog is split across multiple tabs. In this article, we will be using only the Project, Application and Language tabs. Check the user guide for using the other tabs.

When the Configure dialog is opened, the Project tab is selected. Give a name to your project in the Name field. Click on the Browse button and select a directory to create the project. If the given directory does not exist, MarathonITE creates the directory when you save the project.

Optionally you can type some information as description of the project in the Description text field.

Some java applications uses Command key on Mac OSX and Control key on other platforms. You can select Use platform specific… option to make MarathonITE use a different command key while playing the tests. Note that the recording still records Command/Control keys. This option effects only playing the scripts.

Step Three: Configure Application tab.

Select the Application tab. Select the Webstart Offline Launcher drop down.
Application tab." />

Click on the Browse… button select the JNLP file of your application. You can also enter the URL into the text field.

Enter a directory name in the Cache: field to download the jar files. MarathonITE creates this directory in your project directory and downloads all the jar files that supports your application when you start using it.

Optionally, if you click on the Reload button, MarathonITE will automatically deletes the existing jar files and reloads the new jar files of your application into the directory each and every time you start the application.

Step Four: Select a object lookup strategy.

Click on the Object Lookup tab and select an option from the Object Lookup Strategy: drop down.

Step Five: Select a Scripting Language.

Click on the Language tab. Select the Script drop down list to choose a language that is to be used for recording test scripts.

For each scripting language supported by MarathonITE you will see an entry in the ‘Script’ combo box. MarathonITE extends the standard script models to provide additional functions. If you are using MarathonITE select an entry that ends with for MarathonITE.

Step Six: Save the Project Settings.

This launcher doesn’t support Test mode to launch your application like the remaining launchers.

So, click on Save button to save the project. The newly created project is selected in the Project Directory combo box. Click on Select button to open the MarathonITE Main window.

Your MarathonITE project with Webstart Offline launcher is created.

The post Step by Step: Creating a Project with Web Start Offline Launcher appeared first on GUI Test Automation for Java/Swing Applications With Marathon and MarathonITE.

New features in MarathonITE 3.2.6

admin — Tue, 04 Dec 2012 10:22:07 +0000

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

MarathonITE now supports a offline launcher for WebStart applications. Some of you have complained that testing WebStart applications with MarathonITE was slow. Since the WebStart launcher connects to the remote server, even when the server is on the LAN – this causes slowness. Besides this issue, the signing requirements of webstart applications make them tougher to launch with lot of alert dialogs popping over if the JARS are not signed.

The offline launcher downloads the JNLP and JAR files into a cache folder. This is similar to what javaws command does. The difference is that the offline launcher doesn’t check the remote server for updates each and every time. For that create another fixture with reload option enabled and run a testcase with it. We hope this will find good use in your testing projects.

Another feature of MarathonITE is addition of ‘Create names using object properties’ strategy to object lookup strategies. You can create a fixture by selecting this strategy. Using this strategy is helpful in cases where you have access to the source code and setup object properties like name/labeled by etc. Besides that you may find this strategy useful when you are performing exploratory testing, since you need not send objectmap files along with the test scripts for reproducing the scenarios.

Hope you like the new version. We are working on a lookup strategy that allows you to share object maps among multiple testers. That is for the next release.

The post New features in MarathonITE 3.2.6 appeared first on GUI Test Automation for Java/Swing Applications With Marathon and MarathonITE.

Step by Step: Playing Scripts Using Test Runner

admin — Wed, 31 Oct 2012 06:12:40 +0000

» marathonite, marathon

Marathon’s Test Runner View provides a convenient way of executing tests. You can use this view to run all the tests or a selected set of tests. Due to historical reasons (and to show the origin of inspiration), the view is labeled JUnit.

Follow the steps given below to use the Test Runner View.

Steps

Step One: Open the Test Runner View.
Step Two: Play all the Test Cases.
Step Three: Check the Report.
Step Four: Play Selected Test Cases.

Step One: Open the Test Runner View.

From the tabs displayed in the left pane of the Main window, select the JUnit tab.

Test Runner View is displayed. The Test Hierarchy tab displays all the tests in a tree structure. Each sub directory of the Test Cases folder is presented as a test suite. The data driven tests are also displayed as a suite and a test for each record of the data file.

Marathon only displays the saved scripts. None of the unsaved buffers in the editors will be displayed in the Test Runner view.

Step Two: Play all the Test Cases.

In the Test Runner View click on the Run all tests button.

Marathon executes all the test scripts. The progress is shown as a progress bar in the Test Runner View. The progress bar turns red if any of the test scripts fails. Below the progress bar Marathon displays the statistics – number of tests, errors and failures.

Step Three: Check the Report.

Select the Failures tab to display the failed tests.

From this view, you can see the stack trace for the failed tests. Select a test in the view to display the trace for the failed test. Marathon distinguishes between errors and failures. Errors are similar to exceptions where the test script stops execution. The failures are, in general, the failed assertions. When the tests are run in batch mode, the first failure/error stops the test script.

You can use Next Failure and Previous Failure buttons to navigate through the failed tests. Double clicking a test script, opens the corresponding test in the editor. Use the Test Report button to display the HTML report for the current run in your browser.

Step Four: Play Selected Test Cases.

From the Test Runner View you can also execute partial set of tests. Select the tests from the Test Hierarchy tree and click on Play Selected Test button.

Marathon creates a temporary suite of the selected tests and executes them.

The post Step by Step: Playing Scripts Using Test Runner appeared first on GUI Test Automation for Java/Swing Applications With Marathon and MarathonITE.

Step by Step: Playing the Test Script

admin — Fri, 26 Oct 2012 06:36:57 +0000

» marathonite, marathon

Marathon and MarathonITE provides multiple ways to run the test scripts. The easiest way is to run a test from the editor itself.

Follow the steps given below to run a test script from the editor.

Steps

Step One: Choose Report Generation Option.
Step Two: Play the Test Script.
Step Three: Check the Results.
Step Four: Check the Script Output.

Step One: Choose Report Generation Option.

Select a test script from the Navigator window by double clicking it. Use «Marathon» → «Generate Reports» menu option to enable or disable the generation of reports.

When reports are enabled, Marathon store all reports under Test Reports folder. Each run of Test Script creates a new report in this folder. Click on the Show report for last test run button to open the report in the browser.

Step Two: Play the Test Script.

Click on Play the testcase button from the toolbar or select «Marathon» → «Play» from the menu bar or press ‘Ctrl+P’ from the keyboard. You can also choose to play a test case with a delay between actions by choosing Play the test case with a delay button or «Marathon» → «Slow Play» menu options or Ctrl+Shift+P.

Marathon launches the AUT using the fixture defined in the test and runs the test. You can observe that the highlighted line moves while the test is running.

Step Three: Check the Results.

Select the Results tab in the bottom pane to show the errors and failures occurred when a test script is run from the editor.

Results tab contains a table that shows the errors and failures occurred when a test script is run from the editor. Each row shows the message, file name and line number of the error. Double clicking on a row opens the file and positions the cursor at the line where the error occurred.

Results view toolbar provides couple of actions.

Show message: displays the complete error message in a window.
Clear: Clear the contents of the results view.

Step Four: Check the Script Output.

Select the Output to display the output from the script/AUT while the test is executed.

Different font styles and colors are used to distinguish the output from AUT and the script run-time.

The Output view toolbar provides couple of actions.

Clear: Clear the contents of the output view.
Export: Allows to save the output contents into a text file.

The post Step by Step: Playing the Test Script appeared first on GUI Test Automation for Java/Swing Applications With Marathon and MarathonITE.

Step by Step: Recording a Test Script

admin — Mon, 22 Oct 2012 07:37:08 +0000

» marathonite,marathon

Marathon and MarathonITE include a recorder that is used to record test scripts. Even when you want to manually create a script, it is best to start with a recorded script to ensure that all accessed components are available in the object map.

Here are the steps to follow for recording a test script for both Marathon and MarathonITE.

Steps

Step One: Create a New Test Case.
Step Two: Start Recording the Script.
Step Three: Perform Actions on the AUT.
Step Four: Open Assertions Dialog.
Step Five: Add Assertions.
Step Six: Stop Recording.

Step One: Create a New Test Case.

After launching Marathon, create a new test case by clicking Create a new testcase button from the toolbar or select «File» → «New» → «New Testcase» from menu bar. You can also press ‘Ctrl+N’ from the keyboard for creating a new test script.

Marathon creates a new test script and opens it in a new tab in the editing area.

Step Two: Start Recording the Script.

Click the Start recording button from the task bar or select «Marathon» → «Record» from the menu bar or press ‘Ctrl+R’ from the keyboard to start recording.

Marathon main window is minimized and Marathon Control Center window is displayed. Your Application Under Test (AUT) is also launched using the current fixture.

Step Three: Perform Actions on the AUT.

Perform some operations on the AUT.

Marathon records each operation as a script statement and the control center window displays last few recorded operations.

For most components, Marathon records the state of a component after the component loses focus. So a if you enter some text into a text field, Marathon records the select statement after you select another component. For tree, lists and tables Marathon records the last selected items only after you click outside the component.

Step Four: Open Assertions Dialog.

To insert assertions, ‘Ctrl+RightClick’ from mouse, by keeping the pointer on the component of your choice in the AUT. You can also use Ctrl+F8 keystroke while the component has the focus to open the assertion dialog.

Marathon opens the Assertions dialog with different tabs and the title of this window displays the name of the component. MarathonITE also displays a ObjectMap tab through which you can change the name/recognition properties of a component. The selected component is shown with a different background/border on the AUT window.

While the Assertions dialog is open, you can select a different component on the active AUT window. The contents of the Assertions dialog are changed to reflect your selection.

Step Five: Add Assertions.

Insert assertion by double clicking on a property or select a property and click on ‘Insert Assertion’ button. You can also insert a wait statement by selecting a property and clicking the ‘Insert Wait’ button. The wait statement is useful for making the Script to pause while some background processing is happening with the AUT.

Step Six: Stop Recording.

Once you complete recording, click on the Stop recording button from the control center window.

Marathon stops the recording, main window is restored and the editor will contain the recorded script.

The post Step by Step: Recording a Test Script appeared first on GUI Test Automation for Java/Swing Applications With Marathon and MarathonITE.

GUI Test Automation for Java/Swing Applications With Marathon and MarathonITEGUI Test Automation for Java/Swing Applications With Marathon and MarathonITE | Marathon

Released: Marathon and MarathonITE 3.3.2

Marathon and MarathonITE 3.2.9.2 release

Java7 and HeavyWeightWindow

MarathonITE 3.2.9 is released with object map sharing support

Step by Step: Using ObjectMap (enhanced) with test devlopment mode

Steps

Step One: Start MarathonITE.

Step Two: Configure Project tab.

Step Three: Select Test Development Mode.

Step Four: Configure Application tab.

Step Five: Select the Enhanced Object Map Lookup Strategy.

Step Six: Select a Scripting Language.

Step Seven: Save the Project Settings.

Step Eight: Check for a Log Messages.

Step Nine: Check for the Description and Suggestion.

Step Ten: Select the Object Map Editor.

Step Eleven: Modify the Object Map entry for the Component.

Step Twelve: Create a New Fixture(If needed).

Step Thirteen: Select a object lookup strategy.

Step by Step: Selecting Object Lookup Strategies

Steps

Step One: Start MarathonITE.

Step Two: Configure Project tab.

Step Three: Configure Application tab.

Step Four: Select a object lookup strategy.

Step Five: Select a Scripting Language.

Step Six: Save the Project Settings.

Step Seven: Create a New Fixture(If needed).

Step Eight: Select a object lookup strategy.

Step by Step: Creating a Project with Web Start Offline Launcher

Steps

Step One: Start MarathonITE.

Step Two: Configure Project tab.

Step Three: Configure Application tab.

Step Four: Select a object lookup strategy.

Step Five: Select a Scripting Language.

Step Six: Save the Project Settings.

New features in MarathonITE 3.2.6

Step by Step: Playing Scripts Using Test Runner

Steps

Step One: Open the Test Runner View.

Step Two: Play all the Test Cases.

Step Three: Check the Report.

Step Four: Play Selected Test Cases.

Step by Step: Playing the Test Script

Steps

Step One: Choose Report Generation Option.

Step Two: Play the Test Script.

Step Three: Check the Results.

Step Four: Check the Script Output.

Step by Step: Recording a Test Script

Steps

Step One: Create a New Test Case.

Step Two: Start Recording the Script.

Step Three: Perform Actions on the AUT.

Step Four: Open Assertions Dialog.

Step Five: Add Assertions.

Step Six: Stop Recording.