diff --git a/tests/features/varbase/README.md b/tests/features/varbase/README.md
index 3198334d5f40833482b9f0597aa09250020b6c0e..7ad4e565bc646e4cef24550eedd681231fc4c29c 100644
--- a/tests/features/varbase/README.md
+++ b/tests/features/varbase/README.md
@@ -23,10 +23,10 @@ initialization and cleaning up after the test.
```
-## [List of features in the step 1 init tests:](/tests/features/varbase/step1-init-tests/)
+## List of features in the step 1 init tests:
--------------------------------------------------------------------------------
-* [Feature: Create default testing users.](/tests/features/varbase/step1-init-tests/01-create-default-testing-users.feature)
+* Feature: Create default testing users
```
test_authenticated: { email: 'authenticated.test@vardot.com', password: 'dD.123123ddd' }
test_editor: { email: 'editor.test@vardot.com', password: 'dD.123123ddd' }
@@ -35,56 +35,60 @@ test_seo_admin: { email: 'seo.admin.test@vardot.com', password: 'dD.123123ddd' }
test_site_admin: { email: 'site.admin.test@vardot.com', password: 'dD.123123ddd' }
test_super_admin: { email: 'super.admin.test@vardot.com', password: 'dD.123123ddd' }
```
+* Feature: Add Arabic language if we do not have it to languages in the system
-* [Feature: Add Arabic language if we do not have it to languages in the system.](/tests/features/varbase/step1-init-tests/02-add-arabic.feature)
-
-## [List of Features in the step 2 apply tests:](/tests/features/varbase/step2-apply-tests/)
+## List of Features in the step 2 apply tests:
--------------------------------------------------------------------------------
-### [Website Base Requirements](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/)
-* [Feature: Website Base Requirements - User Registration - Only admins login](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-01-user-registration_only-admins-login.feature)
-* [Feature: Website Base Requirements - User Roles - Simple Roles](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-02-user-roles.feature)
-* [Feature: Website Base Requirements - Content Editing - Rich Text Editor - Input formats](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-03-input-formats.feature)
-* [Feature: Website Base Requirements - Website Languages - English](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-04-website-languages_english.feature)
-* [Feature: Website Base Requirements - Website Languages - All content translatable to all languages](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-05-translatable-content-types-to-all-languages.feature)
-* [Feature: Website Base Requirements - Content Editing - Rich Text Editor - Convert URLs into links](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-06-convert-urls-links.feature)
-
-### [User Management](/tests/features/varbase/step2-apply-tests/02-user-management/)
-* [Feature: User Management - Standard User Management - Request new password](/tests/features/varbase/step2-apply-tests/02-user-management/02-01-request-new-password.feature)
-* [Feature: User Management - Standard User Management - Admins can create users and assign a role to them](/tests/features/varbase/step2-apply-tests/02-user-management/02-02-admins-can-create-users-and-assign-role-them.feature)
-* [Feature: User Management - Standard User Management - Login](/tests/features/varbase/step2-apply-tests/02-user-management/02-03-user-login.feature)
-* [Feature: User Management - Have persistent login options and configurations.](/tests/features/varbase/step2-apply-tests/02-user-management/02-04-persistent-login.feature)
-* [Feature: User Management - Standard User Management - Have fine-grained access control of user administrators protections with specific user, or all users in a role.](/tests/features/varbase/step2-apply-tests/02-user-management/02-05-user-protect.feature)
-* [Feature: User Management - Standard User Management - Users with permission to assign roles may select which roles are available for assignment.](/tests/features/varbase/step2-apply-tests/02-user-management/02-06-role-assign.feature)
-
-### [Admin Management](/tests/features/varbase/step2-apply-tests/03-admin-management/)
-* [Feature: Admin management - Support Requirements - Standard Support Navigation - Allow site super administrators to switch users and surf the site as that user.](/tests/features/varbase/step2-apply-tests/03-admin-management/03-01-allows-site-administrators-to-masquerade-by-switching-users.feature)
-* [Feature: Admin management - Standard Back-End Navigation - Navigate through the Drupal admin with the keyboard for faster access](/tests/features/varbase/step2-apply-tests/03-admin-management/03-02-navigate-through-drupal-admin-keyboard.feature)
-* [Feature: Admin management - Standard User Management - Admins can disable users](/tests/features/varbase/step2-apply-tests/03-admin-management/03-03-admins-can-disable-users.feature)
-* [Feature: Admin management - Assets Management - Image media and their usage list page for site admins](/tests/features/varbase/step2-apply-tests/03-admin-management/03-04-image-media-and-their-usage-list-page-for-admins.feature)
-
-### [Content Structure](/tests/features/varbase/step2-apply-tests/04-content-structure/)
-* [Feature: Content Structure - Basic Page.](/tests/features/varbase/step2-apply-tests/04-content-structure/04-01-basic-page-permissions.feature)
-* [Feature: Content Structure - Landing Pages](/tests/features/varbase/step2-apply-tests/04-content-structure/04-02-landing-page-permissions.feature)
-* [Feature: Content Structure - Landing Pages - Add any paragraph types to the page.](/tests/features/varbase/step2-apply-tests/04-content-structure/04-03-landing-page_add-any-paragraph-type-to-the-page.feature)
-* [Feature: Content Structure - Content Structure - Landing Pages - Varbase text and image paragraphs.](/tests/features/varbase/step2-apply-tests/04-content-structure/04-04-landing-page_text-and-image-paragraphs.feature)
-* [Feature: Content Structure - Navigational Features - Breadcrumbs - Standard breadcrumbs](/tests/features/varbase/step2-apply-tests/04-content-structure/04-05-standard-bredcrumbs.feature)
-
-### [Content Management](/tests/features/varbase/step2-apply-tests/05-content-management/)
-* [Feature: Content Management - Add default [entityqueue] module testing content and configuration.](/tests/features/varbase/step2-apply-tests/04-content-structure/05-00-add-default-entityqueue-testing-content-and-config.feature)
-* [Feature: Content Management - Standard Entity Queue Management - Have the option to Reverse order in admin view.](/tests/features/varbase/step2-apply-tests/04-content-structure/05-01-entityqueue-reverse-order-in-admin-view.feature)
-* [Feature: Content Management - Standard Entity Queue Management - Have Entityqueue tab inside the full content page and be able to Add to a queue or Remove from a queue](/tests/features/varbase/step2-apply-tests/04-content-structure/05-02-entityqueue-tab-for-content-types.feature)
-* [Feature: Content Management - Add hero slider to entityqueue using entityqueue form widget.](/tests/features/varbase/step2-apply-tests/04-content-structure/05-03-add-hero-slider-to-entityqueue-using-entityqueue-form-widget.feature)
-* [Feature: Content Management - Cloning content and entities.](/tests/features/varbase/step2-apply-tests/04-content-structure/05-04-cloning-content-and-entities.feature)
-* [Feature: Content Management - Assets Management - Ability to embed existing media image library in the rich text editor](/tests/features/varbase/step2-apply-tests/04-content-structure/05-05-embed-existing-media-image-library.feature)
-* [Feature: Content Management - Content Editing - Rich Text Editor - Easy linking to internal content by searching for content by its titles](/tests/features/varbase/step2-apply-tests/04-content-structure/05-06-easy-linking-internal-content-searching-content-by-its-titles.feature)
-
-
-## [List of features in the step 3 cleanup tests:](/tests/features/varbase/step3-cleanup-tests/)
+### Website Base Requirements
+* Feature: Website Base Requirements - User Registration - Only admins login
+* Feature: Website Base Requirements - User Roles - Simple Roles
+* Feature: Content Editing - Rich Text Editor - Input formats
+* Feature: Website Base Requirements - Website Languages - English
+* Feature: Website Base Requirements - Website Languages - All content translatable to all languages
+* Feature: Content Editing - Rich Text Editor - Convert URLs into links
+
+### User Management
+* Feature: User Management - Standard User Management - Request new password
+* Feature: User Management - Standard User Management - Admins can create users and assign a role to them
+* Feature: User Management - Standard User Management - Login
+* Feature: User Management - Have persistent login options and configurations
+* Feature: User Management - Standard User Management - Have fine-grained access control of user administrators protections with specific user, or all users in a role
+* Feature: User Management - Standard User Management - Users with permission to assign roles may select which roles are available for assignment
+
+### Admin Management
+* Feature: Pre-check important administrator and development pages
+* Feature: Support Requirements - Standard Support Navigation - Allow site super administrators to switch users and surf the site as that user
+* Feature: Admin management - Standard Back-End Navigation - Navigate through the Drupal admin with the keyboard for faster access
+* Feature: User Management - Standard User Management - Admins can disable users
+* Feature: File & Media Management - Assets Management - Image media and their usage list page for site admins
+* Feature: Check JSON:API admin interface and services and Varbase API settings
+* Feature: Preview the site in a number of responsive devices
+
+### Content Structure
+* Feature: Content Structure - Basic Page
+* Feature: Content Structure - Landing Pages
+* Feature: Landing Pages - Add any paragraph types to the page
+* Feature: Content Structure - Landing Pages - Varbase text and image paragraphs
+* Feature: Navigational Features - Breadcrumbs - Standard breadcrumbs
+* Feature: Content Structure - Blog post
+
+### Content Management
+* Feature: Content Management - Add default [entityqueue] module testing content and configuration
+* Feature: Content Management - Standard Entity Queue Management - Have the option to Reverse order in admin view
+* Feature: Content Management - Standard Entity Queue Management - Have Entity queue tab inside the full content page and be able to Add to a queue or Remove from a queue
+* Feature: Content Management - Add hero slider to entity queue using entity queue form widget
+* Feature: Content Management - Cloning content and entities
+* Feature: File & Media Management - Assets Management - Ability to embed existing media image library in the rich text editor
+* Feature: Content Editing - Rich Text Editor - Easy linking to internal content by searching for content by its titles
+
+
+## List of features in the step 3 cleanup tests:
--------------------------------------------------------------------------------
-* [Feature: Delete default testing users.](/tests/features/varbase/step3-cleanup-tests/01-delete-default-testing-users.feature)
+
+* Feature: Delete default testing users
```
test_authenticated
test_editor
@@ -94,5 +98,6 @@ test_site_admin
test_super_admin
```
-* [Feature: Delete Arabic language from the system.](/tests/features/varbase/step3-cleanup-tests/02-delete-arabic.feature)
-* [Feature: Cleanup after [entityqueue] module tests.](/tests/features/varbase/step3-cleanup-tests/03-cleanup-after-entityqueue-tests.feature)
\ No newline at end of file
+* Feature: Delete Arabic language from the system
+* Feature: Cleanup after [entityqueue] module tests
+* Feature: Cleanup leftover media from the Media Library
diff --git a/tests/features/varbase/step1-init-tests/01-create-default-testing-users.feature b/tests/features/varbase/step1-init-tests/01-create-default-testing-users.feature
index 04944927de4ead5711c2b6631f0c64223a488ac7..e877ab9bff2efc8ea7528f29cd195b784ca538b0 100644
--- a/tests/features/varbase/step1-init-tests/01-create-default-testing-users.feature
+++ b/tests/features/varbase/step1-init-tests/01-create-default-testing-users.feature
@@ -1,4 +1,4 @@
-Feature: Create default testing users.
+Feature: Create default testing users
# test_authenticated: { email: 'authenticated.test@vardot.com', password: 'dD.123123ddd' }
# test_editor: { email: 'editor.test@vardot.com', password: 'dD.123123ddd' }
@@ -11,7 +11,7 @@ Feature: Create default testing users.
Given I am a logged in user with the "webmaster" user
@init @tools @local @development @staging
- Scenario: Create the test_authenticated user.
+ Scenario: Create the test_authenticated user
When I go to "/admin/people/create"
And I wait
Then I should see "Add user"
@@ -24,7 +24,7 @@ Feature: Create default testing users.
Then I should not see "The name test_authenticated is already taken."
@init @tools @local @development @staging
- Scenario: Create the test_editor user.
+ Scenario: Create the test_editor user
When I go to "/admin/people/create"
And I wait
Then I should see "Add user"
@@ -38,7 +38,7 @@ Feature: Create default testing users.
Then I should not see "The name test_editor is already taken."
@init @tools @local @development @staging
- Scenario: Create the test_content_admin user.
+ Scenario: Create the test_content_admin user
When I go to "/admin/people/create"
And I wait
Then I should see "Add user"
@@ -52,7 +52,7 @@ Feature: Create default testing users.
Then I should not see "The name test_content_admin is already taken."
@init @tools @local @development @staging
- Scenario: Create the test_seo_admin user.
+ Scenario: Create the test_seo_admin user
When I go to "/admin/people/create"
And I wait
Then I should see "Add user"
@@ -66,7 +66,7 @@ Feature: Create default testing users.
Then I should not see "The name test_seo_admin is already taken."
@init @tools @local @development @staging
- Scenario: Create the test_site_admin user.
+ Scenario: Create the test_site_admin user
When I go to "/admin/people/create"
And I wait
Then I should see "Add user"
@@ -80,7 +80,7 @@ Feature: Create default testing users.
Then I should not see "The name test_site_admin is already taken."
@init @tools @local @development @staging
- Scenario: Create the test_super_admin user.
+ Scenario: Create the test_super_admin user
When I go to "/admin/people/create"
And I wait
Then I should see "Add user"
diff --git a/tests/features/varbase/step1-init-tests/02-add-arabic.feature b/tests/features/varbase/step1-init-tests/02-add-arabic.feature
index b1fd4114637c0c5b0589407d04f62992aecde2b1..b705db5f412dc7c82a67798400c11ee6bf4291fe 100644
--- a/tests/features/varbase/step1-init-tests/02-add-arabic.feature
+++ b/tests/features/varbase/step1-init-tests/02-add-arabic.feature
@@ -1,7 +1,7 @@
-Feature: Add Arabic language if we do not have it to languages in the system.
+Feature: Add Arabic language if we do not have it to languages in the system
@init @tools @local @development @staging @arabic
- Scenario: Add Arabic language if we do not have it to languages in the system.
+ Scenario: Add Arabic language if we do not have it to languages in the system
Given I am a logged in user with the "webmaster" user
When I go to "/admin/config/regional/language"
And I wait
diff --git a/tests/features/varbase/step1-init-tests/README.md b/tests/features/varbase/step1-init-tests/README.md
index 62fdc3bd7d3af142a929bf6e63a5a616e558a2fb..444d77942ceb57b11bc17986ba2d02ba77aabe33 100644
--- a/tests/features/varbase/step1-init-tests/README.md
+++ b/tests/features/varbase/step1-init-tests/README.md
@@ -2,7 +2,7 @@
# List of features in step 1
# Initialization of tests
-* [Feature: Create default testing users.](/tests/features/varbase/step1-init-tests/01-create-default-testing-users.feature)
+* Feature: Create default testing users
```
test_authenticated: { email: 'authenticated.test@vardot.com', password: 'dD.123123ddd' }
test_editor: { email: 'editor.test@vardot.com', password: 'dD.123123ddd' }
@@ -11,5 +11,4 @@ test_seo_admin: { email: 'seo.admin.test@vardot.com', password: 'dD.123123ddd' }
test_site_admin: { email: 'site.admin.test@vardot.com', password: 'dD.123123ddd' }
test_super_admin: { email: 'super.admin.test@vardot.com', password: 'dD.123123ddd' }
```
-
-* [Feature: Add Arabic language if we do not have it to languages in the system.](/tests/features/varbase/step1-init-tests/02-add-arabic.feature)
+* Feature: Add Arabic language if we do not have it to languages in the system
\ No newline at end of file
diff --git a/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-01-user-registration_only-admins-login.feature b/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-01-user-registration_only-admins-login.feature
index 79e106ab9de56dbed4e6c63ceaf55db13c0007ca..10afdd7d869b1f4b5b062fe6ee846d6d43634cd3 100644
--- a/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-01-user-registration_only-admins-login.feature
+++ b/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-01-user-registration_only-admins-login.feature
@@ -7,19 +7,19 @@ So that I will need a site admin or super admin to add me to the website
Given I am an anonymous user
@local @development @staging @production
- Scenario: Check that create new account options does not appear for anonymous users.
+ Scenario: Check that create new account options does not appear for anonymous users
When I go to "/user"
And I wait
Then I should not see "Create new account"
@local @development @staging @production
- Scenario: Check that only admin can create an account.
+ Scenario: Check that only admin can create an account
When I go to "/user/register"
And I wait
Then I should see "Access denied"
@local @development @staging @production
- Scenario: Verify that anonymous users cannot access admin pages.
+ Scenario: Verify that anonymous users cannot access admin pages
When I go to "/admin"
And I wait
Then I should see "Access denied"
diff --git a/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-02-user-roles.feature b/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-02-user-roles.feature
index e45ea861286ecfdc12d4e5d835cf940c260bd9b7..db0bdea523825f5418c496a7bf45ebcdc716b6d7 100644
--- a/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-02-user-roles.feature
+++ b/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-02-user-roles.feature
@@ -4,7 +4,7 @@ I want to be able to see the list of User Roles
So that they must be (Editor, Site Admin, Content Admin, Super Admin)
@local @development @staging @production
- Scenario: Check that all default list of roles are present.
+ Scenario: Check that all default list of roles are present
Given I am a logged in user with the "webmaster" user
When I go to "admin/people/roles"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-03-input-formats.feature b/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-03-input-formats.feature
index 748698c999e951bd9b2a860d48e28977916ef1a4..c5649b2a894798ab2ab1fa81005c42583ea28b69 100644
--- a/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-03-input-formats.feature
+++ b/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-03-input-formats.feature
@@ -4,7 +4,7 @@ I want to be able to switch between input formats
So that can use different type of rich text editors.
@javascript @local @development @staging @production
- Scenario: Check if Site Admin user can change the text format for the body of Basic page.
+ Scenario: Check if Site Admin user can change the text format for the body of Basic page
Given I am a logged in user with the "test_site_admin"
When I go to "/node/add/page"
And I wait
@@ -26,7 +26,7 @@ So that can use different type of rich text editors.
And I should not see the "#cke_edit-body-0-value" element in the "field body"
@javascript @local @development @staging @production
- Scenario: Check if Super Admin user can change the text format for the body of Basic page.
+ Scenario: Check if Super Admin user can change the text format for the body of Basic page
Given I am a logged in user with the "test_super_admin"
When I go to "/node/add/page"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-04-website-languages_english.feature b/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-04-website-languages_english.feature
index 9231d0648d6c1c34e09cf4bcdab26001fc89f992..e410b77af5b3964722355d9a58d78ee6a44b3c80 100644
--- a/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-04-website-languages_english.feature
+++ b/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-04-website-languages_english.feature
@@ -4,7 +4,7 @@ I want to be able to check if the site has got the English language Enabled
So that can be sure that the website is using the English language as one of the languages.
@javascript @local @development @staging @production
- Scenario: Check if we can Create Basic page with English for the language of the content.
+ Scenario: Check if we can Create Basic page with English for the language of the content
Given I am a logged in user with the "test_content_admin" user
And I go to "node/add/page"
And I wait
@@ -18,7 +18,7 @@ So that can be sure that the website is using the English language as one of the
Then I should see "Test English Basic page title by content admin"
@javascript @local @development @staging @production
- Scenario: Check if we can Create Landing page with English for the language of the content.
+ Scenario: Check if we can Create Landing page with English for the language of the content
Given I am a logged in user with the "test_content_admin" user
And I go to "node/add/landing_page"
And I wait
@@ -31,7 +31,7 @@ So that can be sure that the website is using the English language as one of the
Then I should see "Test English Landing page title by content admin"
@javascript @local @development @staging @production
- Scenario: Check if we can Create Basic page with English for the language of the content.
+ Scenario: Check if we can Create Basic page with English for the language of the content
Given I am a logged in user with the "test_site_admin" user
And I go to "node/add/page"
And I wait
@@ -45,7 +45,7 @@ So that can be sure that the website is using the English language as one of the
Then I should see "Test English Basic page title by site admin"
@javascript @local @development @staging @production
- Scenario: Check if we can Create Landing page with English for the language of the content.
+ Scenario: Check if we can Create Landing page with English for the language of the content
Given I am a logged in user with the "test_site_admin" user
And I go to "node/add/landing_page"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-06-convert-urls-links.feature b/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-06-convert-urls-links.feature
index 1e2b9ae393baef76ea0287bfbb8daf3b7b8f2efe..5dcdf17a56c14b869233310b199ffb605b31e236 100644
--- a/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-06-convert-urls-links.feature
+++ b/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-06-convert-urls-links.feature
@@ -4,7 +4,7 @@ I want to add raw URLs and links in the rich text editor
So that they will be converted to links and visitors can click on them.
@javascript @local @development @staging @production
- Scenario: Check if inserted raw URL will convert into a link using the "Rich editor" text format when we save a new Basic page.
+ Scenario: Check if inserted raw URL will convert into a link using the "Rich editor" text format when we save a new Basic page
Given I am a logged in user with the "test_site_admin" user
When I go to "/node/add/page"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/02-user-management/02-01-request-new-password.feature b/tests/features/varbase/step2-apply-tests/02-user-management/02-01-request-new-password.feature
index 1d719dfc5da306533642ae5678b7f5df48269dcb..4aa262e0bbc5f816ea2bee140a4e81e979fc69d8 100644
--- a/tests/features/varbase/step2-apply-tests/02-user-management/02-01-request-new-password.feature
+++ b/tests/features/varbase/step2-apply-tests/02-user-management/02-01-request-new-password.feature
@@ -7,13 +7,13 @@ So that I can reset my password for the account
Given I am not logged in
@local @development @staging @production
- Scenario: Check that an anonymous user can reset his/her password.
+ Scenario: Check that an anonymous user can reset his or her password
When I go to "/user/login"
And I wait
Then I should see "Forgot your password?"
@javascript @local @development @staging @production
- Scenario: Verify that the system cannot send an email to non-existing users/emails.
+ Scenario: Verify that the system cannot send an email to non-existing users or emails
When I go to "/user/password"
And I wait
Then I should see "Username or email address"
diff --git a/tests/features/varbase/step2-apply-tests/02-user-management/02-02-admins-can-create-users-and-assign-role-them.feature b/tests/features/varbase/step2-apply-tests/02-user-management/02-02-admins-can-create-users-and-assign-role-them.feature
index e5b007c8237b6107176e4b88325eb4c11d111ab2..d938fa03a3c51dd07c7b65276b1f617dc27ddf28 100644
--- a/tests/features/varbase/step2-apply-tests/02-user-management/02-02-admins-can-create-users-and-assign-role-them.feature
+++ b/tests/features/varbase/step2-apply-tests/02-user-management/02-02-admins-can-create-users-and-assign-role-them.feature
@@ -7,7 +7,7 @@ So that they will be able to use the site.
Given I am a logged in user with the "webmaster" user
@javascript @local @development @staging @production
- Scenario: Check if admins can see the "Add user" button under People administration page.
+ Scenario: Check if admins can see the "Add user" button under People administration page
Given I go to "/admin/people"
When I click "Add user"
And I should see "People"
@@ -15,7 +15,7 @@ So that they will be able to use the site.
And I should see "Email address"
@javascript @local @development @staging @production
- Scenario: Check if admins can create a new user account as an (authenticated user).
+ Scenario: Check if admins can create a new user account as an authenticated user
Given I go to "/admin/people/create"
When I fill in "tester@vardot.com" for "Email address"
And I fill in "Tester" for "Username"
@@ -24,7 +24,7 @@ So that they will be able to use the site.
And I press "Create new account"
@javascript @cleanup @local @development @staging @production
- Scenario: Delete the Tester user.
+ Scenario: Delete the Tester user
When I go to "/admin/people"
And I fill in "Tester" for "Name or email contains"
And I press "Filter"
diff --git a/tests/features/varbase/step2-apply-tests/02-user-management/02-03-user-login.feature b/tests/features/varbase/step2-apply-tests/02-user-management/02-03-user-login.feature
index 74517add0c2d4ea066c6e12ed449a8f2768a6e80..474e8f942f7ffdcbfe57c6a7d4653d5efe0d210b 100644
--- a/tests/features/varbase/step2-apply-tests/02-user-management/02-03-user-login.feature
+++ b/tests/features/varbase/step2-apply-tests/02-user-management/02-03-user-login.feature
@@ -4,7 +4,7 @@ I want to be able to login to the site
So that I will be able to view/add/edit/ or delete content in the site
@local @development @staging @production
- Scenario: Check if a visitor can login with a valid username and password.
+ Scenario: Check if a visitor can login with a valid username and password
Given I am on "user/login"
And I wait
When I fill in "test_authenticated" for "Username"
@@ -14,7 +14,7 @@ So that I will be able to view/add/edit/ or delete content in the site
Then I should see "test_authenticated"
@local @development @staging @production
- Scenario: Verify a form error after not entering the username or password when we login.
+ Scenario: Verify a form error after not entering the username or password when we login
Given I am on "user/login"
And I wait
When I press "Log in"
diff --git a/tests/features/varbase/step2-apply-tests/02-user-management/02-04-persistent-login.feature b/tests/features/varbase/step2-apply-tests/02-user-management/02-04-persistent-login.feature
index 8a3cd863231f3f9eb2f6c214700191d087b2037a..8815feb88acc3a0a674db79eef469cc0ce36e416 100644
--- a/tests/features/varbase/step2-apply-tests/02-user-management/02-04-persistent-login.feature
+++ b/tests/features/varbase/step2-apply-tests/02-user-management/02-04-persistent-login.feature
@@ -1,10 +1,10 @@
-Feature: User Management - Have persistent login options and configurations.
+Feature: User Management - Have persistent login options and configurations
As a user which can login to the site.
I want to have the option to have "Remember Me" option on the user login form.
So I can persistent my login session independent of setting of a long session lifetime.
@javascript @check @local @development @staging @production
- Scenario: Check the persistent login configuration.
+ Scenario: Check the persistent login configuration
Given I am a logged in user with the "webmaster" user
When I go to "/admin/config/system/persistent_login"
And I wait
@@ -13,7 +13,7 @@ Feature: User Management - Have persistent login options and configurations.
And I should see "0" value in the "edit-max-tokens" input element
@javascript @check @local @development @staging @production
- Scenario: Check if an authenticated user can login and use the [Remember me] option.
+ Scenario: Check if an authenticated user can login and use the [Remember me] option
Given I am not logged in
When I go to "/user"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/02-user-management/02-05-user-protect.feature b/tests/features/varbase/step2-apply-tests/02-user-management/02-05-user-protect.feature
index 8f23fd62b066c2edad414c8020c96078c21d2e58..b61206d05d33f224626671e75d92970a081d895c 100644
--- a/tests/features/varbase/step2-apply-tests/02-user-management/02-05-user-protect.feature
+++ b/tests/features/varbase/step2-apply-tests/02-user-management/02-05-user-protect.feature
@@ -1,10 +1,10 @@
-Feature: User Management - Standard User Management - Have fine-grained access control of user administrators protections with specific user, or all users in a role.
+Feature: User Management - Standard User Management - Have fine-grained access control of user administrators protections with specific user, or all users in a role
As a logged in site admin
I will be allowed to fine-grained access control of user administrators
So that the protections can be specific to a user, or applied to all users in a role.
@javascript @check @local @development @staging @production
- Scenario: Check the User protect configuration.
+ Scenario: Check the User protect configuration
Given I am a logged in user with the "webmaster" user
When I go to "/admin/config/people/userprotect"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/02-user-management/02-06-role-assign.feature b/tests/features/varbase/step2-apply-tests/02-user-management/02-06-role-assign.feature
index fdc37f6d8c966df94fa44ec9d51174e3f0fd1c04..4755ac568c26f46b858d89c38a106523ecd4dee8 100644
--- a/tests/features/varbase/step2-apply-tests/02-user-management/02-06-role-assign.feature
+++ b/tests/features/varbase/step2-apply-tests/02-user-management/02-06-role-assign.feature
@@ -1,10 +1,10 @@
-Feature: User Management - Standard User Management - Users with permission to assign roles may select which roles are available for assignment.
+Feature: User Management - Standard User Management - Users with permission to assign roles may select which roles are available for assignment
As a logged in site admin and a permission to Assign roles
I will be able to assign roles to other users.
So that only users with permission to assign roles may select which roles are available for assignment
@javascript @check @local @development @staging @production
- Scenario: Check the Role Assign configuration.
+ Scenario: Check the Role Assign configuration
Given I am a logged in user with the "webmaster" user
When I go to "/admin/config/people/roleassign"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/03-admin-management/03-00-pre-check-important-admin-development-pages.feature b/tests/features/varbase/step2-apply-tests/03-admin-management/03-00-pre-check-important-admin-development-pages.feature
index 63c216c9f03e624762c07bf945fe95c0d2216c85..90c8ef14d4a569a0f91bda283de17e357dd62b1e 100644
--- a/tests/features/varbase/step2-apply-tests/03-admin-management/03-00-pre-check-important-admin-development-pages.feature
+++ b/tests/features/varbase/step2-apply-tests/03-admin-management/03-00-pre-check-important-admin-development-pages.feature
@@ -1,4 +1,4 @@
-Feature: Pre-check important administrator and development pages.
+Feature: Pre-check important administrator and development pages
As a site admin user
I want to be able to make sure that all admin and development tools are working
So that I can use them after the install or update.
@@ -7,25 +7,25 @@ So that I can use them after the install or update.
Given I am a logged in user with the "webmaster" user
@check @local @development @staging @production
- Scenario: Check the content page.
+ Scenario: Check the content page
When I go to "/admin/content"
And I wait
Then I should see "Content"
@check @local @development @staging @production
- Scenario: Check Files admin page.
+ Scenario: Check Files admin page
When I go to "/admin/content/files"
And I wait
Then I should see "Files"
@check @local @development @staging @production
- Scenario: Check Media Grid admin page.
+ Scenario: Check Media Grid admin page
When I go to "/admin/content/media"
And I wait
Then I should see "Media"
@check @local @development @staging @production
- Scenario: Check Media Table admin page.
+ Scenario: Check Media Table admin page
When I go to "/admin/content/media-table"
And I wait
Then I should see "Media"
@@ -39,7 +39,7 @@ So that I can use them after the install or update.
And I should see "Operations"
@check @local @development @staging @production
- Scenario: Check the structure page.
+ Scenario: Check the structure page
When I go to "/admin/structure"
And I wait
Then I should see "Block layout"
@@ -57,7 +57,7 @@ So that I can use them after the install or update.
And I should see "Webforms"
@check @local @development @staging @production
- Scenario: Check the structure page.
+ Scenario: Check the structure page
When I go to "/admin/structure/page_manager"
And I wait
Then I should see "Pages"
@@ -73,7 +73,7 @@ So that I can use them after the install or update.
And I should see "Total Control dashboard"
@check @local @development @staging @production
- Scenario: Check the views page.
+ Scenario: Check the views page
When I go to "/admin/structure/views"
And I wait
Then I should see "Views"
@@ -81,7 +81,7 @@ So that I can use them after the install or update.
And I should see "Media Hero Slider"
@check @local @development @staging @production
- Scenario: Check the Appearance page.
+ Scenario: Check the Appearance page
When I go to "/admin/appearance"
And I wait
Then I should see "Appearance"
@@ -93,7 +93,7 @@ So that I can use them after the install or update.
And I should see "Vartheme Admin"
@check @local @development @staging @production
- Scenario: Check active type of media types.
+ Scenario: Check active type of media types
When I go to "/media/add"
And I wait
Then I should see "File"
@@ -105,7 +105,7 @@ So that I can use them after the install or update.
And I should see "Tweet"
@check @local @development @staging @production
- Scenario: Check Varbase update instructions page.
+ Scenario: Check Varbase update instructions page
When I go to "/admin/config/development/update-helper"
And I wait
Then I should see "Varbase update instructions"
diff --git a/tests/features/varbase/step2-apply-tests/03-admin-management/03-01-allows-site-administrators-to-masquerade-by-switching-users.feature b/tests/features/varbase/step2-apply-tests/03-admin-management/03-01-allows-site-administrators-to-masquerade-by-switching-users.feature
index bd3cf9447d81a03adcf57c9d3de42554cc37ce1f..2320a4f3eb2f273bf1916b1e52f4083644fd5676 100644
--- a/tests/features/varbase/step2-apply-tests/03-admin-management/03-01-allows-site-administrators-to-masquerade-by-switching-users.feature
+++ b/tests/features/varbase/step2-apply-tests/03-admin-management/03-01-allows-site-administrators-to-masquerade-by-switching-users.feature
@@ -1,10 +1,10 @@
-Feature: Support Requirements - Standard Support Navigation - Allow site super administrators to switch users and surf the site as that user.
+Feature: Support Requirements - Standard Support Navigation - Allow site super administrators to switch users and surf the site as that user
As the site super admin
I want to be able to switch users and surf the site as that user with no password required
So that I can see what is the selected user is seeing in the site then switch back to my own user account at any time.
@javascript @check @local @development @staging @production
-Scenario: Check if the webmaster user UID 1 can masquerade as any user.
+Scenario: Check if the webmaster user UID 1 can masquerade as any user
Given I am a logged in user with the "webmaster" user
# Check if the webmaster user UID 1 can masquerade as an authenticated user.
@@ -63,7 +63,7 @@ Scenario: Check if the webmaster user UID 1 can masquerade as any user.
Then I should see "Masquerade as test_super_admin"
@javascript @check @local @development @staging @production
-Scenario: Check if a super admin user can masquerade as any user.
+Scenario: Check if a super admin user can masquerade as any user
Given I am a logged in user with the "test_super_admin" user
# Check if a super admin user can masquerade as an authenticated user.
@@ -116,7 +116,7 @@ Scenario: Check if a super admin user can masquerade as any user.
Then I should see "Masquerade as webmaster"
@javascript @check @local @development @staging @production
-Scenario: Check if a site admin user can NOT masquerade as any user.
+Scenario: Check if a site admin user can NOT masquerade as any user
# Check if a super admin user can NOT masquerade as the super user (UID 1) "webmaster".
Given I am a logged in user with the "test_site_admin" user
When I go to "/user/1"
@@ -157,21 +157,21 @@ Scenario: Check if a site admin user can NOT masquerade as any user.
Then I should see "Masquerade as test_content_admin"
@javascript @check @local @development @staging @production
-Scenario: Check if a content admin user can NOT masquerade as the super user (UID 1) "webmaster".
+Scenario: Check if a content admin user can NOT masquerade as the super user ID 1 the webmaster
Given I am a logged in user with the "test_content_admin" user
When I go to "/user/1"
And I wait
Then I should not see "Masquerade as webmaster"
@javascript @check @local @development @staging @production
-Scenario: Check if an editor user can NOT masquerade as the super user (UID 1) "webmaster".
+Scenario: Check if an editor user can NOT masquerade as the super user ID 1 the webmaster
Given I am a logged in user with the "test_editor" user
When I go to "/user/1"
And I wait
Then I should not see "Masquerade as webmaster"
@javascript @check @local @development @staging @production
-Scenario: Check if an authenticated user can NOT masquerade as the super user (UID 1) "webmaster".
+Scenario: Check if an authenticated user can NOT masquerade as the super user ID 1 the webmaster
Given I am a logged in user with the "test_authenticated" user
When I go to "/user/1"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/03-admin-management/03-02-navigate-through-drupal-admin-keyboard.feature b/tests/features/varbase/step2-apply-tests/03-admin-management/03-02-navigate-through-drupal-admin-keyboard.feature
index 5c0e0fb0b044e0562d3df44da5089958e2bd9c8f..77dc060beff06f9c7b24379fbefdc57a05950402 100644
--- a/tests/features/varbase/step2-apply-tests/03-admin-management/03-02-navigate-through-drupal-admin-keyboard.feature
+++ b/tests/features/varbase/step2-apply-tests/03-admin-management/03-02-navigate-through-drupal-admin-keyboard.feature
@@ -4,35 +4,35 @@ I want to be able to navigate through the Drupal admin with the keyboard
So that I will have a faster access to administration pages in the site.
@javascript @check @local @development @staging @production
-Scenario: Check if Super Admins can access the Coffee search box to navigate fast between admin pages.
+Scenario: Check if Super Admins can access the Coffee search box to navigate fast between admin pages
Given I am a logged in user with the "test_super_admin" user
When I go to the homepage
And I wait
Then I should see "Go to"
@javascript @check @local @development @staging @production
-Scenario: Check if Site Admins can access the Coffee search box.
+Scenario: Check if Site Admins can access the Coffee search box
Given I am a logged in user with the "test_site_admin" user
When I go to the homepage
And I wait
Then I should see "Go to"
@javascript @check @local @development @staging @production
-Scenario: Check if Content Admins can NOT access the Coffee search box.
+Scenario: Check if Content Admins can NOT access the Coffee search box
Given I am a logged in user with the "test_content_admin" user
When I go to the homepage
And I wait
Then I should not see "Go to"
@javascript @check @local @development @staging @production
-Scenario: Check if Editors can NOT access the Coffee search box.
+Scenario: Check if Editors can NOT access the Coffee search box
Given I am a logged in user with the "test_editor" user
When I go to the homepage
And I wait
Then I should not see "Go to"
@javascript @check @local @development @staging @production
-Scenario: Check if Authenticated users can NOT access the Coffee search box.
+Scenario: Check if Authenticated users can NOT access the Coffee search box
Given I am a logged in user with the "test_authenticated" user
When I go to the homepage
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/03-admin-management/03-03-admins-can-disable-users.feature b/tests/features/varbase/step2-apply-tests/03-admin-management/03-03-admins-can-disable-users.feature
index 77062fec052471777c1ded2aaebd0a7103392e10..bedb163c0d1e8c7a1d471ebc3fac47dd8edd8afb 100644
--- a/tests/features/varbase/step2-apply-tests/03-admin-management/03-03-admins-can-disable-users.feature
+++ b/tests/features/varbase/step2-apply-tests/03-admin-management/03-03-admins-can-disable-users.feature
@@ -4,7 +4,7 @@ I want to be able Block user accounts
So that they will be disabled and not be able to use the site.
@javascript @local @development @staging @production
- Scenario: Check if the "test_authenticated" user is not blocked. and can login.
+ Scenario: Check if the test_authenticated user is not blocked and can login
Given I am on "user/login"
And I wait
When I fill in "test_authenticated" for "Username"
@@ -14,7 +14,7 @@ So that they will be disabled and not be able to use the site.
Then I should see "test_authenticated"
@javascript @local @development @staging @production
- Scenario: Check if the site admin can Administer users and disable a User account "test_authenticated" from accessing the site.
+ Scenario: Check if the site admin can Administer users and disable a User account test_authenticated from accessing the site
Given I am a logged in user with the "test_site_admin" user
When I go to "/admin/people"
And I wait
@@ -32,7 +32,7 @@ So that they will be disabled and not be able to use the site.
Then I should see "The changes have been saved."
@javascript @local @development @staging @production
- Scenario: Check if the blocked user with user id of <Test Blocked User ID> can or can not login.
+ Scenario: Check if the blocked user with user id of Test Blocked User ID can or can not login
Given I am on "user/login"
And I wait
When I fill in "test_authenticated" for "Username"
diff --git a/tests/features/varbase/step2-apply-tests/03-admin-management/03-04-image-media-and-their-usage-list-page-for-admins.feature b/tests/features/varbase/step2-apply-tests/03-admin-management/03-04-image-media-and-their-usage-list-page-for-admins.feature
index ce17cc907ea6ff644bfbdac5da79a3633cb4eeb2..6d5aa8dd1a8d98879e67fb38092e8332788741c7 100644
--- a/tests/features/varbase/step2-apply-tests/03-admin-management/03-04-image-media-and-their-usage-list-page-for-admins.feature
+++ b/tests/features/varbase/step2-apply-tests/03-admin-management/03-04-image-media-and-their-usage-list-page-for-admins.feature
@@ -7,14 +7,14 @@ So that I will be able to manage files, see where they have been used in content
Given I am a logged in user with the "test_site_admin" user
@javascript @local @development @staging @production
- Scenario: Check if content admins can access the content files page.
+ Scenario: Check if content admins can access the content files page
When I go to "admin/content/media-table"
And I wait
Then I should see "Add media"
And I should not see "Access denied"
@local @development @staging @production
- Scenario: Check if we do have a file named "Flag Earth" , if not then upload the file dependently.
+ Scenario: Check if we do have a file named Flag Earth, if not then upload the file dependently
When I go to "/media/add/image"
And I wait
Then I should see "Allowed types: png gif jpg jpeg."
@@ -35,7 +35,7 @@ So that I will be able to manage files, see where they have been used in content
And I should see the "Edit" in the "Flag Earth" row
@javascript @local @development @staging @production
- Scenario: Check if content admins can edit files.
+ Scenario: Check if content admins can edit files
When I go to "admin/content/media-table"
And I wait
Then I should see "Add media"
@@ -53,7 +53,7 @@ So that I will be able to manage files, see where they have been used in content
Then I should see "Image Flag Earth after edit has been updated."
@javascript @local @development @staging @production
- Scenario: Check if content admins can delete files.
+ Scenario: Check if content admins can delete files
When I go to "admin/content/media-table"
And I wait
Then I should see "Add media"
diff --git a/tests/features/varbase/step2-apply-tests/03-admin-management/03-05-json-api-admin-checks-for-the-interface-and-services.feature b/tests/features/varbase/step2-apply-tests/03-admin-management/03-05-json-api-admin-checks-for-the-interface-and-services.feature
index b467034487f25319f3764dd45e0c0f1dc0665038..ca5f5b7dd2219c9065d078bc902bab2ce8653033 100644
--- a/tests/features/varbase/step2-apply-tests/03-admin-management/03-05-json-api-admin-checks-for-the-interface-and-services.feature
+++ b/tests/features/varbase/step2-apply-tests/03-admin-management/03-05-json-api-admin-checks-for-the-interface-and-services.feature
@@ -1,4 +1,4 @@
-Feature: Check JSON:API admin interface and services and Varbase API settings.
+Feature: Check JSON:API admin interface and services and Varbase API settings
As a site admin user
I want to be able to check the JSON:API available interface options
So that I can use them to enable or disable API service for Varbase APIs.
@@ -21,7 +21,7 @@ So that I can use them to enable or disable API service for Varbase APIs.
And I should see "Allowed operations"
@check @local @development @staging @production
- Scenario: Check JSON:API Extras configurations.
+ Scenario: Check JSON:API Extras configurations
When I go to "/admin/config/services/jsonapi/extras"
And I wait
Then I should see "JSON:API Extras"
@@ -35,7 +35,7 @@ So that I can use them to enable or disable API service for Varbase APIs.
And I should see "The following table shows the list of JSON:API resource types available."
@javascript @check @local @development @staging @production
- Scenario: Check Varbase API settings and Generate keys.
+ Scenario: Check Varbase API settings and Generate keys
When I go to "/admin/config/system/varbase/api"
And I wait
Then I should see "Varbase API settings"
diff --git a/tests/features/varbase/step2-apply-tests/03-admin-management/03-06-responsive-preview-devices.feature b/tests/features/varbase/step2-apply-tests/03-admin-management/03-06-responsive-preview-devices.feature
index bf926ea3516dadf79419fbdd50363a2547813690..26e4afc9de05f9864489ee8086596fd09a14b2af 100644
--- a/tests/features/varbase/step2-apply-tests/03-admin-management/03-06-responsive-preview-devices.feature
+++ b/tests/features/varbase/step2-apply-tests/03-admin-management/03-06-responsive-preview-devices.feature
@@ -1,4 +1,4 @@
-Feature: Preview the site in a number of responsive devices.
+Feature: Preview the site in a number of responsive devices
As a site admin user
I want to be able to preview the look and feel of the site in a number of devices
So that I can make sure that the site looks good in small devices too.
diff --git a/tests/features/varbase/step2-apply-tests/04-content-structure/04-01-basic-page-permissions.feature b/tests/features/varbase/step2-apply-tests/04-content-structure/04-01-basic-page-permissions.feature
index 9946dd0639d6fe95bc1493b101615f4f629145b8..0e560a885231919742272311df4ed14fbc049ef9 100644
--- a/tests/features/varbase/step2-apply-tests/04-content-structure/04-01-basic-page-permissions.feature
+++ b/tests/features/varbase/step2-apply-tests/04-content-structure/04-01-basic-page-permissions.feature
@@ -1,4 +1,4 @@
-Feature: Content Structure - Basic Page.
+Feature: Content Structure - Basic Page
As a logged in user with a permission to mange Basic pages
I want to be able to add a "Basic page" to the site with a fixed layout
So that the "Basic page" will show up in the structured menu under its parent page
@@ -7,49 +7,49 @@ So that the "Basic page" will show up in the structured menu under its parent pa
# "Site Admin", or "Super Admin" ) role can add [Basic page]
@javascript @local @development @staging @production
- Scenario: Check if [authenticated user] can add content of "Basic page" type.
+ Scenario: Check if an authenticated user can add content of Basic page type
Given I am a logged in user with the "test_authenticated" user
When I go to "/node/add"
And I wait
Then I should see "You are not authorized to access this page."
@javascript @local @development @staging @production
- Scenario: Check if [Editor] can add content of "Basic page" type.
+ Scenario: Check if an Editor can add content of Basic page type
Given I am a logged in user with the "test_editor" user
When I go to "/node/add"
And I wait
Then I should see "Basic page"
@javascript @local @development @staging @production
- Scenario: Check if [Content Admin] can add content of "Basic page" type.
+ Scenario: Check if a Content Admin can add content of Basic page type
Given I am a logged in user with the "test_content_admin" user
When I go to "/node/add"
And I wait
Then I should see "Basic page"
@javascript @local @development @staging @production
- Scenario: Check if [Site Admin] can add content of "Basic page" type.
+ Scenario: Check if a Site Admin can add content of Basic page type
Given I am a logged in user with the "test_site_admin" user
When I go to "/node/add"
And I wait
Then I should see "Basic page"
@javascript @local @development @staging @production
- Scenario: Check if [Super Admin] can add content of "Basic page" type.
+ Scenario: Check if a Super Admin can add content of Basic page type
Given I am a logged in user with the "test_super_admin" user
When I go to "/node/add"
And I wait
Then I should see "Basic page"
@javascript @local @development @staging @production
- Scenario: Check if the webmaster can add content of "Basic page" type.
+ Scenario: Check if the webmaster can add content of Basic page type
Given I am a logged in user with the "webmaster" user
When I go to "/node/add"
And I wait
Then I should see "Basic page"
@javascript @local @development @staging @production
- Scenario: Check if a user with a permission to manage "Basic page" content type can create Basic pages content
+ Scenario: Check if a user with a permission to manage Basic page content type can create Basic pages content
Given I am a logged in user with the "test_super_admin" user
When I go to "/node/add/page"
And I wait
@@ -59,7 +59,7 @@ So that the "Basic page" will show up in the structured menu under its parent pa
And I should see "Body"
@javascript @local @development @staging @production
- Scenario: Check if we can create a Test Basic page we can see Change layout floating button to change the layout.
+ Scenario: Check if we can create a Test Basic page we can see Change layout floating button to change the layout
Given I am a logged in user with the "test_super_admin" user
When I go to "node/add/page"
And I wait
@@ -70,7 +70,7 @@ So that the "Basic page" will show up in the structured menu under its parent pa
Then I should see "Basic page Test Basic page has been created."
@javascript @local @development @staging @production
- Scenario: Check if a user with a permission to manage "Basic page" content type
+ Scenario: Check if a user with a permission to manage Basic page content type
Given I am a logged in user with the "test_super_admin" user
When I go to "admin/content"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/04-content-structure/04-02-landing-page-permissions.feature b/tests/features/varbase/step2-apply-tests/04-content-structure/04-02-landing-page-permissions.feature
index 2f1675b0e96d24fc92867f654913937f35bec723..54aaccd6e855a8f11a71d693a1d043cb3b11afde 100644
--- a/tests/features/varbase/step2-apply-tests/04-content-structure/04-02-landing-page-permissions.feature
+++ b/tests/features/varbase/step2-apply-tests/04-content-structure/04-02-landing-page-permissions.feature
@@ -4,21 +4,21 @@ I want to be able to add a "Landing page" which has got predefined set of paragr
So that the "Landing page" will show up in the structured menu under its parent page
@javascript @local @development @staging @production
- Scenario: Check if we do have the "Landing page" content type.
+ Scenario: Check if we do have the Landing page content type
Given I am a logged in user with the "webmaster" user
When I go to "/admin/structure/types"
And I wait
Then I should see "Landing page"
@javascript @local @development @staging @production
- Scenario: Check that "Landing page" type have a paragraphs field.
+ Scenario: Check that the Landing page content type has paragraphs field
Given I am a logged in user with the "webmaster" user
When I go to "/admin/structure/types/manage/landing_page/fields"
And I wait
Then I should see "field_lp_paragraphs"
@javascript @local @development @staging @production
- Scenario: Check that Anonymous users can not create a Landing page.
+ Scenario: Check that an Anonymous users can not create a Landing page
Given I am an anonymous user
When I go to "/node/add/landing_page"
And I wait
@@ -26,7 +26,7 @@ So that the "Landing page" will show up in the structured menu under its parent
And I should see "You are not authorized to access this page."
@javascript @local @development @staging @production
- Scenario: Check that authenticated users can not create a Landing page.
+ Scenario: Check that an authenticated user can not create a Landing page
Given I am a logged in user with the "test_authenticated" user
When I go to "/node/add/landing_page"
And I wait
@@ -34,7 +34,7 @@ So that the "Landing page" will show up in the structured menu under its parent
And I should see "You are not authorized to access this page."
@javascript @local @development @staging @production
- Scenario: Check that Editor users can create a Landing page.
+ Scenario: Check that Editor users can create a Landing page
Given I am a logged in user with the "test_editor" user
When I go to "/node/add/landing_page"
And I wait
@@ -42,7 +42,7 @@ So that the "Landing page" will show up in the structured menu under its parent
And I should not see "You are not authorized to access this page."
@javascript @local @development @staging @production
- Scenario: Check that Content Admin users can create a Landing page.
+ Scenario: Check that Content Admin users can create a Landing page
Given I am a logged in user with the "test_content_admin" user
When I go to "/node/add/landing_page"
And I wait
@@ -50,7 +50,7 @@ So that the "Landing page" will show up in the structured menu under its parent
And I should not see "You are not authorized to access this page."
@javascript @local @development @staging @production
- Scenario: Check that Site Admin users can create a Landing page.
+ Scenario: Check that Site Admin users can create a Landing page
Given I am a logged in user with the "test_site_admin" user
When I go to "/node/add/landing_page"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/04-content-structure/04-03-landing-page_add-any-paragraph-type-to-the-page.feature b/tests/features/varbase/step2-apply-tests/04-content-structure/04-03-landing-page_add-any-paragraph-type-to-the-page.feature
index 1c5669b5d1293ae2d1187cb071c8484e0fd3c7df..59c0bb167045ee3e166da66c10508c8f269c8313 100644
--- a/tests/features/varbase/step2-apply-tests/04-content-structure/04-03-landing-page_add-any-paragraph-type-to-the-page.feature
+++ b/tests/features/varbase/step2-apply-tests/04-content-structure/04-03-landing-page_add-any-paragraph-type-to-the-page.feature
@@ -1,10 +1,10 @@
-Feature: Landing Pages - Add any paragraph types to the page.
+Feature: Landing Pages - Add any paragraph types to the page
As a logged in user with a permission to mange Landing pages
I want to be able to add any paragraph type to the page
So that the "Landing page" will show up having paragrpahs of different types
@local @development @staging @production
- Scenario: Upload the "Embed Flag Earth" file.
+ Scenario: Upload the "Embed Flag Earth" file
Given I am a logged in user with the "test_site_admin" user
When I go to "media/add/image"
And I wait
@@ -23,7 +23,7 @@ So that the "Landing page" will show up having paragrpahs of different types
#-----------------------------------------------------------------------------
@javascript @local @development @staging @production
- Scenario: Check Varbase Bootstrap Paragraphs settings, and colours.
+ Scenario: Check Varbase Bootstrap Paragraphs settings
Given I am a logged in user with the "webmaster" user
When I go to "/admin/config/varbase/varbase-bootstrap-paragraphs"
And I wait
@@ -33,7 +33,7 @@ So that the "Landing page" will show up having paragrpahs of different types
Then I should see "The configuration options have been saved."
@javascript @local @development @staging @production
- Scenario: Check if a user with a permission to manage "Landing page" content type can add paragraphs of type "Drupal Block"
+ Scenario: Check if a user with a permission to manage Landing page content type can add paragraphs of type Drupal Block
Given I am a logged in user with the "test_site_admin" user
When I go to "node/add/landing_page"
And I wait
@@ -54,7 +54,7 @@ So that the "Landing page" will show up having paragrpahs of different types
Then I should see "Landing page Test Landing page Drupal Block has been created"
@javascript @local @development @staging @production
- Scenario: Check if a user with a permission to manage "Landing page" content type can add paragraphs of type "Columns (Equal)"
+ Scenario: Check if a user with a permission to manage Landing page content type can add paragraphs of type Columns Equal
Given I am a logged in user with the "test_site_admin" user
When I go to "node/add/landing_page"
And I wait
@@ -72,7 +72,7 @@ So that the "Landing page" will show up having paragrpahs of different types
Then I should see "Landing page Test Landing page Columns (Equal) has been created"
@javascript @local @development @staging @production
- Scenario: Check if a user with a permission to manage "Landing page" content type can add paragraphs of type "Columns (Two Uneven)"
+ Scenario: Check if a user with a permission to manage Landing page content type can add paragraphs of type Columns Two Uneven
Given I am a logged in user with the "test_site_admin" user
When I go to "node/add/landing_page"
And I wait
@@ -90,7 +90,7 @@ So that the "Landing page" will show up having paragrpahs of different types
Then I should see "Landing page Test Landing page Columns (Two Uneven) has been created"
@javascript @local @development @staging @production
- Scenario: Check if a user with a permission to manage "Landing page" content type can add paragraphs of type "Modal"
+ Scenario: Check if a user with a permission to manage Landing page content type can add paragraphs of type Modal
Given I am a logged in user with the "test_site_admin" user
When I go to "node/add/landing_page"
And I wait
@@ -119,7 +119,7 @@ So that the "Landing page" will show up having paragrpahs of different types
Then I should see "Modal title"
@javascript @local @development @staging @production
- Scenario: Check if a user with a permission to manage "Landing page" content type can add paragraphs of type "Rich Text"
+ Scenario: Check if a user with a permission to manage Landing page content type can add paragraphs of type Rich Text
Given I am a logged in user with the "test_site_admin" user
When I go to "node/add/landing_page"
And I wait
@@ -140,7 +140,7 @@ So that the "Landing page" will show up having paragrpahs of different types
And I should see "Rich Text test"
@javascript @local @development @staging @production
- Scenario: Check if a user with a permission to manage "Landing page" content type can add paragraphs of type "Tabs"
+ Scenario: Check if a user with a permission to manage Landing page content type can add paragraphs of type Tabs
Given I am a logged in user with the "test_site_admin" user
When I go to "node/add/landing_page"
And I wait
@@ -167,7 +167,7 @@ So that the "Landing page" will show up having paragrpahs of different types
And I should see "Tab 1"
@javascript @local @development @staging @production
- Scenario: Check if a user with a permission to manage "Landing page" content type can add paragraphs of type "WebForm"
+ Scenario: Check if a user with a permission to manage Landing page content type can add paragraphs of type WebForm
Given I am a logged in user with the "test_site_admin" user
When I go to "node/add/landing_page"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/04-content-structure/04-04-landing-page_text-and-image-paragraphs.feature b/tests/features/varbase/step2-apply-tests/04-content-structure/04-04-landing-page_text-and-image-paragraphs.feature
index 20abd858e3491e09056432018ca4bcb7099c0014..d9ecf92433d4c8e310db07c48f58cd69bf7746ac 100644
--- a/tests/features/varbase/step2-apply-tests/04-content-structure/04-04-landing-page_text-and-image-paragraphs.feature
+++ b/tests/features/varbase/step2-apply-tests/04-content-structure/04-04-landing-page_text-and-image-paragraphs.feature
@@ -1,10 +1,10 @@
-Feature: Content Structure - Landing Pages - Varbase text and image paragraphs.
+Feature: Content Structure - Landing Pages - Varbase text and image paragraphs
As a logged in user with a permission to mange Landing pages
I want to be able to add number of Text and image paragraph compoments
So that the "Landing page" will have text and images in right and left view.
@local @development @staging @production
- Scenario: Upload the "Embed Flag Earth" file.
+ Scenario: Upload the Embed Flag Earth file
Given I am a logged in user with the "test_site_admin" user
When I go to "media/add/image"
And I wait
@@ -23,7 +23,7 @@ So that the "Landing page" will have text and images in right and left view.
#-----------------------------------------------------------------------------
@javascript @local @development @staging @production
- Scenario: Check if a user with a permission to manage "Landing page" content type create a new Landing page.
+ Scenario: Check if a user with a permission to manage Landing page content type create a new Landing page
Given I am a logged in user with the "test_site_admin" user
When I go to "node/add/landing_page"
diff --git a/tests/features/varbase/step2-apply-tests/04-content-structure/04-05-standard-bredcrumbs.feature b/tests/features/varbase/step2-apply-tests/04-content-structure/04-05-standard-bredcrumbs.feature
index 1e1a371bb42077fcda243eb3e33348a70abcc3be..050f7be4c4b643b101d358ba8e6360b9b241da9a 100644
--- a/tests/features/varbase/step2-apply-tests/04-content-structure/04-05-standard-bredcrumbs.feature
+++ b/tests/features/varbase/step2-apply-tests/04-content-structure/04-05-standard-bredcrumbs.feature
@@ -4,7 +4,7 @@ I want to be able to see the back path
So that I can see path I followed to locate the current page usually near the top of the page
@javascript @local @development @staging @production
- Scenario: Add the Test Basic page root page to the main menu.
+ Scenario: Add the Test Basic page root page to the main menu
Given I am a logged in user with the "test_site_admin" user
When I go to "/node/add/page"
And I wait
@@ -20,7 +20,7 @@ So that I can see path I followed to locate the current page usually near the to
And I should see "Test Basic page root body"
@javascript @local @development @staging @production
- Scenario: Add the Test Basic page sub 1, then check the breadcrumb.
+ Scenario: Add the Test Basic page sub 1, then check the breadcrumb
Given I am a logged in user with the "test_site_admin" user
When I go to "/node/add/page"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/04-content-structure/04-06-blog-permissions-feature b/tests/features/varbase/step2-apply-tests/04-content-structure/04-06-blog-permissions-feature
index eccb677de4fa1277e56c132946448ce667e4aee4..51b9c2b31c479a1f4e59a17989cd880d0aee665c 100644
--- a/tests/features/varbase/step2-apply-tests/04-content-structure/04-06-blog-permissions-feature
+++ b/tests/features/varbase/step2-apply-tests/04-content-structure/04-06-blog-permissions-feature
@@ -3,14 +3,14 @@ As a logged in user with a permission to manage Blogs.
I want to be able to add a "Blog"
@javascript @local @development @staging @production
- Scenario: Check if we do have the "Blog" content type.
+ Scenario: Check if we do have the Blog content type
Given I am a logged in user with the "webmaster" user
When I go to "/admin/structure/types"
And I wait
Then I should see "Blog"
@javascript @local @development @staging @production
- Scenario: Check that Anonymous users can not create a Landing page.
+ Scenario: Check that Anonymous users can not create a Landing page
Given I am an anonymous user
When I go to "/node/add/varbase_blog"
And I wait
@@ -18,7 +18,7 @@ I want to be able to add a "Blog"
And I should see "You are not authorized to access this page."
@javascript @local @development @staging @production
- Scenario: Check that authenticated users can not create a Landing page.
+ Scenario: Check that authenticated users can not create a Landing page
Given I am a logged in user with the "test_authenticated" user
When I go to "/node/add/varbase_blog"
And I wait
@@ -26,7 +26,7 @@ I want to be able to add a "Blog"
And I should see "You are not authorized to access this page."
@javascript @local @development @staging @production
- Scenario: Check that Editor users can create a Landing page.
+ Scenario: Check that Editor users can create a Landing page
Given I am a logged in user with the "test_editor" user
When I go to "/node/add/varbase_blog"
And I wait
@@ -34,7 +34,7 @@ I want to be able to add a "Blog"
And I should not see "You are not authorized to access this page."
@javascript @local @development @staging @production
- Scenario: Check that Content Admin users can create a Landing page.
+ Scenario: Check that Content Admin users can create a Landing page
Given I am a logged in user with the "test_content_admin" user
When I go to "/node/add/varbase_blog"
And I wait
@@ -42,7 +42,7 @@ I want to be able to add a "Blog"
And I should not see "You are not authorized to access this page."
@javascript @local @development @staging @production
- Scenario: Check that Site Admin users can create a Landing page.
+ Scenario: Check that Site Admin users can create a Landing page
Given I am a logged in user with the "test_site_admin" user
When I go to "/node/add/varbase_blog"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/05-content-management/05-00-add-default-entityqueue-testing-content-and-config.feature b/tests/features/varbase/step2-apply-tests/05-content-management/05-00-add-default-entityqueue-testing-content-and-config.feature
index 92b5c9ff20b9674bdd62bb3e064b5a571be54be6..2beada3ba2deaa4ffeafe47d2ef191cbdbe830a7 100644
--- a/tests/features/varbase/step2-apply-tests/05-content-management/05-00-add-default-entityqueue-testing-content-and-config.feature
+++ b/tests/features/varbase/step2-apply-tests/05-content-management/05-00-add-default-entityqueue-testing-content-and-config.feature
@@ -1,7 +1,7 @@
-Feature: Content Management - Add default [entityqueue] module testing content and configuration.
+Feature: Content Management - Add default [entityqueue] module testing content and configuration
@javascript @init @tools @local @development @staging
-Scenario: Create "Test Content" content type.
+Scenario: Create Test Content type
Given I am a logged in user with the "test_super_admin" user
When I go to "/admin/structure/types/add"
And I wait
@@ -13,7 +13,7 @@ Scenario: Create "Test Content" content type.
Then I should see "The content type Test Content has been added."
@javascript @init @tools @local @development @staging
-Scenario: Add Entity Queue "Test Queue" and use "Test Content" content type.
+Scenario: Add Entity Queue Test Queue and use Test Content type
Given I am a logged in user with the "test_super_admin" user
When I go to "/admin/structure/entityqueue"
And I wait
@@ -29,7 +29,7 @@ Scenario: Add Entity Queue "Test Queue" and use "Test Content" content type.
Then I should see "The entity queue Test Queue has been added."
@javascript @init @tools @local @development @staging
-Scenario: Add Test content N1, N2, N3, N4 type of test content.
+Scenario: Add Test content N1, N2, N3 type of test content
Given I am a logged in user with the "test_super_admin" user
When I go to "/node/add/test_content"
And I wait
@@ -59,7 +59,7 @@ Scenario: Add Test content N1, N2, N3, N4 type of test content.
Then I should see "Test Content Test content N3 has been created."
@javascript @init @tools @local @development @staging
-Scenario: Add Test content N1, N2, N3, N4 nodes to the "Test Queue" entityqueue.
+Scenario: Add Test content N1, N2, N3 nodes to the Test Queue entityqueue
Given I am a logged in user with the "test_super_admin" user
When I go to "/admin/structure/entityqueue"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/05-content-management/05-01-entityqueue-reverse-order-in-admin-view.feature b/tests/features/varbase/step2-apply-tests/05-content-management/05-01-entityqueue-reverse-order-in-admin-view.feature
index fd2a1ba0fb243b95171d6d13dc32f53dc0fefbd9..7c91df892b097a2e012d7bc888f725587197dd9b 100644
--- a/tests/features/varbase/step2-apply-tests/05-content-management/05-01-entityqueue-reverse-order-in-admin-view.feature
+++ b/tests/features/varbase/step2-apply-tests/05-content-management/05-01-entityqueue-reverse-order-in-admin-view.feature
@@ -1,10 +1,10 @@
-Feature: Content Management - Standard Entity Queue Management - Have the option to Reverse order in admin view.
+Feature: Content Management - Standard Entity Queue Management - Have the option to Reverse order in admin view
As a logged in user with a permission to manage entity queues
I well be able to view the order of entities in entity queues in a reverse order.
So that they will have a flipped order at the front-end.
@javascript @local @development
-Scenario: Check that Reverse order in admin view is working.
+Scenario: Check that Reverse order in admin view is working
Given I am a logged in user with the "webmaster" user
When I go to "/admin/structure/entityqueue"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/05-content-management/05-02-entityqueue-tab-for-content-types.feature b/tests/features/varbase/step2-apply-tests/05-content-management/05-02-entityqueue-tab-for-content-types.feature
index 744e76674d26bf85df1e4b140557b6bf738e7755..b765721767ef005a8fc03157f030013d7bfa9192 100644
--- a/tests/features/varbase/step2-apply-tests/05-content-management/05-02-entityqueue-tab-for-content-types.feature
+++ b/tests/features/varbase/step2-apply-tests/05-content-management/05-02-entityqueue-tab-for-content-types.feature
@@ -4,7 +4,7 @@ I well be able to see an Entity queue tab inside the full content page of a sele
So that I can Add to queue or Remove from queue for the content.
@javascript @local @development
-Scenario: Check if queuable content have the "Entityqueue" tab at the full content page and can Add to queue or Remove from queue.
+Scenario: Check if queuable content have the Entityqueue tab at the full content page and can Add to queue or Remove from queue
Given I am a logged in user with the "test_super_admin" user
When I go to "/node/add/test_content"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/05-content-management/05-03-add-hero-slider-to-entityqueue-using-entityqueue-form-widget.feature b/tests/features/varbase/step2-apply-tests/05-content-management/05-03-add-hero-slider-to-entityqueue-using-entityqueue-form-widget.feature
index e29d22ba628253bc3c327b169f78b044009edd8a..bd1fb6ce6a4270555b2d9867b26864764e70a8ea 100644
--- a/tests/features/varbase/step2-apply-tests/05-content-management/05-03-add-hero-slider-to-entityqueue-using-entityqueue-form-widget.feature
+++ b/tests/features/varbase/step2-apply-tests/05-content-management/05-03-add-hero-slider-to-entityqueue-using-entityqueue-form-widget.feature
@@ -1,9 +1,9 @@
-Feature: Content Management - Add hero slider to entityqueue using entityqueue form widget.
-As a logged in user with a permission to mange entityqueues
-I want to be able to add and remove entities to any allowed entityqueue.
+Feature: Content Management - Add hero slider to entity queue using entity queue form widget
+As a logged in user with a permission to mange entity queues
+I want to be able to add and remove entities to any allowed entity queue.
@local @development @staging @production
- Scenario: Upload the "Flag Earth" file.
+ Scenario: Upload the Flag Earth file
Given I am a logged in user with the "test_site_admin" user
When I go to "media/add/image"
And I wait
@@ -22,7 +22,7 @@ I want to be able to add and remove entities to any allowed entityqueue.
#-----------------------------------------------------------------------------
@javascript @local @development @staging @production
- Scenario: Check that we can open the hero slider media browser.
+ Scenario: Check that we can open the hero slider media browser
Given I am a logged in user with the "test_super_admin" user
When I go to "node/add/varbase_heroslider_media"
And I wait max of 2s for the page to be ready and loaded
@@ -32,7 +32,7 @@ I want to be able to add and remove entities to any allowed entityqueue.
Then the image media browser should be open
@javascript @local @development @staging @production
- Scenario: Add a "Test hero slider number 1" to the heroslider entity queue.
+ Scenario: Add a Test hero slider number 1 to the heroslider entity queue.
Given I am a logged in user with the "test_super_admin" user
When I go to "node/add/varbase_heroslider_media"
And I wait max of 2s for the page to be ready and loaded
@@ -64,7 +64,7 @@ I want to be able to add and remove entities to any allowed entityqueue.
Then I should see "Test hero slider #1"
@javascript @local @development @staging @production
- Scenario: Add a "Test hero slider number 2" to the heroslider entity queue.
+ Scenario: Add a Test hero slider number 2 to the heroslider entity queue
Given I am a logged in user with the "test_super_admin" user
When I go to "node/add/varbase_heroslider_media"
And I wait max of 2s for the page to be ready and loaded
@@ -96,7 +96,7 @@ I want to be able to add and remove entities to any allowed entityqueue.
Then I should see "Test hero slider #2"
@javascript @local @development @staging @production
- Scenario: Check if the "Hero slider" added to the "varbase_heroslider_media" entityqueue.
+ Scenario: Check if the Hero slider added to the varbase hero slider media entity queue
Given I am a logged in user with the "test_super_admin" user
When I go to "admin/structure/entityqueue/varbase_heroslider_media/varbase_heroslider_media"
And I wait
@@ -104,7 +104,7 @@ I want to be able to add and remove entities to any allowed entityqueue.
And I should see "Test hero slider #2" in the "#edit-items-1-target-id" element
@javascript @local @development @staging @production
- Scenario: Remove a "Hero slider" from the "varbase_heroslider_media" entityqueue
+ Scenario: Remove a Hero slider from the varbase hero slider media entity queue
Given I am a logged in user with the "test_super_admin" user
When I go to "admin/content"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/05-content-management/05-04-cloning-content-and-entities.feature b/tests/features/varbase/step2-apply-tests/05-content-management/05-04-cloning-content-and-entities.feature
index 01099741ce2e88033ff4682a5e67f4b68f7cf010..55ffbba8c041269d0f0d40146db59b92b30c34b5 100644
--- a/tests/features/varbase/step2-apply-tests/05-content-management/05-04-cloning-content-and-entities.feature
+++ b/tests/features/varbase/step2-apply-tests/05-content-management/05-04-cloning-content-and-entities.feature
@@ -1,9 +1,9 @@
-Feature: Content Management - Cloning content and entities.
+Feature: Content Management - Cloning content and entities
As a logged in user with a permission to mange entities
I want to be able to clone an entity.
@javascript @local @development
- Scenario: Check if a user with a permission can clone a "landing page"
+ Scenario: Check if a user with a permission can clone a landing page
Given I am a logged in user with the "test_site_admin" user
When I go to "node/add/landing_page"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/05-content-management/05-05-embed-existing-media-image-library.feature b/tests/features/varbase/step2-apply-tests/05-content-management/05-05-embed-existing-media-image-library.feature
index 6a596c3aa2153e3565254373809d2c8522a06e50..25d7fc9ee70d475d4090f4e4f6e198f5078f62b4 100644
--- a/tests/features/varbase/step2-apply-tests/05-content-management/05-05-embed-existing-media-image-library.feature
+++ b/tests/features/varbase/step2-apply-tests/05-content-management/05-05-embed-existing-media-image-library.feature
@@ -9,7 +9,7 @@ So that it will show up under that rich text field without having to upload the
# Create the Basic page and upload the file to the library before the test case.
# ----------------------------------------------------------------------------
@javascript @local @development @staging @production
- Scenario: Create the "Test Basic page to embed existing files" content.
+ Scenario: Create the Test Basic page to embed existing files content
When I go to "node/add/page"
And I wait
And I fill in "Test Basic page to embed existing files" for "Title"
@@ -19,7 +19,7 @@ So that it will show up under that rich text field without having to upload the
Then I should see "Basic page Test Basic page to embed existing files has been created."
@local @development @staging @production
- Scenario: Upload the "Embed Flag Earth" file.
+ Scenario: Upload the Embed Flag Earth file
When I go to "/media/add/image"
And I wait
Then I should see "Allowed types: png gif jpg jpeg."
@@ -37,7 +37,7 @@ So that it will show up under that rich text field without having to upload the
#-----------------------------------------------------------------------------
@javascript @local @development @staging @production
- Scenario: Check if we are able to embed existing files library in the rich text editor.
+ Scenario: Check if we are able to embed existing files library in the rich text editor
When I go to "admin/content"
And I wait
Then I should see "Content"
diff --git a/tests/features/varbase/step2-apply-tests/05-content-management/05-06-easy-linking-internal-content-searching-content-by-its-titles.feature b/tests/features/varbase/step2-apply-tests/05-content-management/05-06-easy-linking-internal-content-searching-content-by-its-titles.feature
index f22d89cd6e1e61e33100387afc1c1d173d76ac36..df1810ccf0a78e871e8e4c44388764b909f05dbd 100644
--- a/tests/features/varbase/step2-apply-tests/05-content-management/05-06-easy-linking-internal-content-searching-content-by-its-titles.feature
+++ b/tests/features/varbase/step2-apply-tests/05-content-management/05-06-easy-linking-internal-content-searching-content-by-its-titles.feature
@@ -4,8 +4,7 @@ I want to be able to add internal links searching the title of an internal conte
So that will ease the work of adding internal links in the rich text editor fields.
@javascript @local @development @staging @production
- Scenario: Check if inserted raw URL will convert into a link when we save when
- We are using the "Visual editor" text format.
+ Scenario: Check if inserted raw URL will convert into a link when we save when We are using the Visual editor text format
Given I am a logged in user with the "test_site_admin" user
When I go to "/node/add/page"
And I wait
@@ -18,8 +17,7 @@ So that will ease the work of adding internal links in the rich text editor fiel
And I should see "Linking to internal content #1 body"
@javascript @local @development @staging @production
- Scenario: Check if inserted raw URL will convert into a link when we save when
- We are using the "Visual editor" text format.
+ Scenario: Check if inserted raw URL will convert into a link when we save when we are using the Visual editor text format
Given I am a logged in user with the "test_site_admin" user
When I go to "/node/add/page"
And I wait
diff --git a/tests/features/varbase/step2-apply-tests/README.md b/tests/features/varbase/step2-apply-tests/README.md
index e40e85782dd02ad46edda25d3c130644b6c07a25..632899753122349ce22d4bb410296091a718ba50 100644
--- a/tests/features/varbase/step2-apply-tests/README.md
+++ b/tests/features/varbase/step2-apply-tests/README.md
@@ -3,40 +3,44 @@
# List of Features in the step 2
-### [Website Base Requirements](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/)
-* [Feature: Website Base Requirements - User Registration - Only admins login](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-01-user-registration_only-admins-login.feature)
-* [Feature: Website Base Requirements - User Roles - Simple Roles](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-02-user-roles.feature)
-* [Feature: Website Base Requirements - Content Editing - Rich Text Editor - Input formats](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-03-input-formats.feature)
-* [Feature: Website Base Requirements - Website Languages - English](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-04-website-languages_english.feature)
-* [Feature: Website Base Requirements - Website Languages - All content translatable to all languages](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-05-translatable-content-types-to-all-languages.feature)
-* [Feature: Website Base Requirements - Content Editing - Rich Text Editor - Convert URLs into links](/tests/features/varbase/step2-apply-tests/01-website-base-requirements/01-06-convert-urls-links.feature)
+### Website Base Requirements
+* Feature: Website Base Requirements - User Registration - Only admins login
+* Feature: Website Base Requirements - User Roles - Simple Roles
+* Feature: Content Editing - Rich Text Editor - Input formats
+* Feature: Website Base Requirements - Website Languages - English
+* Feature: Website Base Requirements - Website Languages - All content translatable to all languages
+* Feature: Content Editing - Rich Text Editor - Convert URLs into links
-### [User Management](/tests/features/varbase/step2-apply-tests/02-user-management/)
-* [Feature: User Management - Standard User Management - Request new password](/tests/features/varbase/step2-apply-tests/02-user-management/02-01-request-new-password.feature)
-* [Feature: User Management - Standard User Management - Admins can create users and assign a role to them](/tests/features/varbase/step2-apply-tests/02-user-management/02-02-admins-can-create-users-and-assign-role-them.feature)
-* [Feature: User Management - Standard User Management - Login](/tests/features/varbase/step2-apply-tests/02-user-management/02-03-user-login.feature)
-* [Feature: User Management - Have persistent login options and configurations.](/tests/features/varbase/step2-apply-tests/02-user-management/02-04-persistent-login.feature)
-* [Feature: User Management - Standard User Management - Have fine-grained access control of user administrators protections with specific user, or all users in a role.](/tests/features/varbase/step2-apply-tests/02-user-management/02-05-user-protect.feature)
-* [Feature: User Management - Standard User Management - Users with permission to assign roles may select which roles are available for assignment.](/tests/features/varbase/step2-apply-tests/02-user-management/02-06-role-assign.feature)
+### User Management
+* Feature: User Management - Standard User Management - Request new password
+* Feature: User Management - Standard User Management - Admins can create users and assign a role to them
+* Feature: User Management - Standard User Management - Login
+* Feature: User Management - Have persistent login options and configurations
+* Feature: User Management - Standard User Management - Have fine-grained access control of user administrators protections with specific user, or all users in a role
+* Feature: User Management - Standard User Management - Users with permission to assign roles may select which roles are available for assignment
-### [Admin Management](/tests/features/varbase/step2-apply-tests/03-admin-management/)
-* [Feature: Admin management - Support Requirements - Standard Support Navigation - Allow site super administrators to switch users and surf the site as that user.](/tests/features/varbase/step2-apply-tests/03-admin-management/03-01-allows-site-administrators-to-masquerade-by-switching-users.feature)
-* [Feature: Admin management - Standard Back-End Navigation - Navigate through the Drupal admin with the keyboard for faster access](/tests/features/varbase/step2-apply-tests/03-admin-management/03-02-navigate-through-drupal-admin-keyboard.feature)
-* [Feature: Admin management - Standard User Management - Admins can disable users](/tests/features/varbase/step2-apply-tests/03-admin-management/03-03-admins-can-disable-users.feature)
-* [Feature: Admin management - Assets Management - Image media and their usage list page for site admins](/tests/features/varbase/step2-apply-tests/03-admin-management/03-04-image-media-and-their-usage-list-page-for-admins.feature)
+### Admin Management
+* Feature: Pre-check important administrator and development pages
+* Feature: Support Requirements - Standard Support Navigation - Allow site super administrators to switch users and surf the site as that user
+* Feature: Admin management - Standard Back-End Navigation - Navigate through the Drupal admin with the keyboard for faster access
+* Feature: User Management - Standard User Management - Admins can disable users
+* Feature: File & Media Management - Assets Management - Image media and their usage list page for site admins
+* Feature: Check JSON:API admin interface and services and Varbase API settings
+* Feature: Preview the site in a number of responsive devices
-### [Content Structure](/tests/features/varbase/step2-apply-tests/04-content-structure/)
-* [Feature: Content Structure - Basic Page.](/tests/features/varbase/step2-apply-tests/04-content-structure/04-01-basic-page-permissions.feature)
-* [Feature: Content Structure - Landing Pages](/tests/features/varbase/step2-apply-tests/04-content-structure/04-02-landing-page-permissions.feature)
-* [Feature: Content Structure - Landing Pages - Add any paragraph types to the page.](/tests/features/varbase/step2-apply-tests/04-content-structure/04-03-landing-page_add-any-paragraph-type-to-the-page.feature)
-* [Feature: Content Structure - Content Structure - Landing Pages - Varbase text and image paragraphs.](/tests/features/varbase/step2-apply-tests/04-content-structure/04-04-landing-page_text-and-image-paragraphs.feature)
-* [Feature: Content Structure - Navigational Features - Breadcrumbs - Standard breadcrumbs](/tests/features/varbase/step2-apply-tests/04-content-structure/04-05-standard-bredcrumbs.feature)
+### Content Structure
+* Feature: Content Structure - Basic Page
+* Feature: Content Structure - Landing Pages
+* Feature: Landing Pages - Add any paragraph types to the page
+* Feature: Content Structure - Landing Pages - Varbase text and image paragraphs
+* Feature: Navigational Features - Breadcrumbs - Standard breadcrumbs
+* Feature: Content Structure - Blog post
-### [Content Management](/tests/features/varbase/step2-apply-tests/05-content-management/)
-* [Feature: Content Management - Add default [entityqueue] module testing content and configuration.](/tests/features/varbase/step2-apply-tests/04-content-structure/05-00-add-default-entityqueue-testing-content-and-config.feature)
-* [Feature: Content Management - Standard Entity Queue Management - Have the option to Reverse order in admin view.](/tests/features/varbase/step2-apply-tests/04-content-structure/05-01-entityqueue-reverse-order-in-admin-view.feature)
-* [Feature: Content Management - Standard Entity Queue Management - Have Entityqueue tab inside the full content page and be able to Add to a queue or Remove from a queue](/tests/features/varbase/step2-apply-tests/04-content-structure/05-02-entityqueue-tab-for-content-types.feature)
-* [Feature: Content Management - Add hero slider to entityqueue using entityqueue form widget.](/tests/features/varbase/step2-apply-tests/04-content-structure/05-03-add-hero-slider-to-entityqueue-using-entityqueue-form-widget.feature)
-* [Feature: Content Management - Cloning content and entities.](/tests/features/varbase/step2-apply-tests/04-content-structure/05-04-cloning-content-and-entities.feature)
-* [Feature: Content Management - Assets Management - Ability to embed existing media image library in the rich text editor](/tests/features/varbase/step2-apply-tests/04-content-structure/05-05-embed-existing-media-image-library.feature)
-* [Feature: Content Management - Content Editing - Rich Text Editor - Easy linking to internal content by searching for content by its titles](/tests/features/varbase/step2-apply-tests/04-content-structure/05-06-easy-linking-internal-content-searching-content-by-its-titles.feature)
+### Content Management
+* Feature: Content Management - Add default [entityqueue] module testing content and configuration
+* Feature: Content Management - Standard Entity Queue Management - Have the option to Reverse order in admin view
+* Feature: Content Management - Standard Entity Queue Management - Have Entity queue tab inside the full content page and be able to Add to a queue or Remove from a queue
+* Feature: Content Management - Add hero slider to entity queue using entity queue form widget
+* Feature: Content Management - Cloning content and entities
+* Feature: File & Media Management - Assets Management - Ability to embed existing media image library in the rich text editor
+* Feature: Content Editing - Rich Text Editor - Easy linking to internal content by searching for content by its titles
diff --git a/tests/features/varbase/step3-cleanup-tests/01-delete-default-testing-users.feature b/tests/features/varbase/step3-cleanup-tests/01-delete-default-testing-users.feature
index 18b25431179c4398734cbaad0b60cb547d8dab71..c47d275c855a4099ededb6e5e5ae490702506076 100644
--- a/tests/features/varbase/step3-cleanup-tests/01-delete-default-testing-users.feature
+++ b/tests/features/varbase/step3-cleanup-tests/01-delete-default-testing-users.feature
@@ -1,4 +1,4 @@
-Feature: Delete default testing users.
+Feature: Delete default testing users
# test_authenticated: { email: 'authenticated.test@vardot.com', password: 'dD.123123ddd' }
# test_editor: { email: 'editor.test@vardot.com', password: 'dD.123123ddd' }
@@ -11,7 +11,7 @@ Feature: Delete default testing users.
Given I am a logged in user with the "webmaster" user
@javascript @cleanup @tools @local @development @staging
- Scenario: Delete the test_authenticated user.
+ Scenario: Delete the test_authenticated user
When I go to "/admin/people"
And I wait
And I fill in "test_authenticated" for "Name or email contains"
@@ -29,7 +29,7 @@ Feature: Delete default testing users.
Then I should see "test_authenticated has been deleted."
@javascript @cleanup @tools @local @development @staging
- Scenario: Delete the test_editor user.
+ Scenario: Delete the test_editor user
When I go to "/admin/people"
And I wait
And I fill in "test_editor" for "Name or email contains"
@@ -48,7 +48,7 @@ Feature: Delete default testing users.
Then I should see "test_editor has been deleted."
@javascript @cleanup @tools @local @development @staging
- Scenario: Delete the test_content_admin user.
+ Scenario: Delete the test_content_admin user
When I go to "/admin/people"
And I fill in "test_content_admin" for "Name or email contains"
And I press "Filter"
@@ -66,7 +66,7 @@ Feature: Delete default testing users.
Then I should see "test_content_admin has been deleted."
@javascript @cleanup @tools @local @development @staging
- Scenario: Delete the test_seo_admin user.
+ Scenario: Delete the test_seo_admin user
When I go to "/admin/people"
And I wait
And I fill in "test_seo_admin" for "Name or email contains"
@@ -85,7 +85,7 @@ Feature: Delete default testing users.
Then I should see "test_seo_admin has been deleted."
@javascript @cleanup @tools @local @development @staging
- Scenario: Delete the test_site_admin user.
+ Scenario: Delete the test_site_admin user
When I go to "/admin/people"
And I wait
And I fill in "test_site_admin" for "Name or email contains"
@@ -104,7 +104,7 @@ Feature: Delete default testing users.
Then I should see "test_site_admin has been deleted."
@javascript @cleanup @tools @local @development @staging
- Scenario: Delete the test_super_admin user.
+ Scenario: Delete the test_super_admin user
When I go to "/admin/people"
And I wait
And I fill in "test_super_admin" for "Name or email contains"
diff --git a/tests/features/varbase/step3-cleanup-tests/02-delete-arabic.feature b/tests/features/varbase/step3-cleanup-tests/02-delete-arabic.feature
index 320f4421f109ad1dabe461ec48a8f75b9af5b892..531516ad8ce6320fa9f83f62cc6ddfc868983b3f 100644
--- a/tests/features/varbase/step3-cleanup-tests/02-delete-arabic.feature
+++ b/tests/features/varbase/step3-cleanup-tests/02-delete-arabic.feature
@@ -1,7 +1,7 @@
-Feature: Delete Arabic language from the system.
+Feature: Delete Arabic language from the system
@javascript @cleanup @arabic @local
- Scenario: Delete Arabic language from the system.
+ Scenario: Delete Arabic language from the system
Given I am a logged in user with the "webmaster" user
When I go to "/admin/config/regional/language/delete/ar"
And I wait
diff --git a/tests/features/varbase/step3-cleanup-tests/03-cleanup-after-entityqueue-tests.feature b/tests/features/varbase/step3-cleanup-tests/03-cleanup-after-entityqueue-tests.feature
index daf4c1d103f04c09560efb37866f8310af1c3a14..1194ba6d4bad59ce737c06e302c105e3d410039d 100644
--- a/tests/features/varbase/step3-cleanup-tests/03-cleanup-after-entityqueue-tests.feature
+++ b/tests/features/varbase/step3-cleanup-tests/03-cleanup-after-entityqueue-tests.feature
@@ -1,7 +1,7 @@
-Feature: Cleanup after [entityqueue] module tests.
+Feature: Cleanup after [entityqueue] module tests
@javascript @cleanup @local @development
-Scenario: Delete Entity Queue "Test Queue".
+Scenario: Delete Entity Queue Test Queue
Given I am a logged in user with the "webmaster" user
When I go to "/admin/structure/entityqueue/test_queue/delete"
And I wait
@@ -12,7 +12,7 @@ Scenario: Delete Entity Queue "Test Queue".
@javascript @cleanup @local @development
-Scenario: Delete "Test Content" content type item
+Scenario: Delete Test Content content type item
Given I am a logged in user with the "webmaster" user
When I go to "/admin/structure/types/manage/test_content/delete"
And I wait
diff --git a/tests/features/varbase/step3-cleanup-tests/04-cleanup-leftover-media-in-the-media-library.feature b/tests/features/varbase/step3-cleanup-tests/04-cleanup-leftover-media-in-the-media-library.feature
new file mode 100644
index 0000000000000000000000000000000000000000..c30249ce8be7f42bb372f62b885ed2d6532f30ab
--- /dev/null
+++ b/tests/features/varbase/step3-cleanup-tests/04-cleanup-leftover-media-in-the-media-library.feature
@@ -0,0 +1,16 @@
+Feature: Cleanup leftover media from the Media Library
+
+@javascript @cleanup @local @development
+Scenario: Delete leftover media from the Media Library
+ Given I am a logged in user with the "webmaster" user
+ When I go to "/admin/content/media"
+ And I wait
+ Then I should see "Media"
+ When I check the box "edit-select-all"
+ And I select "views_bulk_operations_delete_entity" from "edit-action"
+ And I press "Apply to selected items"
+ And I wait
+ Then I should see "Are you sure you wish to perform"
+ When I press "Execute action"
+ And I wait 10s
+ Then I should see "Media"
diff --git a/tests/features/varbase/step3-cleanup-tests/README.md b/tests/features/varbase/step3-cleanup-tests/README.md
index 93eddf3ced972aba2de8a2d2cf1bc0b8a77f218d..38a1752b50035d485de67952c87fd96c56ba62d4 100644
--- a/tests/features/varbase/step3-cleanup-tests/README.md
+++ b/tests/features/varbase/step3-cleanup-tests/README.md
@@ -2,7 +2,7 @@
# Cleanup tests
# List of features in the step 3
-* [Feature: Delete default testing users.](/tests/features/varbase/step3-cleanup-tests/01-delete-default-testing-users.feature)
+* Feature: Delete default testing users
```
test_authenticated
test_editor
@@ -12,5 +12,6 @@ test_site_admin
test_super_admin
```
-* [Feature: Delete Arabic language from the system.](/tests/features/varbase/step3-cleanup-tests/02-delete-arabic.feature)
-* [Feature: Cleanup after [entityqueue] module tests.](/tests/features/varbase/step3-cleanup-tests/03-cleanup-after-entityqueue-tests.feature)
\ No newline at end of file
+* Feature: Delete Arabic language from the system
+* Feature: Cleanup after [entityqueue] module tests
+* Feature: Cleanup leftover media from the Media Library
\ No newline at end of file
diff --git a/tests/tools/drush/on-development.feature b/tests/tools/drush/on-development.feature
deleted file mode 100644
index c2c93a0eaaeec91621e5c409fee7778c71a8a680..0000000000000000000000000000000000000000
--- a/tests/tools/drush/on-development.feature
+++ /dev/null
@@ -1,85 +0,0 @@
-Feature: On development.
-As a Developer
-I want to be able to swich number of variables and module ON and OFF
-So that will be able to work on my local Development machine.
-
-# NOTE: Make sure that you commented variables with force override in
-# then local.settings.php file for Varbase 7.x-3.x
-
-## On Development
-# https://bitbucket.org/snippets/Vardot/M7yd
-# ------------------------------------------------------------
-# drush vset error_level 2;
-# drush vset preprocess_js 0;
-# drush vset preprocess_css 0;
-# drush vset cache 0;
-# drush vset page_compression 0;
-# drush vset block_cache 0;
-# drush vset file_temporary_path '/tmp';
-# drush en field_ui views_ui context_ui ds_ui module_filter dblog -y;
-
- @api @tools @local @development
- Scenario: Set error_level to 2.
- Given I run drush "vset" "error_level 2"
- Then print last drush output
-
- @api @tools @local @development
- Scenario: Set preprocess_js to 0.
- Given I run drush "vset" "preprocess_js 0"
- Then print last drush output
-
- @api @tools @local @development
- Scenario: Set preprocess_css to 0.
- Given I run drush "vset" "vset preprocess_css 0"
- Then print last drush output
-
- @api @tools @local @development
- Scenario: Set cache to 0.
- Given I run drush "vset" "cache 0"
- Then print last drush output
-
- @api @tools @local @development
- Scenario: Set page_compression to 0.
- Given I run drush "vset" "page_compression 0"
- Then print last drush output
-
- @api @tools @local @development
- Scenario: Set block_cache to 0.
- Given I run drush "vset" "block_cache 0"
- Then print last drush output
-
- @api @tools @local @development
- Scenario: Set file_temporary_path to '/tmp'.
- Given I run drush "vset" "file_temporary_path '/tmp'"
- Then print last drush output
-
- @api @tools @local @development
- Scenario: Enable field_ui.
- Given I run drush "en" "field_ui -y"
- Then print last drush output
-
- @api @tools @local @development
- Scenario: Enable views_ui.
- Given I run drush "en" "views_ui -y"
- Then print last drush output
-
- @api @tools @local @development
- Scenario: Enable context_ui.
- Given I run drush "en" "context_ui -y"
- Then print last drush output
-
- @api @tools @local @development
- Scenario: Enable ds_ui.
- Given I run drush "en" "field_ui -y"
- Then print last drush output
-
- @api @tools @local @development
- Scenario: Enable module_filter.
- Given I run drush "en" "module_filter -y"
- Then print last drush output
-
- @api @tools @local @development
- Scenario: Enable dblog.
- Given I run drush "en" "dblog -y"
- Then print last drush output
-
diff --git a/tests/tools/drush/on-production.feature b/tests/tools/drush/on-production.feature
deleted file mode 100644
index 438ce79c131030ca4ea24d01df4ee25ad17bb886..0000000000000000000000000000000000000000
--- a/tests/tools/drush/on-production.feature
+++ /dev/null
@@ -1,80 +0,0 @@
-Feature: On development.
-As a Developer
-I want to be able to swich number of variables and module ON and OFF
-So that will be able to work on my local Development machine.
-
-# NOTE: Make sure that you commented variables with force override in
-# then local.settings.php file for Varbase 7.x-3.x
-
-## On Production
-# https://bitbucket.org/snippets/Vardot/M7yd
-# ------------------------------------------------------------
-# drush vset error_level 0;
-# drush vset preprocess_js 1;
-# drush vset preprocess_css 1;
-# drush vset cache 1;
-# drush vset page_compression 1;
-# drush vset block_cache 1;
-#
-# drush dis field_ui views_ui context_ui module_filter ds_ui dblog -y;
-
-@api @tools @production
- Scenario: Set error_level to 0.
- Given I run drush "vset" "error_level 0"
- Then print last drush output
-
- @api @tools @production
- Scenario: Set preprocess_js to 1
- Given I run drush "vset" "preprocess_js 1"
- Then print last drush output
-
- @api @tools @production
- Scenario: Set preprocess_css to 1.
- Given I run drush "vset" "preprocess_css 1"
- Then print last drush output
-
- @api @tools @production
- Scenario: Set cache to 1.
- Given I run drush "vset" "cache 1"
- Then print last drush output
-
- @api @tools @production
- Scenario: Set page_compression to 1.
- Given I run drush "vset" "page_compression 1"
- Then print last drush output
-
- @api @tools @production
- Scenario: Set block_cache to 1.
- Given I run drush "vset" "block_cache 1"
- Then print last drush output
-
- @api @tools @production
- Scenario: Enable field_ui module.
- Given I run drush "dis" "field_ui -y"
- Then print last drush output
-
- @api @tools @production
- Scenario: Enable views_ui module.
- Given I run drush "dis" "views_ui -y"
- Then print last drush output
-
- @api @tools @production
- Scenario: Enable context_ui module.
- Given I run drush "dis" "context_ui -y"
- Then print last drush output
-
- @api @tools @production
- Scenario: Enable ds_ui module.
- Given I run drush "dis" "field_ui -y"
- Then print last drush output
-
- @api @tools @production
- Scenario: Enable module_filter module.
- Given I run drush "dis" "module_filter -y"
- Then print last drush output
-
- @api @tools @production
- Scenario: Enable dblog module.
- Given I run drush "dis" "dblog -y"
- Then print last drush output
-