v2.1.1

Bug fixes

• Fixes handling of page URIs that are RegExp objects (#4)

v2.1.0

New functionality

• Automatic installer: The necessary glue files are created or edited, even if you have a customized Cypress installation or none at all. See the new installation process for details.

v2.0.0

Breaking changes

• Setting routes, custom steps, attribute names, and other options is simpler; see README
• data-force="true|false" attributes are now data-options="{ force: true|false }"
• Support for <input type="file"> has been dropped for now; use alternatives (one, two) instead
• Placeholder login & logout steps are no longer included and must be added as custom steps
• For the I set: step, the data table now requires column headers in the first row:

And I set:
| element        | value            |
| email input    | name@example.com |
| password input | password123      |

v1.3.0

New functionality

• Added data table support for element text equality and contains assertions (see example below)
• Added support for asserting input values (see example below)

Scenario: Input values can be set using inline data tables
---
Given I navigate to "input actions"
And I set:
| text input       | Text value     |
| password input   | Password value |
When I click "submit button"
Then "text input" should be "Text value"
Then "password input" should be "Password value"

• Added support for multi-selects
• Add ability to force click (ie. ignoring actionability) with the force attribute

Bug fixes

• New values replace existing values when setting text input values. Previously, the new value was appended to the existing value.

v1.2.0

New functionality

• You can now assert the current page by path string or regex, not just by name:

Then I should be on "/path/to/page.html"
Then I should be on "/.*\.html$/"

Bug fixes

• Setting file inputs now works correctly with multi-file inputs, eg. <input name="files" multiple>

v1.1.6

Bug fixes

• Radio and checkbox inputs can be selected by value. Previously only selection by a custom data value attribute was possible.

v1.1.5

Bug fixes

• Removes empty content check from {element} should be visible assertions