Skip to content

Fix Gherkin lint issues #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
swissspidy merged 1 commit into from
Apr 2, 2025
Merged

Fix Gherkin lint issues #80

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion features/fetch.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
Feature: Manage oEmbed cache.
Feature: Manage oEmbed fetch.

Background:
Given a WP install
Expand Down
4 changes: 2 additions & 2 deletions features/provider.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ Feature: Manage oEmbed providers.
"""
http://example.com/api/oembed.{format}
"""
Then STDOUT should not contain:
And STDOUT should not contain:
"""
http://example.com/*
"""
Expand Down Expand Up @@ -198,7 +198,7 @@ Feature: Manage oEmbed providers.
@require-wp-4.0
Scenario: Discover a provider with limited response size
When I run `wp embed provider match https://audio.com/audio-com/collections/ambient-focus`
And save STDOUT as {DEFAULT_STDOUT}
Then save STDOUT as {DEFAULT_STDOUT}

# Response limit too small
When I try `wp embed provider match https://audio.com/audio-com/collections/ambient-focus --limit-response-size=10`
Expand Down