A Python module, that provides re-usable steps for testing web applications with the Gauge framework. Development on native app testing has only just started.

This is an extensible and flexible test-automation library for Gauge. It enables users with and without programming knowledge to create end-to-end test scenarios in Markdown syntax. Developers can still easily extend their test scenarios with custom code. Selenium and Appium are used to simulate user interaction with the browser. A wide range of platforms and browsers are supported. Tests can also be executed on devices and emulators in the SauceLabs cloud.

Find the documentation on all Gauge steps of this project in the overview:

Gauge Step Overview

This is a library for the Gauge framework, so Gauge+Python must be installed first.

• Install Python >= 3.10 on your platform and make it available in the $PATH
• Install Gauge and create a test project with Python

It is useful to understand the basic workings of Gauge first. The documentation is excellent.

• Install this module
• Find out the path to this module after installation:

  echo $( python -m site --user-site )/gauge_web_app_steps

• Add that path to the property STEP_IMPL_DIR inside the test project file env/default/python.properties. Paths to multiple modules are comma separated.
  Example on a Mac:

  STEP_IMPL_DIR = /Users/<user>/Library/Python/3.10/lib/python/site-packages/gauge_web_app_steps, step_impl
  

• Reload Visual Studio Code
• Write a new scenario in specs/example.spec. VSC offers auto-completion

This module can be installed from source:

cd path/to/gauge-web-app-steps
pip install --user .

Or the latest package can be downloaded and installed from PyPi:

pip install gauge-web-app-steps --user --upgrade

When coding on this project, unit tests can be executed like this:

TEST_SKIP_IT=1 python -m unittest discover -v -s tests/ -p 'test_*.py'

Contributions are welcome.

Some known inter-operability issues can be found on the troubleshooting page. If things don't work immediately, a solution might already be documented there.

The Configuration follows the Gauge configuration approach. A lot of behaviour, including the browsers and devices to use for the tests, can be determined with properties.

Configuration Overview

Step parameters allow the use of placeholders, that can be defined in the Gauge environment properties files. Some steps also allow to set a placeholder value manually. Property keys act as placeholders, they are defined like ${key}. They will be replaced by its value if such a property key/value pair exists in any env/*/*.properties file or within the execution scope.

Mathematical expressions can also be evaluated. For example: #{5 + 5 * 5} is evaluated to 30.

It is possible to combine the two features. Placeholder substitution takes place before mathematical expression evaluation.

Functional expressions will generate a result during step execution. There are 2 expressions: One will generate a UUID, and the other will yield the current date and time: !{uuid}, !{time}, !{time:%Y-%m-%d}. The time format is optional, if omitted ISO format will be used. The time format pattern is described in the Python language documentation.

Note that the property expressions start with $, mathematical expressions with #, and functional expressions with !.

* Open "${homepage_url}/home"

* Assert "id" = "sum" equals "#{5 + 6}"

* Assert "id" = "sum" equals "#{$addend + 5 * 5}"

* Type "!{uuid}"

* Type "!{time}"

* Type "!{time:%Y-%m-%d}"

The property "homepage_url" can be defined in env/default/test.properties like this:

homepage_url = https://my-app.net

It is also possible to define a property in a step:

* Save placeholder "addend" = "5"

Maintainers