Skip to content

Commit

Permalink
Update steps
Browse files Browse the repository at this point in the history
  • Loading branch information
Miraeld committed Sep 19, 2024
1 parent 3ed8cef commit c588e74
Showing 1 changed file with 8 additions and 7 deletions.
15 changes: 8 additions & 7 deletions src/features/ll-lcp.feature
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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

0 comments on commit c588e74

Please sign in to comment.