Jemmy framework

Ultimate UI testing solution.

Overview

Here is a general Jemmy scheme at the time of creating this document. The scheme shows Jemmy library with the extentions as well as some of the products it is used for as a test tool.

Documentation index

Jemmy v2

Tutorial

Jemmy v3

Walk through

General

Recording vs. coding - our take on recording tools
Concept oriented testing - the way we design our libraries
Automation effectiveness - the formula

UI test.

UI test work-flow could be broken to three kinds of steps:

Find controls you need to do next action for
Do something with that control
Verify results of the action

Find and Do

First two parts should look something like this, then

Starting from some hierarchy root,
look for a control with certain characteristics,
and do something meaningful to it

Which, with Jemmy, looks like this

SomeHierarchyRoot.lookup(new SertainCharacteristics()).
as(SomeMeaningfulControlInterface.class).do();

Verify

Test could verify

UI feedback

Jemmy provides all the support for verifying this. Check documentation and samples for more info.

Some controls to appear

This comes back to component lookup.

Some controls properties to change

Again, either the lookup or waiting for a control property to be equal to something.

Image update

Use Jemmy image API.

Non-UI feedback

Well ... since the test is written in Java, there should not be any problem to implement any kind of check, is there? Just remember to wait for a result - do not verify it right away. You could use Jemmy waiting API for that.

File been created or updated
Database record created
Sun goes up :)

Old main mage located here

Main Menu