0.01
No commit activity in last 3 years
No release in over 3 years
There's a lot of open issues
LapisLazuli provides cucumber helper functions and scaffolding for easier (web) test automation suite development. A lot of functionality is aimed at dealing better with [Watir](http://watir.com/), such as: - Easier/more reliable find and wait functionality for detecting web page elements. - Easier browser handling - Better error handling - etc.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

>= 2.0
>= 12.3
>= 0.17

Runtime

>= 4.0
>= 3.1
>= 1.11
>= 5.11
>= 0.6
>= 0.5
>= 0.20
>= 6
 Project Readme

Lapis Lazuli

LapisLazuli provides cucumber helper functions and scaffolding for easier (web) test automation suite development.

Gem Version Code Climate Test Coverage

Tested with Cucumber 4, 5 & 6 For cucumber 2 and 3, have a look at the version 2 release of Lapis Lazuli.

A lot of functionality is aimed at dealing better with Watir, such as:

  • Easier/more reliable find and wait functionality for detecting web page elements.
  • Easier browser handling
  • Better error handling
  • etc.

Installation

For detailed installation notes, go to: http://www.testautomation.info/Installing_ruby_with_cucumber

Add this line to your application's Gemfile:

gem 'lapis_lazuli'

And then execute:

$ bundle

Or install it yourself as:

$ gem install lapis_lazuli

Usage

The Lapis Lazuli project has two main purposes:

  • Provide a repository of common test functions for test automation engineers.
  • Make it easy to get started on a test automation project with these test functions.

The first goal is fulfilled by the Lapis Lazuli module itself, which can be imported in any cucumber project like this:

require 'lapis_lazuli'
World(LapisLazuli)

All of Lapis Lazuli's helper functions will be available in your step definitions then. However, you won't need to do this if you create a new Lapis Lazuli project. Simple run:

$ lapis_lazuli create <projectpath>

And a cucumber project will be set up for you in the given path. The last path name component will be considered the project name, so e.g. a path of projects/for_client/website1 will mean the project's name is going to be website1.

Change to that newly created project directory and read the README.md file there for further instructions.

Be sure to read the GitHub Wiki or testautomation.info for further documentation.

Contributing

Please see the Wiki page on contributing

License

Copyright (c) 2013-2019 spriteCloud B.V. and other node-apinator contributors. See the LICENSE file for details.