Everybody can author a new question

JavaBlackBelt

Subscribe to JavaBlackBelt: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get JavaBlackBelt: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


JavaBlackBelt Authors: Sumith Kumar Puri, Duncan Thomas, Maureen O'Gara, Karthik Narayanan, Steve Beaty

Related Topics: RIA Developer's Journal, Java EE Journal, JavaBlackBelt, Sun Developer Journal, HP Virtualization Journal, Java Developer Magazine

Article

An Introduction to Abbot

A Friendly JUnit Extension for GUI Testing

  • The script editor will be used to create the test cases. Costello, the script editor, can be started by:

    java -jar lib/abbot.jar

    Once the GUI is running, the first step is to create a new script (File->New Script). Each script has a launch line that specifies the method (containing the GUI) to be tested. The launch line is edited with the information that can launch the GUI. The launch information requires the method name, arguments for the method, class information, and the classpath (see Figure 2).

    method="main"
    args="[]"
    class="CelsiusConverter"
    classpath="src/demo"

    Note that the XML test script example has the same information in the launch tag.

    With the launch information in place, the GUI can be launched (Test->Launch). This will prepare the framework to record user actions. To record user actions, press F2 (Capture->All Actions). With this step we can record the first case, which inputs a positive number, and then press convert.

    Once the user interactions have been captured, we can move the actions out of the sequence block for better readability. With the script looking the way we want, it's now time to add an assertion. To do this, we'll use the Hierarchy tab to navigate to the GUI component. Upon selection of the GUI component, the name-value pair to be validated can be selected and the Assert Property = Value button will add the assertion (see Figure 3).

    The other two test cases can be created similarly to form a test suite. The test cases can run within the JUnit test harness utilizing either the command line or the GUI test runner. The junit.extensions.abbot.ScriptFixture class is subclassed to create the CelsiusConverterTest.

    public class CelsiusConverterTest
    extends ScriptFixture

    The junit.extensions.abbot.ScriptTestSuite class is used to autogenerate a suite based on test scripts matching a certain criteria. In this case, all scripts residing in a particular directory will be used. The test ScriptTestSuite class is subclassed from the junit.Framework.TestSuite class.

    public static Test suite() {
    return new ScriptTestSuite
    (CelsiusConverterTest.class,
    "src\demo\scripts\CelsiusConverter");
    }

    The main method of the CelsiusConverterTest class invokes the JUnit test runners.

    public static void main(String[] args){
    args = Log.init(args);
    String[] names = {
    CelsiusConverterTest.class.getName()
    };
    if (args.length == 1 &&
    args[0].equals("--gui"))
    junit.swingui.TestRunner.main(names);
    else
    junit.textui.TestRunner.main(names);
    }

    This approach facilitates the creation of a variety of user interaction scenarios that can be easily integrated with JUnit. Another interesting and handy feature is the ability to insert existing scripts into another script. Some high-level GUI tasks can be broken down into smaller tasks. In these cases, I've created scripts for the most granular tasks and then created different interaction scenarios by inserting the scripts for different tasks in a different order or by adding additional user interactions in between the tasks. Since the scripts are XML-based, they're very easy to read and they help in rapidly generating different scenarios.

  • More Stories By Satadip Dutta

    Satadip Dutta is a software architect at Hewlett-Packard (http://devresource.hp.com) and has been programming in Java since 1997. His areas of interest include distributed software architecture, Web services, and user interface design. Satadip holds an MS in Computer Science from Virginia Tech.

    Comments (7) View Comments

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


    Most Recent Comments
    Ashwath 01/18/05 02:34:16 AM EST

    I tried to run the code that u haven for 'GUI already exista' scenario. But it doen't work.. give me some eg.s

    tlroche 08/22/03 10:05:14 PM EDT

    "Abbot for SWT" (project name=abbotforswt) is an Eclipse plugin
    which seeks to extend Abbot ... for SWT (but you guessed :-) It is
    currently available only from the IIOSB (a "walled garden" version of
    SourceForge inaccessible outside IBM) @

    https://w3.opensource.ibm.com/projects/abbotforswt/

    (IIOSB residence is intended to be temporary. We are currently in IBM
    Open Source Steering Committee pre-review, and therefore hope to
    contribute our extensions back to Abbot sometime this millenium :-)
    For more detail, including

    * how abbotforswt extends j.a.Robot and Abbot

    * abbotforswt vs blackbox tools (e.g. RobotJ/XDE Tester)

    * related Eclipse 3.0 plan items

    see the (currently rather crude) abbotforswt homepage

    To demonstrate abbotforswt's feasibility, we have taken scenario 2
    from the JDJ article above, recoded its SUT (a dialog) in SWT, and
    designed and implemented an API targeting SWT equivalent to Abbot's
    existing API targeting AWT/Swing. For more details, see our release
    notes.

    Sound interesting? Try it out! However, first:

    <required type="legalese">

    If you are an IBMer and have NOT already completed your "OSPG
    training," please read the Open Source Participation Guidelines
    before you check out any code.

    </required>

    You have 2 installation options. Instructions are for Eclipse/
    WebSphere Studio users:

    0 Install the release zip. Goto our release page

    read the "IMPORTANT NOTICE", then follow the instructions in the
    release notes

    Note that you need not register for IIOSB to get the release, but we
    hope you will, because you're a fine human being. (Apologies for
    speciesism to all the fine non-human programmers out there :-)

    1 Install from CVS. This is a good first step toward becoming an
    abbotforswt contributor!

    - Run your development workbench (devbench) with either Target
    Platform pointing to a WSAD build (which is how I tested), or just
    import org.apache.xerces (should work, but not tested).

    - Create a new CVS repository location with

    host=cvs.opensource.ibm.com
    repository path=/cvs/abbotforswt
    user=anonymous
    no password
    connection type=pserver

    and check out HEAD/abbotforswt.

    - Browse to our release notes

    search or scroll to "run the demo"

    - Skip to step 4

    The demo can then be run in each of 3 ways, all of which are
    documented in the release notes:

    * using Test Collector in a launched WebSphere Studio build

    * using pde.junit to launch an Eclipse or WS build

    * using Eclipse's JUnit to launch just the UI

    tlroche 08/22/03 09:55:08 PM EDT

    "Abbot for SWT" (project name=abbotforswt) is an Eclipse plugin which seeks to extend Abbot ... for SWT (but you guessed :-) It is currently available only from the IIOSB (a "walled garden" version of SourceForge inaccessible outside IBM) @

    https://w3.opensource.ibm.com/projects/abbotforswt/

    (IIOSB residence is intended to be temporary. We are currently in IBM Open Source Steering Committee pre-review, and therefore hope to contribute our extensions back to Abbot sometime this millenium :-) For more detail, including

    * how abbotforswt extends j.a.Robot and Abbot

    * abbotforswt vs blackbox tools (e.g. RobotJ/XDE Tester)

    * related Eclipse 3.0 plan items

    see the (currently rather crude) abbotforswt homepage

    http://w3.opensource.ibm.com/~abbotforswt/

    To demonstrate abbotforswt's feasibility, we have taken scenario 2 from the JDJ article above, recoded its SUT (a dialog) in SWT, and designed and implemented an API targeting SWT equivalent to Abbot's existing API targeting AWT/Swing. For more details, see our release notes @

    http://w3.opensource.ibm.com/project/shownotes.php?release_id=597

    Sound interesting? Try it out! However, first:

    If you are an IBMer and have NOT already completed your "OSPG training," please read the Open Source Participation Guidelines

    http://ltc.linux.ibm.com/open_source/ospg.html

    before you check out any code.

    You have 2 installation options. Instructions are for Eclipse/ WebSphere Studio users:

    0 Install the release zip. Goto our release page

    http://w3.opensource.ibm.com/project/showfiles.php?group_id=1023

    read the "IMPORTANT NOTICE", then follow the instructions in the release notes

    http://w3.opensource.ibm.com/project/shownotes.php?release_id=597

    Note that you need not register for IIOSB to get the release, but we hope you will, because you're a fine human being. (Apologies for speciesism to all the fine non-human programmers

    http://www.newtechusa.com/PPI/pressroom.asp#higher

    out there :-)

    1 Install from CVS. This is a good first step toward becoming an abbotforswt contributor!

    - Run your development workbench (devbench) with either Target Platform pointing to a WSAD build (which is how I tested), or just import org.apache.xerces (should work, but not tested).

    - Create a new CVS repository location with

    host=cvs.opensource.ibm.com
    repository path=/cvs/abbotforswt
    user=anonymous
    no password
    connection type=pserver

    and check out HEAD/abbotforswt.

    - Browse to our release notes

    http://w3.opensource.ibm.com/project/shownotes.php?release_id=597

    search or scroll to "run the demo"

    - Skip to step 4

    The demo can then be run in each of 3 ways, all of which are documented in the release notes:

    * using Test Collector in a launched WebSphere Studio build

    * using pde.junit to launch an Eclipse or WS build

    * using Eclipse's JUnit to launch just the UI

    tlroche 08/22/03 09:51:39 PM EDT

    "Abbot for SWT" (project name=abbotforswt) is an Eclipse plugin which seeks to extend Abbot ... for SWT (but you guessed :-) It is currently available only from the IIOSB (a "walled garden" version of SourceForge inaccessible outside IBM) @

    https://w3.opensource.ibm.com/projects/abbotforswt/

    (IIOSB residence is intended to be temporary. We are currently in IBM Open Source Steering Committee pre-review, and therefore hope to contribute our extensions back to Abbot sometime this millenium :-) For more detail, including

    * how abbotforswt extends j.a.Robot and Abbot

    * abbotforswt vs blackbox tools (e.g. RobotJ/XDE Tester)

    * related Eclipse 3.0 plan items

    see the (currently rather crude) abbotforswt homepage

    http://w3.opensource.ibm.com/~abbotforswt/

    To demonstrate abbotforswt's feasibility, we have taken scenario 2 from the JDJ article above, recoded its SUT (a dialog) in SWT, and designed and implemented an API targeting SWT equivalent to Abbot's existing API targeting AWT/Swing. For more details, see our release notes @

    http://w3.opensource.ibm.com/project/shownotes.php?release_id=597

    Sound interesting? Try it out! However, first:

    If you are an IBMer and have NOT already completed your "OSPG training," please read the Open Source Participation Guidelines

    http://ltc.linux.ibm.com/open_source/ospg.html

    before you check out any code.

    You have 2 installation options. Instructions are for Eclipse/ WebSphere Studio users:

    0 Install the release zip. Goto our release page

    http://w3.opensource.ibm.com/project/showfiles.php?group_id=1023

    read the "IMPORTANT NOTICE", then follow the instructions in the release notes

    http://w3.opensource.ibm.com/project/shownotes.php?release_id=597

    Note that you need not register for IIOSB to get the release, but we hope you will, because you're a fine human being. (Apologies for speciesism to all the fine non-human programmers

    http://www.newtechusa.com/PPI/pressroom.asp#higher

    out there :-)

    1 Install from CVS. This is a good first step toward becoming an abbotforswt contributor!

    - Run your development workbench (devbench) with either Target Platform pointing to a WSAD build (which is how I tested), or just import org.apache.xerces (should work, but not tested).

    - Create a new CVS repository location with

    host=cvs.opensource.ibm.com
    repository path=/cvs/abbotforswt
    user=anonymous
    no password
    connection type=pserver

    and check out HEAD/abbotforswt.

    - Browse to our release notes

    http://w3.opensource.ibm.com/project/shownotes.php?release_id=597

    search or scroll to "run the demo"

    - Skip to step 4

    The demo can then be run in each of 3 ways, all of which are documented in the release notes:

    * using Test Collector in a launched WebSphere Studio build

    * using pde.junit to launch an Eclipse or WS build

    * using Eclipse's JUnit to launch just the UI

    Jeff 04/29/03 08:26:00 PM EDT

    I believe this is a forum in which comments need to be made about the article and its vaildity.

    The above messages should be in English and any concerns/comments should be made available for the benefit for all in the community

    Bhojohori Manna 04/29/03 06:00:00 AM EDT

    Chee chee, Ei rokom gala gali dile hobe.Dada koto bhalo article likheche.

    Utgandu 04/29/03 05:54:00 AM EDT

    Dada,ei jinis poisa diye keu porbe bhebechen apni?USa te theke apnio sobar moto boka patha hoye gechen .Apni ei jinista kotha theke chotha korechen?Ar apni ki GUI Master ke chenen???jobab chai,jobab dao.