Repository navigation
Flaky audio provider tests #85
Copy link
Copy link
Closed
Labels
command:embed-provider-matchRelated to 'embed provider match' commandRelated to 'embed provider match' commandscope:testingRelated to testingRelated to testingstate:unconfirmed
Description
001 Scenario: Match an oEmbed provider # features/add-oembed-provider.feature:130
Then the return code should be 0 # features/add-oembed-provider.feature:142
$ wp embed provider match https://audio.com/audio-com/collections/ambient-focus
Error: No oEmbed provider found for given URL.
cwd: /tmp/wp-cli-test-run--698bf0335d1073.98861007/
run time: 0.38755297660828
exit status: 1 (RuntimeException)
002 Scenario: Discover a provider with limited response size # features/add-oembed-provider.feature:198
When I run `wp embed provider match https://audio.com/audio-com/collections/ambient-focus` # features/add-oembed-provider.feature:199
$ wp embed provider match https://audio.com/audio-com/collections/ambient-focus
Error: No oEmbed provider found for given URL.
cwd: /tmp/wp-cli-test-run--698bf035387a76.64233588/
run time: 0.39840817451477
exit status: 1 (RuntimeException)
003 Scenario: Only match an oEmbed provider if discover # features/add-oembed-provider.feature:245
Then the return code should be 0 # features/add-oembed-provider.feature:256
$ wp embed provider match https://audio.com/audio-com/collections/ambient-focus
Error: No oEmbed provider found for given URL.
cwd: /tmp/wp-cli-test-run--698bf035c7e016.36044166/
run time: 0.37659192085266
exit status: 1 (RuntimeException)
004 Scenario: Match an oEmbed provider # features/provider.feature:131
Then the return code should be 0 # features/provider.feature:143
$ wp embed provider match https://audio.com/audio-com/collections/ambient-focus
Error: No oEmbed provider found for given URL.
cwd: /tmp/wp-cli-test-run--698bf036b19877.74411875/
run time: 0.48289489746094
exit status: 1 (RuntimeException)
005 Scenario: Discover a provider with limited response size # features/provider.feature:199
When I run `wp embed provider match https://audio.com/audio-com/collections/ambient-focus` # features/provider.feature:200
$ wp embed provider match https://audio.com/audio-com/collections/ambient-focus
Error: No oEmbed provider found for given URL.
cwd: /tmp/wp-cli-test-run--698bf037b5d8e1.11950562/
run time: 0.39745402336121
exit status: 1 (RuntimeException)
006 Scenario: Only match an oEmbed provider if discover # features/provider.feature:246
Then the return code should be 0 # features/provider.feature:257
$ wp embed provider match https://audio.com/audio-com/collections/ambient-focus
Error: No oEmbed provider found for given URL.
cwd: /tmp/wp-cli-test-run--698bf038514275.81959407/
run time: 0.34361886978149
exit status: 1 (RuntimeException)
We should stabilize them and speed them up by using our request mocking util (Given that HTTP requests to ... will respond with)
Reacted by Copilot
Metadata
Metadata
Assignees
Labels
command:embed-provider-matchRelated to 'embed provider match' commandRelated to 'embed provider match' commandscope:testingRelated to testingRelated to testingstate:unconfirmed
Activity