From c588e747f8358478fc9973a7924c4ee33cf46dac Mon Sep 17 00:00:00 2001 From: Gael Robin Date: Thu, 19 Sep 2024 21:41:50 +0200 Subject: [PATCH] Update steps --- src/features/ll-lcp.feature | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/src/features/ll-lcp.feature b/src/features/ll-lcp.feature index 527e340..de25c0a 100644 --- a/src/features/ll-lcp.feature +++ b/src/features/ll-lcp.feature @@ -8,10 +8,11 @@ Feature: Lazyload with LCP When I go to 'wp-admin/options-general.php?page=wprocket#dashboard' And I save settings 'media' 'lazyloadCssBgImg' -# Scenario: Should Exclude LCP/ATF from Lazyload -# Given I visit page '[TEMPLATE]' with browser dimension 1600 x 700 -# When I clear cache -# Then lcp image markup is not written to LL format + Scenario: Should Exclude LCP/ATF from Lazyload + Given I visit page 'lcp_with_imagify' with browser dimension 1600 x 700 + When I am logged in + And I clear cache + Then lcp image markup is not written to LL format # And ATF image markup is not written to LL format Scenario: Should exclude next-gen lcp/atf from LL @@ -20,8 +21,8 @@ Feature: Lazyload with LCP And I go to 'wp-admin/options-general.php?page=imagify' And I save imagify API key And display next-gen is enabled on imagify -# And page with images having next-gen avif, webp, avif/webp, no next gen is visited # I didn't get that +# And page 'lcp_with_imagify' with images having next-gen avif, webp, avif/webp, no next gen is visited # I didn't get that When I clear cache -# And I visit the page '[TEMPLATE]' with dimension 1600 x 700 -# Then lcp image markup is not written to LL format + And I visit page 'lcp_with_imagify' with browser dimension 1600 x 700 + Then lcp image markup is not written to LL format # And ATF image markup is not written to LL format