@vardot/varbase-e2e 2.0.0

package/tests/features/test--then--i-should-be-on-page.feature

@@ -0,0 +1,10 @@
+Feature: An example to ensure that you are on a specific page
+  As an anonymous user,
+  I want to ensure that I am on a specific page
+
+  Scenario: Ensure that you are on a specific page
+    Given I am on the homepage
+     When I go to "/about-us.html"
+     Then I should be on "/about-us.html"
+     When I move backward one page
+     Then I should be on homepage

package/tests/features/test--then--i-should-be-on-the-homepage.feature

@@ -0,0 +1,10 @@
+Feature: An example to ensure that you are on the homepage
+  As an anonymous user,
+  I want to ensure that I am on the homepage
+
+  Scenario: Ensure that you are on the homepage
+    Given I am on the homepage
+     When I go to "/about-us.html"
+      And I move backward one page
+      And I wait max of 3 seconds
+     Then I should be on the homepage

package/tests/features/test--then--i-should-not-see-an-element-by-attr.feature

@@ -0,0 +1,8 @@
+Feature: An example to ensure that a specific element is not visible on the current page by its attribute
+  As a user,
+  I want to ensure that when I'm on a particular page, I do not see a specific element identified by its attribute
+
+  Scenario: Ensure that a specific element is not visible based on its attribute
+    Given I am on "/test--then--i-should--see-text-in-element.html"
+     Then I should not see an "emailId" element by its "id" attr
+      And I should not see a "countryCss" element by attr

package/tests/features/test--then--i-should-not-see-an-element.feature

@@ -0,0 +1,8 @@
+Feature: An example to ensure that a specific element is not visible on the current page by its label
+  As a user,
+  I want to ensure that when I'm on a particular page, I do not see a specific element by its label
+
+  Scenario: Ensure to test that a specific element is not visible by its label
+    Given I am on "/test--then--i-should--see-text-in-element.html"
+     Then I should not see an "Eamil" element
+      And I should not see a "Country" element

package/tests/features/test--then--i-should-see-an-element-by-attr.feature

@@ -0,0 +1,8 @@
+Feature: An example to ensure visibility of a specific element on the current page by its attributes
+  As a user,
+  I want to make sure that when I'm on a particular page, I can see a specific element by its attributes
+
+  Scenario: Ensure visibility of a specific element by its attributes
+    Given I am on "/test--then--i-should--see-text-in-element.html"
+     Then I should see a "uname" element by its "id" attr
+      And I should see a "pwordcss" element by attr

package/tests/features/test--then--i-should-see-an-element.feature

@@ -0,0 +1,8 @@
+Feature: An example to ensure that a specific element is visible on the current page by its label
+  As a user,
+  I want to ensure that when I'm on a particular page, I can see a specific element by its label
+
+  Scenario: Check to test seeing for a specific element by its label
+    Given I am on "/test--then--i-should--see-text-in-element.html"
+     Then I should see a "Username" element
+      And I should see a "Password" element

package/tests/features/test--then--i-should-see-n-elements.feature

@@ -0,0 +1,24 @@
+Feature: Assert the exact number of elements matching a selector
+  As a tester,
+  I want to assert how many elements match a CSS selector
+  so that I can catch regressions in list lengths, card counts, and nav items.
+
+  Scenario: Count h1 headings on the homepage
+    Given I am on homepage
+     Then I should see 1 "h1" element
+
+  Scenario: Count list items inside the first list on the homepage
+    Given I am on homepage
+     Then I should see 13 "ul:first-of-type li" elements
+
+  Scenario: Expect zero matches for a missing selector
+    Given I am on homepage
+     Then I should see 0 ".does-not-exist" elements
+
+  Scenario: Pronoun variant — "we"
+    Given I am on homepage
+     Then we should see 1 "h1" element
+
+  Scenario: No pronoun
+    Given I am on homepage
+     Then should see 1 "h1" element

package/tests/features/test--then--i-should-see-text-in-table-row.feature

@@ -0,0 +1,96 @@
+Feature: Assert text visibility in table rows
+  As a test automation engineer
+  I want to verify text content within specific table rows
+  So that I can validate data accuracy and proper display in tables
+
+        Background:
+            Given I am on "/test--then--i-should-see-text-in-table-row.html"
+
+        Scenario: Verify employee information is displayed correctly
+             Then I should see "Admin" in the "John Smith" row
+              And I should see "john.smith@company.com" in the "John Smith" row
+              And I should see "Engineering" in the "John Smith" row
+              And I should see "Active" in the "John Smith" row
+              And I should see "$85,000" in the "John Smith" row
+
+        Scenario: Verify different employee roles are displayed
+             Then I should see "User" in the "Jane Doe" row
+              And I should see "Manager" in the "Bob Johnson" row
+              And I should see "User" in the "Alice Cooper" row
+              And I should not see "Admin" in the "Jane Doe" row
+              And I should not see "Admin" in the "Bob Johnson" row
+
+        Scenario: Verify employee status visibility
+             Then I should see "Active" in the "John Smith" row
+              And I should see "Active" in the "Jane Doe" row
+              And I should see "On Leave" in the "Bob Johnson" row
+              And I should see "Inactive" in the "Alice Cooper" row
+              And I should not see "Inactive" in the "John Smith" row
+              And I should not see "Active" in the "Alice Cooper" row
+
+        Scenario: Verify product inventory information
+             Then I should see "Wireless Headphones" in the "WH-2024-001" row
+              And I should see "$199.99" in the "Wireless Headphones" row
+              And I should see "150" in the "Wireless Headphones" row
+              And I should see "In Stock" in the "Wireless Headphones" row
+              And I should not see "Out of Stock" in the "Wireless Headphones" row
+
+        Scenario: Verify low stock and out of stock products
+             Then I should see "Low Stock" in the "Gaming Mouse" row
+              And I should see "5" in the "Gaming Mouse" row
+              And I should see "Out of Stock" in the "Office Chair" row
+              And I should see "0" in the "Office Chair" row
+              And I should not see "In Stock" in the "Gaming Mouse" row
+              And I should not see "In Stock" in the "Office Chair" row
+
+        Scenario: Verify order status information
+             Then I should see "Completed" in the "ORD-2024-001" row
+              And I should see "Michael Chen" in the "ORD-2024-001" row
+              And I should see "Processing" in the "ORD-2024-002" row
+              And I should see "Sarah Wilson" in the "ORD-2024-002" row
+              And I should see "Cancelled" in the "ORD-2024-003" row
+              And I should see "Shipped" in the "ORD-2024-004" row
+
+        Scenario: Verify negative assertions for order status
+             Then I should not see "Processing" in the "ORD-2024-001" row
+              And I should not see "Completed" in the "ORD-2024-002" row
+              And I should not see "Shipped" in the "ORD-2024-003" row
+              And I should not see "Cancelled" in the "ORD-2024-004" row
+
+        Scenario: Verify project information
+             Then I should see "Website Redesign" in the "John Smith" row
+              And I should see "75%" in the "Website Redesign" row
+              And I should see "High" in the "Website Redesign" row
+              And I should see "Mobile App" in the "Jane Doe" row
+              And I should see "45%" in the "Mobile App" row
+              And I should see "Medium" in the "Mobile App" row
+
+        Scenario: Verify project progress and priorities
+             Then I should see "90%" in the "API Integration" row
+              And I should see "High" in the "API Integration" row
+              And I should see "3 members" in the "API Integration" row
+              And I should not see "Low" in the "API Integration" row
+              And I should not see "100%" in the "API Integration" row
+
+        Scenario: Cross-table data verification
+             Then I should see "John Smith" in the "john.smith@company.com" row
+              And I should see "John Smith" in the "Website Redesign" row
+              And I should see "Jane Doe" in the "jane.doe@company.com" row
+              And I should see "Jane Doe" in the "Mobile App" row
+              And I should not see "Bob Johnson" in the "Website Redesign" row
+              And I should not see "Alice Cooper" in the "Mobile App" row
+
+        Scenario: Verify currency and numeric data
+             Then I should see "$199.99" in the "Wireless Headphones" row
+              And I should see "$79.99" in the "Gaming Mouse" row
+              And I should see "$299.99" in the "Office Chair" row
+              And I should see "$49.99" in the "Laptop Stand" row
+              And I should not see "$0.00" in the "Wireless Headphones" row
+              And I should not see "$999.99" in the "Gaming Mouse" row
+
+        Scenario: Verify date and timestamp information
+             Then I should see "2024-08-15" in the "ORD-2024-001" row
+              And I should see "2024-08-16" in the "ORD-2024-002" row
+              And I should see "2024-09-15" in the "Website Redesign" row
+              And I should see "2024-10-30" in the "Mobile App" row
+              And I should not see "2023-01-01" in the "ORD-2024-001" row

package/tests/features/test--then--print-current-url-and-response.feature

@@ -0,0 +1,21 @@
+Feature: Debug helpers — print current URL and last response HTML
+  As a tester,
+  I want to dump the current URL and page HTML to the console
+  so that I can diagnose failures without attaching a debugger.
+
+  Scenario: Print current URL
+    Given I am on homepage
+     Then print current URL
+
+  Scenario: Print last response HTML
+    Given I am on homepage
+     Then print last response
+
+  Scenario: Print both in the same scenario
+    Given I am on homepage
+     Then print current URL
+      And print last response
+
+  Scenario: Print current URL after navigating
+    Given I am on "/about-us.html"
+     Then print current URL

package/tests/features/test--then--the-checkbox-is-checked.feature

@@ -0,0 +1,18 @@
+Feature: An example of a test case for selecting a checkbox
+  As a tester,
+  I want to be able to check that the checkbox is checked or not
+
+  Scenario: Verify that the checkbox is checked
+    Given I am on "/test--then--the-checkbox-checked.html"
+     When I check "rememberMe"
+      And I check "PrivacyPolicy"
+      And I press "Register" by attr
+     Then the checkbox "#rememberMe" is checked
+      And I should see "Registration Done Successfully"
+
+  Scenario: Verify that the checkbox is not checked
+    Given I am on "/test--then--the-checkbox-checked.html"
+     When I check "PrivacyPolicy"
+      And I press "Register" by attr
+     Then the checkbox "#rememberMe" is not checked
+     Then I should see "Registration Done Successfully"

package/tests/features/test--then--the-checkbox-should-be-checked.feature

@@ -0,0 +1,16 @@
+Feature: An example to assert the selection of a checkbox
+  As an anonymous user,
+  I want to ensure that a specific checkbox is checked before submitting a particular action
+
+  Scenario: Ensure that the checkbox is checked
+    Given I am on "/test--then--the-checkbox-checked.html"
+     When I check "PrivacyPolicy"
+      And I press "Register" by attr
+     Then the checkbox "#PrivacyPolicy" should be checked
+      And I should see "Registration Done Successfully"
+
+  Scenario: Ensure that the checkbox is not checked
+    Given I am on "/test--then--the-checkbox-checked.html"
+     When I press "Register" by attr
+     Then the "#PrivacyPolicy" checkbox should not be checked
+      And I should see "Please check Agree to Privacy Policy"

package/tests/features/test--then--the-element-should-contain-cssproperty.feature

@@ -0,0 +1,9 @@
+Feature: An example to verify whether the element contains a specific expected CSS property.
+  As a developer,
+  I want to verify whether the element contains a specific expected CSS property.
+
+  Scenario: Verify whether the element contains a specific expected CSS property
+    Given I am on "/test--then--the-element-should_not-contain-cssproperty.html"
+     Then I should see a "body" element by attr
+     When I press "Submit"
+     Then the "body" element should contain "background-color:white;"

package/tests/features/test--then--the-element-should-not-contain-cssproperty.feature

@@ -0,0 +1,10 @@
+Feature: An example to verify whether the element does not contain a specific expected CSS property.
+  As a developer,
+  I want to verify whether the element does not contain a specific expected CSS property.
+
+  Scenario: Verify whether the element does not contain a certain CSS property
+    Given I am on "/test--then--the-element-should_not-contain-cssproperty.html"
+     Then I should see a "body" element by attr
+     When I press "Submit"
+     Then the "#uname" element should not contain "border:solid 5px red;"
+      And the "pword" element should not contain "font-size: 28px;"

package/tests/features/test--then--the-field-should-contain-value.feature

@@ -0,0 +1,11 @@
+Feature: An example to verify whether the field contains a specific value identified by its element label
+  As a tester,
+  I want to verify whether the field has a specific value based on its element label
+
+  Scenario: Verify that the field has a particular value based on its element label
+    Given I am on "/test--then--i-should--not--see-text-in-element.html"
+      And I fill in "Username" with "user1"
+     Then the "Username" field should contain "user1"
+     When I press "Reset" by attr
+      And I fill in "Username" with "user2"
+     Then the "Username" field should contain "user2"

package/tests/features/test--then--the-response-should-contain.feature

@@ -0,0 +1,11 @@
+Feature: An example to ensure that the response page contains specific text
+  As a tester,
+  I want to navigate to a page to verify whether it contains specific text
+
+  Scenario: Ensure that the response page contains specific text
+    Given I am on the homepage
+     Then the response should contain "Welcome to the homepage"
+
+  Scenario: Ensure that the response page does not contain specific text
+    Given I am on the homepage
+     Then the response should not contain "Access denied"

package/tests/features/test--then--the-response-status-code-should-be.feature

@@ -0,0 +1,31 @@
+Feature: An example to check the status code of a page response
+  As a tester,
+  I want to be able to check the status code of a page response
+
+  Scenario: Check the response status code for a non-existing page
+    Given I am on the homepage
+     When I go to "/not-existing-page.html"
+      And I wait max of 2 seconds
+     Then the response status code should be 404
+      And the response status code should not be 200
+
+  Scenario: Check the response status code for an existing page
+    Given I am on the homepage
+     When I go to "/existing-page.html"
+      And I wait max of 2 seconds
+     Then the response status code should not be 404
+      And the response status code should be 200
+
+  Scenario: Check the response status code for an API that returns a JSON format
+    Given I am on the homepage
+     When I go to "/example-api.json"
+      And I wait max of 2 seconds
+     Then the response status code should not be 404
+      And the response status code should be 200
+
+  Scenario: Check the response status code for a parameter in the API that returns JSON format
+    Given I am on the homepage
+     When I go to "/example-api.json?include=author"
+      And I wait max of 2 seconds
+     Then the response status code should not be 404
+      And the response status code should be 200

package/tests/features/test--then--the-url-should-match.feature

@@ -0,0 +1,7 @@
+Feature: An example of checking for matching URLs based on a specific pattern
+  As a tester,
+  I want to ensure that the current page path matches a specific pattern
+
+  Scenario: Ensure that the current page path matches the URL pattern that uses dashes between words
+    Given I am on "/test-acceptable-url-path.html"
+     Then the url should match "(https?:\/\/)?([a-zA-Z0-9-]+\.)*[a-zA-Z0-9-]+\.[a-zA-Z]{2,}(:\d+)?(\/[^?#\s_]+)?(\?[^#\s_]+)?(#.*)?"

package/tests/features/test--then-the-link-should-contain-by-attribute.feature

@@ -0,0 +1,18 @@
+Feature: An example of checking the href attribute of a link element to see if it contains a specific URL, which is found by its attributes.
+  As a tester,
+  I want to be able to check link href if contain a specific URL found by its attributes
+
+  Scenario: Verify that the link contains "about" by its direct id, class attribute
+    Given I am on "/test--then--the-link-should-contain.html"
+     Then the "#aboutUsid" link should contain "about" by attr
+      And the ".contactUs" link should contain "/contact-" by attr
+      
+  Scenario: Verify that the link contains "contact-" by its id, class attribute
+    Given I am on "/test--then--the-link-should-contain.html"
+     Then the "contactUsid" link should contain "/contact-" by its "id" attribute
+      And the "aboutUs" link should contain "about" by its "class" attribute
+
+  Scenario: Verify that the link contains "about" by its "Title" attribute
+    Given I am on "/test--then--the-link-should-contain.html"
+     Then the "aboutUsTitle" link should contain "about-us" by attr
+      And the "aboutUsTitle" link should contain "about-us" by its "title" attribute

package/tests/features/test--then-the-link-should-contain.feature

@@ -0,0 +1,7 @@
+Feature: An example of checking the href attribute of a link element to see if it contains a specific text.
+  As a tester,
+  I want to be able to check link href if contain a specific text
+
+  Scenario: Verify that the link contains "about"
+    Given I am on "/test--then--the-link-should-contain.html"
+     Then the "About us" link should contain "about"

package/tests/features/test--when--i-additionally-select.feature

@@ -0,0 +1,30 @@
+Feature: Add an option to a multi-select without clearing existing selection
+  As a tester,
+  I want to build up a multi-select selection across multiple steps
+  so that I can test <select multiple> workflows one option at a time.
+
+  Scenario: Add two colors to an empty Colors multi-select
+    Given I am on "/test--when--i-additionally-select.html"
+     When I additionally select "Red" from "Colors"
+      And I additionally select "Blue" from "Colors"
+
+  Scenario: Start with one, then add two more
+    Given I am on "/test--when--i-additionally-select.html"
+     When I select "Red" from "Colors"
+      And I additionally select "Blue" from "Colors"
+      And I additionally select "Green" from "Colors"
+
+  Scenario: Pronoun variant — "we"
+    Given I am on "/test--when--i-additionally-select.html"
+     When we additionally select "Red" from "Colors"
+      And we additionally select "Yellow" from "Colors"
+
+  Scenario: No pronoun
+    Given I am on "/test--when--i-additionally-select.html"
+     When additionally select "Admin" from "Roles"
+      And additionally select "Editor" from "Roles"
+
+  Scenario: Multi-select on a second select on the same page
+    Given I am on "/test--when--i-additionally-select.html"
+     When I additionally select "Admin" from "Roles"
+      And I additionally select "Viewer" from "Roles"

package/tests/features/test--when--i-attach-file-to-feild.feature

@@ -0,0 +1,9 @@
+Feature: An example of checking the attachment of a file to a field
+  As a tester,
+  I want to be able to attach a file (e.g., images) to a field
+
+  Scenario: Checking the attachment of an image to a field
+    Given I am on "/test--when--i-attach-file-to-feild.html"
+     When I attach the file "vardot.png" to "#fileUpload"
+      And I press "Submit" by attr
+      And I wait 2 second

package/tests/features/test--when--i-check-checkbox.feature

@@ -0,0 +1,21 @@
+Feature: An example of checking and unchecking a checkbox
+  As a tester,
+  I want to be able to check and uncheck a checkbox
+
+  Scenario: Implementing the ability to check and uncheck a checkbox
+    Given I am on "/test--when--i-check-uncheck-checkbox.html"
+     When I check "bike"
+      And I check "car"
+      And I press "Submit" by "value" attr
+     Then I should see "You have a Bike Car"
+     When I check "van"
+      And I press "Submit" by "value" attr
+     Then I should see "You have a Bike Car Van"
+     When I uncheck "bike"
+      And I press "Submit" by "value" attr
+     Then I should see "You have a Car Van"
+     When I uncheck "car"
+     When I uncheck "van"
+      And I press "Submit" by "value" attr
+     Then I should see "You have a"
+

package/tests/features/test--when--i-click-link-by-attribute.feature

@@ -0,0 +1,21 @@
+Feature: An example of clicking a link by its attribute
+  As a tester,
+  I want to be able to click a link by its attribute
+
+  Scenario: Verify the action of clicking a link by targeting its ID attribute
+    Given I am on "/test--when--i-click-link.html"
+     When I click "#aboutUsid" by attr
+      And I wait max of 2 seconds
+     Then I should see "About Us"
+
+  Scenario: Verify the action of clicking a link by its ID attribute
+    Given I am on "/test--when--i-click-link.html"
+     When I click "aboutUsid" by its "id" attribute
+      And I wait max of 2 seconds
+     Then I should see "About Us"
+
+  Scenario: Verify the action of clicking a link by its class attribute
+    Given I am on "/test--when--i-click-link.html"
+     When I click "aboutUs" by "class" attr
+      And I wait max of 2 seconds
+     Then I should see "About Us"

package/tests/features/test--when--i-click-link.feature

@@ -0,0 +1,9 @@
+Feature: An example of clicking a link by its text
+  As a tester,
+  I want to be able to click a link based on its text
+
+  Scenario: Verify clicking a link by its text
+    Given I am on "/test--when--i-click-link.html"
+     When I click "About us link"
+      And I wait max of 2 seconds
+     Then I should see "About Us"

package/tests/features/test--when--i-click-text-in-table-row.feature

@@ -0,0 +1,37 @@
+Feature: Click specific text in table rows
+  As a test automation engineer
+  I want to be able to click on specific text within table rows
+  So that I can interact with table actions based on row content
+
+     Background:
+       Given I am on "/test--when--i-click-text-in-table-row.html"
+
+       Scenario: Click Edit button in John Smith row
+         When I click "Edit" in the "John Smith" row
+         Then I should see "Performed (edit) action on (John Smith)" in the "#action-message" element by attr
+
+        Scenario: Click View Details button in Jane Doe row
+          When I click "View Details" in the "Jane Doe" row
+          Then I should see "Performed (view) action on (Jane Doe)" in the "#action-message" element by attr
+
+        Scenario: Click Delete button in Bob Johnson row
+          When I click "Delete" in the "Bob Johnson" row
+          Then I should see "Performed (delete) action on (Bob Johnson)" in the "#action-message" element by attr
+
+        Scenario: Click Download link in Product A row
+          When I click "Download" in the "Product A" row
+          Then I should see "Performed (download) action on (Product A)" in the "#action-message" element by attr
+
+        Scenario: Click View Details in Order #12345 row
+          When I click "View Details" in the "Order #12345" row
+          Then I should see "Performed (view) action on (Order #12345)" in the "#action-message" element by attr
+
+        Scenario: Click Track in Order #67890 row
+          When I click "Track" in the "Order #67890" row
+          Then I should see "Performed (track) action on (Order #67890)" in the "#action-message" element by attr
+
+        Scenario: Multiple table interaction
+          When I click "Edit" in the "John Smith" row
+           And I wait 1 second
+           And I click "Download" in the "Product B" row
+          Then I should see "Performed (download) action on (Product B)" in the "#action-message" element by attr

package/tests/features/test--when--i-fill-in-by-attr.feature

@@ -0,0 +1,31 @@
+Feature: An example of filling an input textbox with a value using its attributes.
+  As a tester,
+  I want to fill an input field with a value using its attributes.
+
+  Scenario: Fill in the input field using its ID and class attributes.
+    Given I am on "/test--when--i-fill-in.html"
+     When I fill in "#uname" with "John Smith" by attr
+      And I fill in "pwordcss" with "1234" by its "class" attr
+     When I press "Login"
+     Then I should see "You enter Username: John Smith and Password: 1234"
+
+  Scenario: Fill in the input field using its placeholder attribute.
+    Given I am on "/test--when--i-fill-in.html"
+     When I fill in "Your full name" with "John Smith" by its "placeholder" attr
+      And I fill in "Your Password" with "1234" by attr
+     When I press "Login"
+     Then I should see "You enter Username: John Smith and Password: 1234"
+
+  Scenario: Specify a value, then identify and use the field's attribute to fill in the input field.
+    Given I am on "/test--when--i-fill-in.html"
+     When I fill in "John Smith" for "#uname" by attr
+     When I fill in "1234" for "pwordcss" by attr
+     When I press "Login"
+     Then I should see "You enter Username: John Smith and Password: 1234"
+  
+  Scenario: Fill in the input field with an empty value using its attribute.
+    Given I am on "/test--when--i-fill-in.html"
+     When I fill in "#uname" with: by attribute
+      And I fill in "password" with: by attr
+     When I press "Login" by attr
+     Then I should see "You enter Username: and Password:"

package/tests/features/test--when--i-fill-in-table-by-attr.feature

@@ -0,0 +1,19 @@
+Feature: An example of populating a table of input fields with values using their attributes.
+  As a tester,
+  I want to be able to fill input text fields with values using their attributes.
+
+  Scenario: Check the filling of a table of input fields using different attributes.
+    Given I am on "/test--when--i-fill-in.html"
+     When I fill in the following: by attr
+    | #uname   | John Smith |
+    | pwordcss | 1234       |
+     When I press "Login"
+     Then I should see "You enter Username: John Smith and Password: 1234"
+
+  Scenario: Check the filling of a table of input fields using the placeholder attribute.
+    Given I am on "/test--when--i-fill-in.html"
+     When I fill in the following: by its "placeholder" attribute
+    | Your full name | John Smith |
+    | Your Password  | 1234       |
+     When I press "Login"
+     Then I should see "You enter Username: John Smith and Password: 1234"

package/tests/features/test--when--i-fill-in.feature

@@ -0,0 +1,32 @@
+Feature: An example of filling an input textbox with a value using its label.
+  As a tester,
+  I want to be able to fill input text fields with values using their labels.
+
+  Scenario: Check filling an input field with a value using its label.
+    Given I am on "/test--when--i-fill-in.html"
+     When I fill in "Username" with "John Smith"
+     When I fill in "Password" with "1234"
+     When I press "Login"
+     Then I should see "You enter Username: John Smith and Password: 1234"
+
+  Scenario: Check filling in a value for an input field using its label.
+    Given I am on "/test--when--i-fill-in.html"
+     When I fill in "John Smith" for "Username"
+     When I fill in "1234" for "Password"
+     When I press "Login"
+     Then I should see "You enter Username: John Smith and Password: 1234"
+
+  Scenario: Check filling an input field with an empty value using its label.
+    Given I am on "/test--when--i-fill-in.html"
+     When I fill in "Username" with:
+      And I fill in "Password" with:
+     When I press "Login"
+     Then I should see "You enter Username: and Password:"
+     
+  Scenario: Check filling a table of input fields using their labels.
+    Given I am on "/test--when--i-fill-in.html"
+     When I fill in the following:
+    | Username | John Smith |
+    | Password | 1234       |
+     When I press "Login"
+     Then I should see "You enter Username: John Smith and Password: 1234"

package/tests/features/test--when--i-follow.feature

@@ -0,0 +1,22 @@
+Feature: Follow a link by its visible text
+  As a tester,
+  I want to follow a link by its visible anchor text
+  so that scenarios read like a user journey.
+
+  Scenario: Follow a link by its visible text
+    Given I am on "/test--when--i-click-link.html"
+     When I follow "About us link"
+      And I wait max of 2 seconds
+     Then I should see "About Us"
+
+  Scenario: Follow a link using the "we" pronoun
+    Given I am on "/test--when--i-click-link.html"
+     When we follow "About us link"
+      And I wait max of 2 seconds
+     Then I should see "About Us"
+
+  Scenario: Follow a link with no pronoun
+    Given I am on "/test--when--i-click-link.html"
+     When follow "About us link"
+      And I wait max of 2 seconds
+     Then I should see "About Us"

package/tests/features/test--when--i-go-to-homepage.feature

@@ -0,0 +1,9 @@
+Feature: An example of testing whether the user is on any page and then navigating to the homepage.
+  As a user,
+  I want to be able to navigate to the homepage from another page.
+  So that I can check the welcome message on the homepage.
+  
+  Scenario: Check if on the About Us page, then navigate to the homepage.
+    Given I am on "/about-us.html"
+     When I go to the homepage
+     Then I should see "Welcome to the homepage of the Varbase E2E Examples"

package/tests/features/test--when--i-move-forward-backward-one-page.feature

@@ -0,0 +1,14 @@
+Feature: An example of navigating forward and backward by one page.
+  As a tester,
+  I want to be able to navigate forward and backward by one page.
+
+  Scenario: Check to navigate forward and backward one page
+    Given I am on the homepage
+     When I go to "/about-us.html"
+     Then I should see "About Us"
+     When I move backward one page
+      And I wait max of 3 seconds
+     Then I should see "Welcome to the homepage of the Varbase E2E Examples"
+     When I move forward one page
+      And I wait max of 3 seconds
+     Then I should see "About Us"