From fa967407e5ae7c379d8d82ff5f22c3d92e3bd1d8 Mon Sep 17 00:00:00 2001
From: Pascal Birchler <pascalb@google.com>
Date: Mon, 17 Jul 2023 13:07:56 +0200
Subject: [PATCH] Fix tests (#72)

Looks like one of the providers used in #71 changed their oEmbed output since then.
---
 features/fetch.feature | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/features/fetch.feature b/features/fetch.feature
index 4260176..a522301 100644
--- a/features/fetch.feature
+++ b/features/fetch.feature
@@ -54,7 +54,7 @@ Feature: Manage oEmbed cache.
 
     # Unknown provider requiring discovery but not returning iframe so would be sanitized for WP >= 4.4 without 'skip-sanitization' option.
     # Old versions of WP_oEmbed can trigger PHP "Only variables should be passed by reference" notices on discover so use "try" to cater for these.
-    When I try `wp embed fetch https://view.ceros.com/ceros/new-experience-3/p/1 --skip-sanitization`
+    When I try `wp embed fetch https://app.ex.co/stories/item/8fb2343f-fa5d-48d4-8723-f8b5d51cc1a9 --skip-sanitization`
     Then the return code should be 0
     And STDERR should not contain:
       """
@@ -62,7 +62,7 @@ Feature: Manage oEmbed cache.
       """
     And STDOUT should contain:
       """
-      ceros.com/
+      app.ex.co/
       """
     And STDOUT should contain:
       """
@@ -72,14 +72,18 @@ Feature: Manage oEmbed cache.
       """
       <iframe
      """
+    And STDOUT should not contain:
+      """
+      <script
+     """
 
   # WP 4.9 always returns clickable link even for sanitized oEmbed responses.
   @require-wp-4.9
   Scenario: Get HTML embed code for a given URL that requires discovery and is sanitized
-    When I run `wp embed fetch https://view.ceros.com/ceros/new-experience-3/p/1`
+    When I run `wp embed fetch https://app.ex.co/stories/item/8fb2343f-fa5d-48d4-8723-f8b5d51cc1a9`
     Then STDOUT should contain:
       """
-      ceros.com/
+      app.ex.co/
       """
     And STDOUT should contain:
       """