diff --git a/src/features/ll-css-bg-image-double-colon.feature b/src/features/ll-css-bg-image-double-colon.feature index d79326e..2408209 100644 --- a/src/features/ll-css-bg-image-double-colon.feature +++ b/src/features/ll-css-bg-image-double-colon.feature @@ -8,6 +8,7 @@ Feature: C14626 - Should lazyload CSS background images inside internal, and ext And I save settings 'media' 'lazyloadCssBgImg' Scenario: Open the page template and compare to nowprocket + Given visual regression reference is generated Then I must not see any visual regression 'doubleColon' Then I must not see any error in debug.log When I log out diff --git a/src/features/ll-css-bg-image-elementor.feature b/src/features/ll-css-bg-image-elementor.feature index e22defd..17f44e2 100644 --- a/src/features/ll-css-bg-image-elementor.feature +++ b/src/features/ll-css-bg-image-elementor.feature @@ -2,7 +2,8 @@ Feature: C14412 - Should be compatible with Elementor background Scenario: Enable LL BG Images and check page template - Given I am logged in + Given visual regression reference is generated + And I am logged in And plugin is installed 'new_release' And plugin is activated When I go to 'wp-admin/options-general.php?page=wprocket#dashboard' diff --git a/src/features/ll-css-bg-image-fallback-js-disabled.feature b/src/features/ll-css-bg-image-fallback-js-disabled.feature index 0b48568..7d5c015 100644 --- a/src/features/ll-css-bg-image-fallback-js-disabled.feature +++ b/src/features/ll-css-bg-image-fallback-js-disabled.feature @@ -2,7 +2,8 @@ Feature: C13977 - Should have a fallback for browsers where JavaScript is disabled Scenario: Open the page template and compare to nowprocket with javascript disabled - Given I am logged in + Given visual regression reference is generated + And I am logged in And plugin is installed 'new_release' And plugin is activated When I go to 'wp-admin/options-general.php?page=wprocket#dashboard' diff --git a/src/features/ll-css-bg-image-single-colon.feature b/src/features/ll-css-bg-image-single-colon.feature index f95cef3..1eec6cb 100644 --- a/src/features/ll-css-bg-image-single-colon.feature +++ b/src/features/ll-css-bg-image-single-colon.feature @@ -8,6 +8,7 @@ Feature: C14626 - Should lazyload CSS background images inside internal, and ext And I save settings 'media' 'lazyloadCssBgImg' Scenario: Open the page template and compare to nowprocket + Given visual regression reference is generated Then I must not see any visual regression 'singleColon' Then I must not see any error in debug.log When I log out diff --git a/src/features/ll-css-bg-image.feature b/src/features/ll-css-bg-image.feature index df01076..fcde9d7 100644 --- a/src/features/ll-css-bg-image.feature +++ b/src/features/ll-css-bg-image.feature @@ -8,6 +8,7 @@ Feature: C13969 - Should lazyload CSS background images inside internal, and ext And I save settings 'media' 'lazyloadCssBgImg' Scenario: Open the page template and compare to nowprocket + Given visual regression reference is generated Then I must not see any visual regression 'llcss' Then I must not see any error in debug.log When I log out diff --git a/src/features/lrc-visual-regression.feature b/src/features/lrc-visual-regression.feature index 1ea206a..31758d5 100644 --- a/src/features/lrc-visual-regression.feature +++ b/src/features/lrc-visual-regression.feature @@ -8,6 +8,7 @@ Feature: LRC Visual Regression Test on Live Template And I go to 'wp-admin/options-general.php?page=wprocket#dashboard' Scenario: Shouldn't have any visual regression when visiting + Given visual regression reference is generated When I log out And I visit scenario urls And I am logged in