Automated browser tests for web applications. Similar to Ruby's Capybara.
Switch branches/tags
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
bin
spec
src
vendor
.editorconfig
.gitignore
.travis.yml
LICENSE
README.md
shard.yml

README.md

LuckyFlow

LuckyFlow is a library for testing user flows in the browser. It is similar to Ruby's Capybara.

LuckyFlow example

Installation in Lucky projects

LuckyFlow is already installed and configured. Check out the guides to see how to use it: https://luckyframework.org/guides/browser-tests/

Installation in other Crystal projects

Add this to your application's shard.yml:

development_dependencies:
  lucky_flow:
    github: luckyframework/lucky_flow

Configure LuckyFlow in spec/spec_helper.cr:

require "lucky_flow"

LuckyFlow.configure do
  # This is required
  settings.base_uri = "http://localhost:<port>"

  # Optional settings. Defaults are shown here
  settings.retry_delay = 10.milliseconds
  settings.stop_retrying_after = 1.second
  settings.screenshot_directory = "./tmp/screenshots"
end

# Put this at the bottom of the file.
# If a required setting is missing, this will catch it.
Habitat.raise_if_missing_settings!

Then view the guides: https://luckyframework.org/guides/browser-tests/

You should be ready to go!

Usage

Note that you can only pass string paths to visit since only Lucky has route helpers described in the guide below. Example: visit "/my-path"

View guide at: https://luckyframework.org/guides/browser-tests/

Contributing

  1. Fork it ( https://github.com/luckyframework/lucky_flow/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Make your changes
  4. Run ./bin/test to run the specs, build shards, and check formatting
  5. Commit your changes (git commit -am 'Add some feature')
  6. Push to the branch (git push origin my-new-feature)
  7. Create a new Pull Request

Contributors