Skip to content
This repository has been archived by the owner on Sep 3, 2024. It is now read-only.
/ swing-back Public archive

A framework for automated testing swing-application using a PageObject pattern

License

Notifications You must be signed in to change notification settings

sbtqa/swing-back

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

74 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

English description | Описание на русском

Swing-back

Build Status GitHub release Maven Central

Swing-back it's a framework for automated testing swing-application using a PageObject pattern.

Documentation

Test example

There is example of using the swing-back with comments here

Loading and starting test application

There are several ways to load required application for testing via the swing-back.

Swing-back supports a loading from file system. This requires add a few properties into application.properties file witch are stored in classpath/config.

  • swingback.app.startclass = the full name of the main class your application (mandatory)

  • swingback.forms.package = full package path to package with forms

  • swingback.jvm.prop.systemProperty1 = value1 (optional)

    swingback.jvm.prop.systemProperty2 = value2

    swingback.jvm.prop.systemPropertyN = valueN

In this instance systemProperty1, systemProperty2, … systemPropertyN will be set in the jvm context in which the application will be ran.

With these parameters the required jars your application must be stored in a folder with path classpath/app/jars. All required resources for the test application must be stored in a classpath/app/resources folder.

If you want to specify a custom location with jars you should to add more parameters:

  • swingback.app.jars.path.abs = the absolute path to jars folder
  • swingback.app.resources.path.abs = the absolute path to resources folder

In this case swing-back will search the jars and resources in the folder specified folders.

Searching element on form

For finding form element use choosers. There are some choosers in priority order for easy to use.

  • ComponentChooserByName (determine element by name swing component.)

  • ComponentChooserByToolTip (determine element by tool tip swing component.)

  • ComponentChooserByText (determine element by text swing component.)

  • ComponentChooserByIndex (determine element by index among other components with the same type).

  • ComponentChooserByCoordinates (determine element by coordinates swing components.)

You can write yourself chooser by analogy.

Contacts

If you found error or you have a question? Check, maybe someone asked before, not found? Just create a new issue!

License

Page-Factory is released under the Apache 2.0. Details here.

About

A framework for automated testing swing-application using a PageObject pattern

Topics

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •