Issue #3255633: Switch default Automated Functional Testing users creation to...

Issue #3255633: Switch default Automated Functional Testing users creation to use drush user:create and drush user:role:add and use the default manual testing user names and emails

tests/features/varbase/step2-apply-tests/04-content-structure/04-06-blog-permissions.feature → tests/features/varbase/04-content-structure/04-06-blog-permissions.feature

@@ -19,7 +19,7 @@ I want to be able to add a "Blog"
 
   @javascript @local @development @staging @production
   Scenario: Check that authenticated users can not create a Landing page
-    Given I am a logged in user with the "test_authenticated" user
+    Given I am a logged in user with the "Normal user" user
      When I go to "/node/add/varbase_blog"
       And I wait
      Then I should see "Access denied"
@@ -27,7 +27,7 @@ I want to be able to add a "Blog"
 
   @javascript @local @development @staging @production
   Scenario: Check that Editor users can create a Landing page
-    Given I am a logged in user with the "test_editor" user
+    Given I am a logged in user with the "Editor" user
      When I go to "/node/add/varbase_blog"
       And I wait
      Then I should not see "Access denied"
@@ -35,7 +35,7 @@ I want to be able to add a "Blog"
 
   @javascript @local @development @staging @production
   Scenario: Check that Content Admin users can create a Landing page
-    Given I am a logged in user with the "test_content_admin" user
+    Given I am a logged in user with the "Content admin" user
      When I go to "/node/add/varbase_blog"
       And I wait
      Then I should not see "Access denied"
@@ -43,7 +43,7 @@ I want to be able to add a "Blog"
 
   @javascript @local @development @staging @production
   Scenario: Check that Site Admin users can create a Landing page
-    Given I am a logged in user with the "test_site_admin" user
+    Given I am a logged in user with the "Site admin" user
      When I go to "/node/add/varbase_blog"
       And I wait
      Then I should not see "Access denied"

tests/features/varbase/step2-apply-tests/04-content-structure/04-07-landing-page-layout-builder-permissions.feature → tests/features/varbase/04-content-structure/04-07-landing-page-layout-builder-permissions.feature

@@ -28,7 +28,7 @@ So that the "Landing page (Layout Builder)" will show up in the structured menu
 
   @javascript @local @development @staging @production
   Scenario: Check that an authenticated user can not create a Landing page (Layout Builder)
-    Given I am a logged in user with the "test_authenticated" user
+    Given I am a logged in user with the "Normal user" user
      When I go to "/node/add/landing_page_lb"
       And I wait
      Then I should see "Access denied"
@@ -36,7 +36,7 @@ So that the "Landing page (Layout Builder)" will show up in the structured menu
 
   @javascript @local @development @staging @production
   Scenario: Check that Editor users can create a Landing page (Layout Builder)
-    Given I am a logged in user with the "test_editor" user
+    Given I am a logged in user with the "Editor" user
      When I go to "/node/add/landing_page_lb"
       And I wait
      Then I should not see "Access denied"
@@ -44,7 +44,7 @@ So that the "Landing page (Layout Builder)" will show up in the structured menu
 
   @javascript @local @development @staging @production
   Scenario: Check that Content Admin users can create a Landing page (Layout Builder)
-    Given I am a logged in user with the "test_content_admin" user
+    Given I am a logged in user with the "Content admin" user
      When I go to "/node/add/landing_page_lb"
       And I wait
      Then I should not see "Access denied"
@@ -52,7 +52,7 @@ So that the "Landing page (Layout Builder)" will show up in the structured menu
 
   @javascript @local @development @staging @production
   Scenario: Check that SEO Admin users can create a Landing page (Layout Builder)
-    Given I am a logged in user with the "test_seo_admin" user
+    Given I am a logged in user with the "SEO admin" user
      When I go to "/node/add/landing_page_lb"
       And I wait
      Then I should not see "Access denied"
@@ -60,7 +60,7 @@ So that the "Landing page (Layout Builder)" will show up in the structured menu
 
   @javascript @local @development @staging @production
   Scenario: Check that Site Admin users can create a Landing page (Layout Builder)
-    Given I am a logged in user with the "test_site_admin" user
+    Given I am a logged in user with the "Site admin" user
      When I go to "/node/add/landing_page_lb"
       And I wait
      Then I should not see "Access denied"

tests/features/varbase/step2-apply-tests/04-content-structure/04-08-landing-page-layout-builder_check-to-add-sections-and-choose-layouts-for-sections.feature → tests/features/varbase/04-content-structure/04-08-landing-page-layout-builder_check-to-add-sections-and-choose-layouts-for-sections.feature

@@ -5,7 +5,7 @@ So that the "Landing (Layout Builder) page" will show up having the listed secti
 
   @javascript @local @development @staging @production
   Scenario: Check if a user with a permission to manage Landing page (Layout Builder) content type can add sections with any layouts to the page
-    Given I am a logged in user with the "test_site_admin" user
+    Given I am a logged in user with the "Site admin" user
      When I go to "/node/add/landing_page_lb"
       And I wait
      Then I should see "Create Landing page (Layout Builder)"

tests/features/varbase/step2-apply-tests/04-content-structure/04-09-homepage-permissions.feature → tests/features/varbase/04-content-structure/04-09-homepage-permissions.feature

@@ -40,7 +40,7 @@ So that the homepage can be changed with permission in an easy way and be sure i
 
   @javascript @local @development @staging @production
   Scenario: Check that an authenticated user can not edit the Homepage which built by the Landing page (Layout Builder)
-    Given I am a logged in user with the "test_authenticated" user
+    Given I am a logged in user with the "Normal user" user
      When I go to the homepage
       And I wait
      Then I should see "Welcome to Varbase"
@@ -57,7 +57,7 @@ So that the homepage can be changed with permission in an easy way and be sure i
 
   @javascript @local @development @staging @production
   Scenario: Check that Editor users can edit the Homepage which built by the Landing page (Layout Builder)
-    Given I am a logged in user with the "test_editor" user
+    Given I am a logged in user with the "Editor" user
      When I go to the homepage
       And I wait
      Then I should see "Welcome to Varbase"
@@ -75,7 +75,7 @@ So that the homepage can be changed with permission in an easy way and be sure i
 
   @javascript @local @development @staging @production
   Scenario: Check that Content Admin users can edit the Homepage which built by the Landing page (Layout Builder)
-    Given I am a logged in user with the "test_content_admin" user
+    Given I am a logged in user with the "Content admin" user
      When I go to the homepage
       And I wait
      Then I should see "Welcome to Varbase"
@@ -93,7 +93,7 @@ So that the homepage can be changed with permission in an easy way and be sure i
 
   @javascript @local @development @staging @production
   Scenario: Check that SEO Admin users can edit the Homepage which built by the Landing page (Layout Builder)
-    Given I am a logged in user with the "test_seo_admin" user
+    Given I am a logged in user with the "SEO admin" user
      When I go to the homepage
       And I wait
      Then I should see "Welcome to Varbase"
@@ -111,7 +111,7 @@ So that the homepage can be changed with permission in an easy way and be sure i
 
   @javascript @local @development @staging @production
   Scenario: Check that Site Admin users can edit the Homepage which built by the Landing page (Layout Builder)
-    Given I am a logged in user with the "test_site_admin" user
+    Given I am a logged in user with the "Site admin" user
      When I go to the homepage
       And I wait
      Then I should see "Welcome to Varbase"

tests/features/varbase/step2-apply-tests/05-content-management/05-02-entityqueue-tasks-for-content-types.feature → tests/features/varbase/05-content-management/05-02-entityqueue-tasks-for-content-types.feature

@@ -5,7 +5,7 @@ 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
-  Given I am a logged in user with the "test_super_admin" user
+  Given I am a logged in user with the "Super admin" user
    When I go to "/node/add/test_content"
     And I wait
    Then I should see "Create Test Content"

tests/features/varbase/step2-apply-tests/05-content-management/05-03-add-hero-slider-to-entityqueue-using-entityqueue-form-widget.feature → tests/features/varbase/05-content-management/05-03-add-hero-slider-to-entityqueue-using-entityqueue-form-widget.feature

@@ -4,7 +4,7 @@ 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
-    Given I am a logged in user with the "test_site_admin" user
+    Given I am a logged in user with the "Site admin" user
      When I go to "/media/add/image"
       And I wait
      Then I should see "Allowed types: png gif jpg jpeg."
@@ -23,7 +23,7 @@ I want to be able to add and remove entities to any allowed entity queue.
 
   @javascript @local @development @staging @production
   Scenario: Add a Test hero sliders to the heroslider entity queue them remove them
-    Given I am a logged in user with the "test_super_admin" user
+    Given I am a logged in user with the "Super admin" user
 
      # Add the "Test hero slier #1" content and to the hero slider queue.
      When I go to "/node/add/varbase_heroslider_media"

tests/features/varbase/step2-apply-tests/05-content-management/05-04-cloning-content-and-entities.feature → tests/features/varbase/05-content-management/05-04-cloning-content-and-entities.feature

@@ -4,7 +4,7 @@ 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 (Paragraphs)
-    Given I am a logged in user with the "test_site_admin" user
+    Given I am a logged in user with the "Site admin" user
      When I go to "/node/add/landing_page"
       And I wait
       And I fill in "Test Clone landing page" for "Title"
@@ -47,7 +47,7 @@ I want to be able to clone an entity.
 
   @javascript @local @development
   Scenario: Check if a user with a permission deleted a cloned entity the original will not affected
-    Given I am a logged in user with the "test_super_admin" user
+    Given I am a logged in user with the "Super admin" user
      When I go to "/admin/content"
       And I wait
      Then I should see "Content"

tests/features/varbase/step2-apply-tests/05-content-management/05-05-embed-existing-media-image-library.feature → tests/features/varbase/05-content-management/05-05-embed-existing-media-image-library.feature

@@ -4,7 +4,7 @@ I want to be able to embed existing files from the library of files in the CKEdi
 So that it will show up under that rich text field without having to upload the image for each content
 
   Background:
-    Given I am a logged in user with the "test_site_admin" user
+    Given I am a logged in user with the "Site admin" user
 
   # Create the Basic page and upload the file to the library before the test case.
   # ----------------------------------------------------------------------------
@@ -19,7 +19,7 @@ So that it will show up under that rich text field without having to upload the
        And I wait
       Then I should see "Basic page Test Basic page to embed existing files has been created."
 
-   @local @development @staging @production
+   @javascript @local @development @staging @production
    Scenario: Upload the  Embed Flag Earth file
       When I go to "/media/add/image"
        And I wait
@@ -35,55 +35,3 @@ So that it will show up under that rich text field without having to upload the
        And I press the "Save" button
        And I wait
       Then I should see "Embed Flag Earth"
-  #-----------------------------------------------------------------------------
-
-#  @javascript @local @development @staging @production
-#  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"
-#     When I fill in "Test Basic page to embed existing files" for "Title"
-#      And I press the "Filter" button
-#      And I wait
-#     Then I should see "Test Basic page to embed existing files"
-#     When I click "Edit" in the "Test Basic page to embed existing files" row
-#      And I wait
-#      And I wait for 5 seconds
-#     Then I should see "Edit Basic page Test Basic page to embed existing files"
-#     When I move focus to "Body" rich text editor field
-#      And I click the editor media browser command button
-#      And I wait
-#      And I wait for AJAX to finish
-#      And I wait
-#      And I wait for 5 seconds
-#     Then the editor media browser should be open
-#     When I switch to iframe "entity_browser_iframe_editor_media_browser"
-#      And I fill in "Embed Flag Earth" for "edit-name"
-#      And I press the "Search" button
-#      And I wait for AJAX to finish
-#     Then I should see image with the "Embed Flag Earth all earth in space" title text
-#     When I double click on the image with the "Embed Flag Earth all earth in space" title text
-#      And wait max of 5s
-#      And I wait for AJAX to finish
-#      And wait max of 5s
-#      And I switch to main frame
-#      And I wait for AJAX to finish
-#      And wait max of 5s
-#      And I fill in "Embed Flag Earth custom Caption text" for "Caption"
-#      And I fill in "Embed Flag Earth custom Alt text" for "Alternate text"
-#     When I click "Embed" in the "button" element with the "class" attribute set to "js-form-submit form-submit"
-#      And I wait for AJAX to finish
-#      And I select "published" from "edit-moderation-state-0-state"
-#      And I press the "Save" button
-#      And I wait
-#     Then I should see "Basic page Test Basic page to embed existing files has been updated."
-#     When I go to "/admin/content"
-#      And I wait
-#     Then I should see "Content"
-#     When I fill in "Test Basic page to embed existing files" for "Title"
-#      And I press the "Filter" button
-#      And I wait
-#     Then I should see "Test Basic page to embed existing files"
-#     When I click "Test Basic page to embed existing files"
-#      And I wait
-#     Then I should see image with the "Embed Flag Earth all earth in space" title text

tests/features/varbase/step2-apply-tests/05-content-management/05-06-easy-linking-internal-content-searching-content-by-its-titles.feature → tests/features/varbase/05-content-management/05-06-easy-linking-internal-content-searching-content-by-its-titles.feature

@@ -5,7 +5,7 @@ So that will ease the work of adding internal links in the rich text editor fiel
 
   @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
-    Given I am a logged in user with the "test_site_admin" user
+    Given I am a logged in user with the "Site admin" user
      When I go to "/node/add/page"
       And I wait
      Then I should see "Create Basic page"
@@ -19,7 +19,7 @@ So that will ease the work of adding internal links in the rich text editor fiel
 
   @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
-    Given I am a logged in user with the "test_site_admin" user
+    Given I am a logged in user with the "Site admin" user
      When I go to "/node/add/page"
       And I wait
      Then I should see "Create Basic page"

tests/features/varbase/README.md

 # Varbase Gherkin features
 
-A list of features, and scenarios to have a full test over Varbase 9.1.x
+A list of features, and scenarios to have a full test over Varbase
 
 If you want to run all Gherkin Features over a new Varbase site.
 You will need to create the list of Testing users, Arabic
@@ -17,87 +17,5 @@ If you want to run the test in steps, if you are not interested in the
 initialization and cleaning up after the test.
 
 ```
-  $ ../../../bin/behat tests/features/varbase/step1-init-tests
-  $ ../../../bin/behat tests/features/varbase/step2-apply-tests
-  $ ../../../bin/behat tests/features/varbase/step3-cleanup-tests
+  $ ../../../bin/behat tests/features/varbase
 ```
-
-
-## List of features in the step 1 init tests:
---------------------------------------------------------------------------------
-
-* 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' }
-test_content_admin: { email: 'content.admin.test@vardot.com', password: 'dD.123123ddd' }
-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
-
-## List of Features in the step 2 apply 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
-```
-test_authenticated
-test_editor
-test_content_admin
-test_seo_admin
-test_site_admin
-test_super_admin
-```
-
-* Feature: Delete Arabic language from the system
-* Feature: Cleanup after [entityqueue] module tests
-* Feature: Cleanup leftover media from the Media Library

tests/features/varbase/step1-init-tests/README.md

-# Varbase Gherkin features
-# List of features in step 1
-# Initialization of tests
-
-* 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' }
-test_content_admin: { email: 'content.admin.test@vardot.com', password: 'dD.123123ddd' }
-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/step2-apply-tests/README.md

-# Varbase Gherkin features
-# Apply tests
-# List of Features in the step 2
-
-
-### 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

tests/features/varbase/step1-init-tests/01-create-default-testing-users.feature → tests/tools/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' }
-# test_content_admin: { email: 'content.admin.test@vardot.com', password: 'dD.123123ddd' }
-# 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' }
+# Normal user: { email: 'test.authenticated@vardot.com', password: 'dD.123123ddd' }
+# Editor: { email: 'test.editor@vardot.com', password: 'dD.123123ddd' }
+# Content admin: { email: 'test.content_admin@vardot.com', password: 'dD.123123ddd' }
+# SEO admin: { email: 'test.seo_admin@vardot.com', password: 'dD.123123ddd' }
+# Site admin: { email: 'test.site_admin@vardot.com', password: 'dD.123123ddd' }
+# Super admin: { email: 'test.super_admin@vardot.com', password: 'dD.123123ddd' }
 
   Background:
     Given I am a logged in user with the "webmaster" user
 
-  @init @tools @local @development @staging
-  Scenario: Create the test_authenticated user
+  @javascript @init @tools @local @development @staging
+  Scenario: Create the Normal user user
      When I go to "/admin/people/create"
       And I wait
      Then I should see "Add user"
-     When I fill in "authenticated.test@vardot.com" for "Email address"
-      And I fill in "test_authenticated" for "Username"
+     When I fill in "test.authenticated@vardot.com" for "Email address"
+      And I fill in "Normal user" for "Username"
       And I fill in "dD.123123ddd" for "Password"
       And I fill in "dD.123123ddd" for "Confirm password"
       And I press "Create new account"
       And I wait
-     Then I should not see "The name test_authenticated is already taken."
+     Then I should not see "The name Normal user is already taken."
 
-  @init @tools @local @development @staging
-  Scenario: Create the test_editor user
+  @javascript @init @tools @local @development @staging
+  Scenario: Create the Editor user
      When I go to "/admin/people/create"
       And I wait
      Then I should see "Add user"
-     When I fill in "editor.test@vardot.com" for "Email address"
-      And I fill in "test_editor" for "Username"
+     When I fill in "test.editor@vardot.com" for "Email address"
+      And I fill in "Editor" for "Username"
       And I fill in "dD.123123ddd" for "Password"
       And I fill in "dD.123123ddd" for "Confirm password"
       And I check the box "Editor"
       And I press "Create new account"
       And I wait
-     Then I should not see "The name test_editor is already taken."
+     Then I should not see "The name Editor is already taken."
 
-  @init @tools @local @development @staging
-  Scenario: Create the test_content_admin user
+  @javascript @init @tools @local @development @staging
+  Scenario: Create the Content admin user
      When I go to "/admin/people/create"
       And I wait
      Then I should see "Add user"
-     When I fill in "content.admin.test@vardot.com" for "Email address"
-      And I fill in "test_content_admin" for "Username"
+     When I fill in "test.content_admin@vardot.com" for "Email address"
+      And I fill in "Content admin" for "Username"
       And I fill in "dD.123123ddd" for "Password"
       And I fill in "dD.123123ddd" for "Confirm password"
       And I check the box "Content Admin"
       And I press "Create new account"
       And I wait
-     Then I should not see "The name test_content_admin is already taken."
+     Then I should not see "The name Content admin is already taken."
 
-  @init @tools @local @development @staging
-  Scenario: Create the test_seo_admin user
+  @javascript @init @tools @local @development @staging
+  Scenario: Create the SEO admin user
      When I go to "/admin/people/create"
       And I wait
      Then I should see "Add user"
-     When I fill in "seo.admin.test@vardot.com" for "Email address"
-      And I fill in "test_seo_admin" for "Username"
+     When I fill in "test.seo_admin@vardot.com" for "Email address"
+      And I fill in "SEO admin" for "Username"
       And I fill in "dD.123123ddd" for "Password"
       And I fill in "dD.123123ddd" for "Confirm password"
       And I check the box "SEO Admin"
       And I press "Create new account"
       And I wait
-     Then I should not see "The name test_seo_admin is already taken."
+     Then I should not see "The name SEO admin is already taken."
 
-  @init @tools @local @development @staging
-  Scenario: Create the test_site_admin user
+  @javascript @init @tools @local @development @staging
+  Scenario: Create the Site admin user
      When I go to "/admin/people/create"
       And I wait
      Then I should see "Add user"
-     When I fill in "site.admin.test@vardot.com" for "Email address"
-      And I fill in "test_site_admin" for "Username"
+     When I fill in "test.site_admin@vardot.com" for "Email address"
+      And I fill in "Site admin" for "Username"
       And I fill in "dD.123123ddd" for "Password"
       And I fill in "dD.123123ddd" for "Confirm password"
       And I check the box "Site Admin"
       And I press "Create new account"
       And I wait
-     Then I should not see "The name test_site_admin is already taken."
+     Then I should not see "The name Site admin is already taken."
 
-  @init @tools @local @development @staging
-  Scenario: Create the test_super_admin user
+  @javascript @init @tools @local @development @staging
+  Scenario: Create the Super admin user
      When I go to "/admin/people/create"
       And I wait
      Then I should see "Add user"
-     When I fill in "super.admin.test@vardot.com" for "Email address"
-      And I fill in "test_super_admin" for "Username"
+     When I fill in "test.super_admin@vardot.com" for "Email address"
+      And I fill in "Super admin" for "Username"
       And I fill in "dD.123123ddd" for "Password"
       And I fill in "dD.123123ddd" for "Confirm password"
       And I check the box "Super Admin"
       And I press "Create new account"
       And I wait
-     Then I should not see "The name test_super_admin is already taken."
+     Then I should not see "The name Super admin is already taken."

tests/features/varbase/step1-init-tests/02-add-arabic.feature → tests/tools/step1-init-tests/02-add-arabic.feature

 Feature: Add Arabic language if we do not have it to languages in the system
 
-  @init @tools @local @development @staging @arabic
+  @javascript @init @tools @local @development @staging @arabic
   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"

tests/tools/step1-init-tests/README.md

+# Varbase Gherkin features
+# List of features in step 1
+# Initialization of tests
+
+Moved to tests/tools
+

tests/features/varbase/step3-cleanup-tests/01-delete-default-testing-users.feature → tests/tools/step3-cleanup-tests/01-delete-default-testing-users.feature

 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' }
-# test_content_admin: { email: 'content.admin.test@vardot.com', password: 'dD.123123ddd' }
-# 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' }
+# Normal user: { email: 'test.authenticated@vardot.com', password: 'dD.123123ddd' }
+# Editor: { email: 'test.editor@vardot.com', password: 'dD.123123ddd' }
+# Content admin: { email: 'test.content_admin@vardot.com', password: 'dD.123123ddd' }
+# SEO admin: { email: 'test.seo_admin@vardot.com', password: 'dD.123123ddd' }
+# Site admin: { email: 'test.site_admin@vardot.com', password: 'dD.123123ddd' }
+# Super admin: { email: 'test.super_admin@vardot.com', password: 'dD.123123ddd' }
 
   @javascript @cleanup @tools @local @development @staging
   Scenario: Delete default testing users.
@@ -13,12 +13,12 @@ Feature: Delete default testing users
      When I go to "/admin/people"
       And I wait
      Then I should see "People"
-     When I check the box "test_authenticated"
-      And I check the box "test_editor"
-      And I check the box "test_content_admin"
-      And I check the box "test_seo_admin"
-      And I check the box "test_site_admin"
-      And I check the box "test_super_admin"
+     When I check the box "Normal user"
+      And I check the box "Editor"
+      And I check the box "Content admin"
+      And I check the box "SEO admin"
+      And I check the box "Site admin"
+      And I check the box "Super admin"
       And I select "Cancel the selected user accounts" from "action"
      When I press "Apply to selected items"
       And I wait