Skip to content

Support params in provider_state (v3) #168

Closed
@jrmhaig

Description

@jrmhaig

The example on the README has a provider state of 'an alligator exists', which can be defined in the provider configuration with:

  provider_state 'an alligator exists' do
    ...
  end

Is there any way to use some form of pattern matching with provider_state so that a single block could be used for both 'an alligator called Tom exists' and 'an alligator called Jerry exists'?

I'm thinking of something similar to https://github.com/cucumber/cucumber/tree/master/cucumber-expressions

Metadata

Metadata

Assignees

No one assigned

    Labels

    v3pact v3 specification

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions