Spreewald 1.0.0 released

Posted Almost 10 years ago. Visible to the public.

Spreewald now has a spreewald binary that lists all available steps, optionally filtering them. Example:

$> spreewald

# All Spreewald steps
Given I am on ...
... long list

$> spreewald check

# All Spreewald steps containing 'check'
When I check "..."
When I uncheck "..."
Then the "..." checkbox( within ...)? should be checked
Then the "..." checkbox( within ...)? should not be checked
Then the radio button "..." should( not)? be (checked|selected)
Dominik Schöler
makandra.de
Say thanks1
Last edit
Almost 10 years ago
License
Source code in this card is licensed under the MIT License.

Related cards:

Spreewald 4.3.3 released

Field error steps

Spreewald's The ... field should have an error and The ... field should have the error ... steps now have built-in support for Rails and Bootstrap (v3-v5) error classes. When using Bootstrap, it is no longer necessary to ...

Spreewald 1.1.0 released

Spreewald 1.1.0 drops the be_true and be_false matchers in order to be RSpec 3 and Ruby 2 compatible. For backward compatibility, these matchers are replaced with == true and == false.

[Note the slightly more changed semantics of the upda...

Spreewald version 0.9.4 released

  • "I click on ..." step fixed
  • Errors added to ToleranceForSeleniumSyncIssues::RETRY_ERRORS
    • Capybara::ElementNotFound
    • Selenium::WebDriver::Error::ElementNotVisibleError
    • Selenium::WebDriver::Error::NoSuchFrameError

Spreewald 1.2.0 released: new "select field should be sorted" step

Usage:

Then the "sorted" select should be sorted
But the "unsorted" select should not be sorted

Migrating to Spreewald

This describes how to migrate an existing cucumber test suite to Spreewald.

  1. Add the gem
  2. Include spreewald into your cucumber environment by putting
    require 'spree...

howto fix spreewald issue „database configuration does not specify adapter (ActiveRecord::AdapterNotSpecified)“

This error occurs when you already have a database.yml which defines the database for the cucumber environment instead of test. (Spreewald database.sample.yml has changed)

Fix

Change cucumber to test in your databse.yml

test: ...

Cucumber: Test that an element is not overshadowed by another element

I needed to make sure that an element is visible and not overshadowed by an element that has a higher z-index (like a modal overlay).

Here is the step I wanted:

Then the very important notice should not be overshadowed by another element
`...

Beware: Nested Spreewald patiently blocks are not patient

Note: The behaviour of Spreewald's within step is as described below for version < 1.9.0; For Spreewald >= 1.9.0 it is as described in Solution 1.

When doing integration testing with cucumber and selenium you will often encounter problems ...

Nested Spreewald patiently blocks are now patient

In Spreewald 1.10.4+, nested patiently blocks are now patient.

Here is an example:

patiently do
  outer_code
  patiently do
    inner_code
  end
end

On spreewald 1.11.2+ the inner block will wait for the full configured wait time ...

Spreewald 0.6.1 makes it easier to inspect form values

The new version of Spreewald makes it easier to inspect form values.

Testing the value of any type of input control

  • When the step `Then the "foo" field s...
Posted by Dominik Schöler to makandra dev (2014-07-09 19:27)
This website uses short-lived cookies to improve usability.
or learn more