Skip to content
Go to file
Cannot retrieve contributors at this time
222 lines (170 sloc) 12.4 KB


Gwen Web Automation

A dynamic interpreter that enables teams to quickly automate front end web tests and repetitive online processes with Gherkin feature specifications. A web DSL interacts with Selenium under the covers for you so you don't have to do any of that programming or technical development work. All the standard Selenium locators are supported and you can additionally inject JavaScript in places where dynamically finding elements or running functions on web pages may be necessary.

Home | Get Started | DSL | Settings | Blog | Wiki | FAQ | License | Support | Twitter

Current Status

Build Status GitHub All Releases

What's New?

Why Gwen?

So you can drive web based tests and online processes with declarative Gherkin feature specs that describe behavior ..

 Feature: Google search

Scenario: Lucky Google search
    Given I have Google in my browser
     When I do a search for "Gwen automation"
     Then I should find a Gwen page

.. by defining locators and step definitions in separate and imperative Gherkin meta specs that describe automation ..

 Feature: Google search meta (automation glue)

Scenario: I have Google in my browser
    Given I start a new browser
     When I navigate to ""
     Then the page title should be "Google"

Scenario: I do a search for "<query>"
    Given the search field can be located by name "q"
     When I enter "$<query>" in the search field
     Then the page title should contain "$<query>"

Scenario: I should find a Gwen page
    Given link 1 can be located by css selector ".rc a"
     When I click link 1
     Then the current URL should match regex ".+[G|g]wen.*"

.. without having to develop any framework, page objects or Selenium code.

How it Works

Meta features are the automation glue in Gwen and they are defined in Gherkin too. They define locators and step definitions that are matched against steps in features to locate elements and perform browser operations using the Gwen web DSL. @StepDef annotated scenarios in meta are loaded into memory when Gwen is launched and bound to steps in features by name to achieve execution at runtime. So your features remain clean and free of automation clutter.

Key Features

  • Behavour driven automation
    • Declarative features describe behavior
    • Imperative Meta features describe automation
    • Gwen binds the two at runtime to drive automation
  • A prescribed Web DSL performs all browser interactions for you
  • Automation across browsers and platforms is consistent (Chrome, Firefox, Safari, Edge and IE)
  • An interactive REPL console provides a step by step execution environment

Get Started

System Requirements

  • Linux, Mac or Windows OS
  • Chrome, Firefox, Safari, Edge or IE web browser
  • Java JRE or JDK 8 (version 1.8) or higher
    • You can verify that you have Java installed by opening a command prompt and typing java -version. A version will be displayed if you have Java installed.
    • Install Java if you do not see a version displayed

Install Gwen and Go!

Ensure that your system meets the above requirements and then perform the following:

  1. Download and extract into to a folder on your computer
  2. Start automating

Learn More

User Network and Support

Join our user network at Gwenify to get access to the community and company level chat and support for your workplace.


Copyright 2014-2020 Brady Wood, Branko Juric and Gwen contributors.

This software is open sourced under the Apache License, Version 2.0.

See also: LICENSE.

This project has dependencies on Gwen and other open source projects. All distributed third party dependencies and their licenses are listed in the LICENSE-THIRDPARTY file.

Open sourced 28 June 2014 03:27 pm AEST


New capabilities, improvements, fixes, and documentation are all welcomed candidates for contribution. Each submission is reviewed and verified by the project maintainers before being integrated and released to the community. We ask that all code submissions include unit tests or sample test features providing relevant coverage.

By submitting contributions, you agree to release your work under the license that covers this software.

How to Contribute

  1. Fork this repository
  2. Create a branch on your forked repository
  3. Commit your changes to your branch
  4. Push your branch to your forked repository
  5. Create a pull request from your branch to here



We thank the following contributors and active users for helping to make Gwen better. You are all awesome!

The following contributors submitted pull requests that have been merged:

The following users raised issues or requests that have been addressed:


Known Users


Integrates With

You can’t perform that action at this time.