@vardot/varbase-e2e 2.0.0

package/tests/features/modal-advanced-example.feature

@@ -0,0 +1,54 @@
+Feature: Modal Dialog - Advanced Scenarios
+  As a QA engineer testing complex modal behaviors
+  I want to handle various modal interactions
+  So that I can ensure comprehensive modal testing coverage
+
+  Background:
+    Given I am on "/test--modal-dialogs.html"
+
+  Scenario: Verify modal with specific title
+    When I click "show-welcome-modal" by attr
+    And I wait for modal to appear
+    Then I should see a modal with title "Welcome Message"
+    And I should see "Thank you for joining us!" in the modal
+    When I click "OK" in the modal
+    And I wait 1 second
+    Then I should not see a modal
+
+  Scenario: Handle settings modal with form
+    When I click ".open-settings" by attr
+    And I wait for the modal to appear
+    Then I should see the "settings-modal" modal
+    And I should see "User Settings" in the modal dialog
+    When I fill in "username" with "john_doe" by attr
+    And I fill in "email" with "john@example.com" by "id" attr
+    And I click "Save Changes" button in the modal
+    And I wait 1 second
+    Then I should see "Settings saved successfully" in the modal
+    When I click "Close" in the modal dialog
+    And I wait 1 second
+    Then I should not see a modal
+
+  Scenario: Verify contact modal does not contain error message
+    When I click "#contact-form-btn" by attr
+    And I wait for modal to appear
+    Then I should see a modal
+    And I should not see "Payment failed" in the modal
+    And I should see "Enter payment details" in the modal dialog
+    When I dismiss the modal
+    And I wait 1 second
+    Then I should not see the modal dialog
+
+  Scenario: Form submission in contact modal
+    When I click "#contact-form-btn" by attr
+    And I wait for the modal dialog to appear
+    Then I should see the modal
+    When I fill in the following: by attr
+      | contact-name    | Jane Smith            |
+      | contact-email   | jane@example.com      |
+      | contact-message | This is a test message|
+    And I click "Submit" button in the modal
+    And I wait 1 second
+    Then I should see "Message sent successfully" in the modal
+    And I wait for the modal to disappear
+    Then I should not see the modal

package/tests/features/modal-basic-example.feature

@@ -0,0 +1,42 @@
+Feature: Modal Dialog - Basic Interactions
+  As a user testing modal dialogs
+  I want to interact with modal windows
+  So that I can verify modal functionality works correctly
+
+  Background:
+    Given I am on "/test--modal-dialogs.html"
+
+  Scenario: Modal should not appear initially
+    Then I should not see a modal
+
+  Scenario: Open and verify modal visibility
+    When I click "show-modal" by attr
+    And I wait for the modal to appear
+    Then I should see a modal
+    And I should see "Welcome" in the modal
+    And I should see "This is a sample modal dialog" in the modal dialog
+
+  Scenario: Click confirm button in modal
+    When I click "trigger-modal" by attr
+    And I wait for the modal to appear
+    Then I should see a modal
+    When I click "Confirm" in the modal
+    And I wait 1 second
+    Then I should not see a modal
+
+  Scenario: Close modal using close button
+    When I click "#show-modal" by attr
+    And I wait for modal to appear
+    Then I should see the modal
+    When I close the modal
+    And I wait for the modal to disappear
+    Then I should not see the modal
+
+  Scenario: Verify specific modal by identifier
+    When I click "delete-btn" by attr
+    And I wait for modal to appear
+    Then I should see a "delete-confirmation-modal" modal
+    And I should see "Are you sure you want to delete this item?" in the modal
+    When I click "Cancel" button in the modal dialog
+    And I wait 1 second
+    Then I should not see the modal dialog

package/tests/features/modal-error-handling-example.feature

@@ -0,0 +1,37 @@
+Feature: Modal Dialog - Error Handling and Edge Cases
+  As a test automation engineer
+  I want to verify modal error states and edge cases
+  So that I can ensure robust modal functionality
+
+  Background:
+    Given I am on the "/test--modal-dialogs.html" page
+
+  Scenario: Confirm deletion with modal
+    When I click "Delete" in the "Project Alpha" row
+    And I wait for the modal to appear
+    Then I should see a modal
+    And I should see "Are you sure you want to delete Project Alpha?" in the modal
+    When I click "Yes, Delete" button in the modal
+    And I wait for the modal to disappear
+    Then I should not see a modal
+    And I should see "Project deleted successfully"
+
+  Scenario: Cancel deletion action dismisses modal
+    When I click "Delete" in the "Project Beta" row
+    And I wait for modal to appear
+    Then I should see the modal dialog
+    And I should see "Are you sure you want to delete Project Beta?" in the modal
+    When I click "Cancel" in the modal
+    And I wait 1 second
+    Then I should not see the modal dialog
+
+  Scenario: Delete confirmation modal content verification
+    When I click "delete-btn" by attr
+    And I wait for modal to appear
+    Then I should see a "delete-confirmation-modal" modal
+    And I should see "Are you sure you want to delete this item?" in the modal
+    And I should see "This action cannot be undone" in the modal dialog
+    And I should not see "Item has been deleted" in the modal
+    When I click "Cancel" button in the modal
+    And I wait 1 second
+    Then I should not see a modal

package/tests/features/modal.feature

@@ -0,0 +1,11 @@
+Feature: Modal step definitions
+
+  Scenario: Open and inspect modal
+    Given I am on "/modal.html"
+     Then I should not see the modal
+     When I click on the element "#open"
+      And I wait for the modal to appear
+     Then I should see the modal
+      And the modal should contain "Welcome modal text"
+      And the modal should not contain "Goodbye"
+     When I click on "#close-btn" in the modal

package/tests/features/path.feature

@@ -0,0 +1,16 @@
+Feature: Path step definitions
+
+  Scenario: Path and query parameter assertions
+    Given I am on "/path.html?lang=en&debug=1"
+     Then the path should be "/path.html"
+      And the path should not be "/wrong"
+      And current url should have the "lang" parameter
+      And current url should have the "lang" parameter with the "en" value
+      And current url should not have the "missing" parameter
+      And current url should not have the "lang" parameter with the "fr" value
+
+  Scenario: History navigation
+    Given I am on "/path.html"
+     When I go to "/element.html"
+      And I go back
+     Then the path should be "/path.html"

package/tests/features/response.feature

@@ -0,0 +1,8 @@
+Feature: Response step definitions
+
+  Scenario: Inspect response headers from main navigation
+    Given I am on the homepage
+     Then the response should contain the header "content-type"
+      And the response header "content-type" should contain the value "html"
+      And the response should not contain the header "x-fake-header"
+      And the response header "content-type" should not contain the value "application/json"

package/tests/features/responsive.feature

@@ -0,0 +1,10 @@
+Feature: Responsive step definitions
+
+  Scenario: Set viewport via breakpoints
+    Given I am on the homepage
+     When I set the viewport to the "mobile" breakpoint
+      And I set the viewport to the "tablet" breakpoint
+      And I set the viewport to the "desktop" breakpoint
+      And I set the viewport width to 800
+      And I set the viewport height to 600
+      And I set the viewport to 1024 by 768

package/tests/features/table.feature

@@ -0,0 +1,18 @@
+Feature: Table step definitions
+
+  Scenario: Inspect table content
+    Given I am on "/table.html"
+     Then the table "#users" should have 3 rows
+      And the table "#users" should have 3 columns
+      And the table "#users" should not be empty
+      And the table "#empty" should be empty
+      And the table "#users" should contain the following columns:
+        | Name |
+        | Role |
+        | Status |
+      And the table "#users" should be sorted by "Name" in "ascending" order
+      And the table "#users" should contain the following rows:
+        | Alice | Admin |
+      And the "Bob" row should contain the following:
+        | User |
+        | Active |

package/tests/features/test--given--i-am-an-anonymous-user.feature

@@ -0,0 +1,10 @@
+Feature: Given I am an anonymous user
+
+  Scenario: Anonymous user is redirected to homepage with no cookies
+    Given I am an anonymous user
+    Then the url should match "\/"
+
+  Scenario: Anonymous user cannot access a protected page
+    Given I am an anonymous user
+    When I go to "/account"
+    Then I should not be on the "/account" page

package/tests/features/test--given--i-am-on-homepage.feature

@@ -0,0 +1,16 @@
+Feature: An example of testing for being on the homepage.
+  As an anonymous user,
+  I want to be able to navigate to the homepage
+  so that I can check the welcome message on the homepage.
+  
+  Scenario: Ensure that you are on the homepage by using 'the' before the word 'homepage'.
+    Given I am on the homepage
+     Then I should see "Welcome to the homepage of the Varbase E2E Examples"
+
+  Scenario: Ensure that you are on the homepage without using 'the' before the word 'homepage'.
+    Given I am on homepage
+     Then I should see "Welcome to the homepage of the Varbase E2E Examples"
+
+  Scenario: Ensure that you are on the homepage without using 'the' before the word 'homepage' and using 'we' instead of 'I'.
+    Given we are on homepage
+     Then we should see "Welcome to the homepage of the Varbase E2E Examples"

package/tests/features/test--then--i-save-screenshot.feature

@@ -0,0 +1,33 @@
+Feature: Save screenshots to disk.
+  As a tester,
+  I want to capture screenshots at arbitrary points in my scenarios
+  so that I can review rendered pages and debug failures.
+
+  Background:
+    Given I am on homepage
+
+  Scenario: Save a screenshot at the current viewport size.
+    Then I save screenshot
+
+  Scenario: Save a full-page screenshot.
+    Then I save fullscreen screenshot
+
+  Scenario: Save a screenshot after resizing the viewport.
+    Then I save 1440 x 900 screenshot
+
+  Scenario: Save a full-page screenshot at a fixed viewport.
+    Then I save fullscreen 1200 x 800 screenshot
+
+  Scenario: Save a screenshot with an explicit filename.
+    Then I save screenshot with name "varbase-e2e-home.png"
+
+  Scenario: Save a full-page screenshot with an explicit filename.
+    Then I save fullscreen screenshot with name "varbase-e2e-home-full.png"
+
+  Scenario: Save a screenshot with filename tokens.
+    Then I save screenshot with name "{feature_file}_{step_line}_{datetime}.png"
+
+  @screenshots
+  Scenario: Auto-capture a screenshot after every step in a tagged scenario.
+    Given I am on "/about-us.html"
+     Then I should see "About Us"

package/tests/features/test--then--i-see-locator.feature

@@ -0,0 +1,320 @@
+Feature: Relative element positioning assertions and advanced selector system.
+  As a tester,
+  I want to assert that page components are positioned correctly relative to each other
+  and resolve elements via a named CSS/XPath selector registry
+  so that I can catch layout regressions without brittle pixel comparisons.
+
+  Background:
+    Given I am on homepage
+    And I define css selectors:
+      | heading  | h1              |
+      | subline  | h3              |
+      | list     | ul              |
+
+  # ---------------------------------------------------------------------------
+  # Breakpoints — cover all 7 configured sizes (pronoun variants too).
+  # ---------------------------------------------------------------------------
+  Scenario: Resize to xs breakpoint.
+    Given I am viewing the site on a xs screen
+    Then I see visible heading
+
+  Scenario: Resize to sm breakpoint.
+    Given I am viewing the site on a sm screen
+    Then I see visible heading
+
+  Scenario: Resize to md breakpoint.
+    Given I am viewing the site on a md device
+    Then I see visible heading
+
+  Scenario: Resize to lg breakpoint.
+    Given I am viewing the site on a lg screen
+    Then I see visible heading
+
+  Scenario: Resize to xl breakpoint (default).
+    Given I am viewing the site on a xl screen
+    Then I see visible heading
+
+  Scenario: Resize to xxl breakpoint.
+    Given I am viewing the site on a xxl screen
+    Then I see visible heading
+
+  Scenario: Resize to xxxl breakpoint using quoted name.
+    Given I am viewing the site on a "xxxl" screen
+    Then I see visible heading
+
+  Scenario: Resize using the "we are" pronoun variant.
+    Given we are viewing the site on a md screen
+    Then we see visible heading
+
+  Scenario: Resize using no pronoun at all.
+    Given viewing the site on a lg screen
+    Then I see visible heading
+
+  # ---------------------------------------------------------------------------
+  # Position assertions — above / below / left / right / inside / outside.
+  # ---------------------------------------------------------------------------
+  Scenario: Assert heading is above list.
+    Then I see heading above list
+
+  Scenario: Assert heading is above multiple targets.
+    Then I see heading above subline, list
+
+  Scenario: Assert list is below heading.
+    Then I see list below heading
+
+  Scenario: Assert chained above relations.
+    Then I see heading above subline
+    Then I see subline above list
+
+  Scenario: Assert heading is inside of body component.
+    Given I define css selectors:
+      | body | body |
+    Then I see heading inside of body
+
+  Scenario: Assert body outside of heading.
+    Given I define css selectors:
+      | body | body |
+    Then I see body outside of heading
+
+  Scenario: Pronoun variants on position assertions.
+    Then we see heading above list
+    Then see heading above list
+
+  # ---------------------------------------------------------------------------
+  # Visibility + hidden.
+  # ---------------------------------------------------------------------------
+  Scenario: Assert single component visible.
+    Then I see visible heading
+
+  Scenario: Assert multiple components visible.
+    Then I see visible heading, subline and list
+
+  Scenario: Assert hidden (don't see) with missing components.
+    Given I define css selectors:
+      | missing | #does-not-exist |
+    Then I don't see missing
+
+  Scenario: Pronoun variants on visibility.
+    Then we see visible heading
+    Then see visible heading
+
+  # ---------------------------------------------------------------------------
+  # Advanced selector registry — CSS + XPath.
+  # ---------------------------------------------------------------------------
+  Scenario: Register a named CSS selector at runtime.
+    When I add "page heading" selector for "h1" css selector
+    Then I see visible page heading
+
+  Scenario: Register a named XPath selector at runtime.
+    When I add "first heading" selector for "//h1[1]" xpath selector
+    Then I see visible first heading
+
+  Scenario: Register multiple selectors and use mix of components, css, xpath.
+    When I add "page heading" selector for "h1" css selector
+    And I add "third level" selector for "//h3[1]" xpath selector
+    Then I see visible page heading
+    And I see visible third level
+    And I see page heading above list
+
+  Scenario: Print registered CSS selectors.
+    When I add "page heading" selector for "h1" css selector
+    Then I print css selectors
+
+  Scenario: Print registered XPath selectors.
+    When I add "first heading" selector for "//h1[1]" xpath selector
+    Then I print xpath selectors
+
+  Scenario: Pronoun variants on selector registration.
+    When we add "nav item" selector for "nav a" css selector
+    And add "first para" selector for "//p[1]" xpath selector
+    Then we print css selectors
+    And we print xpath selectors
+
+  Scenario: Bulk define CSS selectors via data table.
+    Given I define css selectors:
+      | bulk heading | h1 |
+      | bulk subline | h3 |
+      | bulk list    | ul |
+    Then I see visible bulk heading, bulk subline, bulk list
+    And I see bulk heading above bulk list
+
+  Scenario: Bulk define XPath selectors via data table.
+    Given I define xpath selectors:
+      | xp heading | //h1[1] |
+      | xp subline | //h3[1] |
+      | xp list    | //ul[1] |
+    Then I see visible xp heading, xp subline, xp list
+    And I see xp heading above xp list
+
+  Scenario: Mix bulk CSS + bulk XPath in one scenario.
+    Given I define css selectors:
+      | mixed heading | h1 |
+    And I define xpath selectors:
+      | mixed first list | //ul[1] |
+    Then I see mixed heading above mixed first list
+
+  # ---------------------------------------------------------------------------
+  # Focus and text selection on input fields.
+  # ---------------------------------------------------------------------------
+  Scenario: Move focus to a field and assert focus.
+    Given I am on "/test--when--i-fill-in.html"
+    And I add "username" selector for "[name='username']" css selector
+    When I move focus to "username" field
+    Then I see username has focus
+
+  Scenario: Select all text in a field.
+    Given I am on "/test--when--i-fill-in.html"
+    And I add "username" selector for "[name='username']" css selector
+    And I fill in "username" with "varbase-e2e-tester"
+    When I select all text in "username" field
+    Then I see username has focus
+
+  Scenario: Select a character range in a field.
+    Given I am on "/test--when--i-fill-in.html"
+    And I fill in "username" with "varbase-e2e-tester"
+    When I select from 0 to 7 text in "username" field
+
+  Scenario: Select a substring inside a field.
+    Given I am on "/test--when--i-fill-in.html"
+    And I fill in "username" with "varbase-e2e-tester"
+    When I select "tester" text in "username" field
+
+  Scenario: Pronoun variants on focus + selection.
+    Given I am on "/test--when--i-fill-in.html"
+    And I fill in "username" with "varbase-e2e-tester"
+    When we move focus to "username" field
+    And we select all text in "username" field
+
+  # ---------------------------------------------------------------------------
+  # Click by named component.
+  # ---------------------------------------------------------------------------
+  Scenario: Click a registered component.
+    Given I define css selectors:
+      | first heading | h1 |
+    When I click first heading
+
+  Scenario: Click using "on" phrasing.
+    Given I define css selectors:
+      | first heading | h1 |
+    When I click on first heading
+
+  Scenario: Click pronoun variants.
+    Given I define css selectors:
+      | first heading | h1 |
+    When we click first heading
+    And click on first heading
+
+  # ---------------------------------------------------------------------------
+  # Advanced — selector file loading (JSON).
+  # ---------------------------------------------------------------------------
+  Scenario: Load selectors from a single JSON file.
+    When I add selectors from "homepage-selectors.json" file
+    Then I see visible homepage heading
+    And I see visible homepage first heading
+    And I print css selectors
+    And I print xpath selectors
+
+  Scenario: Load selectors from two JSON files (front-end + back-end).
+    When I add selectors from "front-end-selectors.json" file
+    And I add selectors from "back-end-selectors.json" file
+    Then I see visible page heading, admin heading
+    And I see visible first heading, admin first heading
+
+  Scenario: Loaded file selectors mix with components and inline registrations.
+    When I add selectors from "homepage-selectors.json" file
+    And I add "inline heading" selector for "h1" css selector
+    And I add "inline first heading" selector for "//h1[1]" xpath selector
+    Then I see visible homepage heading
+    And I see visible inline heading
+    And I see visible inline first heading
+    And I see heading above list
+    And I see homepage heading above list
+
+  # ---------------------------------------------------------------------------
+  # Advanced — resolver priority (components → css → xpath) with overrides.
+  # ---------------------------------------------------------------------------
+  Scenario: Component overrides a CSS registration of the same name.
+    When I add "shared" selector for "ul" css selector
+    And I define css selectors:
+      | shared | h1 |
+    Then I see visible shared
+    And I see shared above list
+
+  Scenario: CSS registration overrides a prior CSS registration of same name.
+    When I add "dynamic" selector for "h1" css selector
+    And I add "dynamic" selector for "ul" css selector
+    Then I see visible dynamic
+    And I see heading above dynamic
+
+  Scenario: XPath-only registration resolves via xpath= prefix.
+    When I add "first subline xp" selector for "//h3[1]" xpath selector
+    Then I see visible first subline xp
+
+  # ---------------------------------------------------------------------------
+  # Advanced — multi-subject, multi-target position dispatch.
+  # ---------------------------------------------------------------------------
+  Scenario: Multiple subjects, single target (above).
+    Then I see heading, subline above list
+
+  Scenario: Single subject, multiple targets with "and" + comma.
+    Then I see heading above subline, list
+
+  Scenario: Chain of position assertions covers layout order.
+    Then I see heading above subline, list
+    And I see subline above list
+    And I see list below subline, heading
+
+  # ---------------------------------------------------------------------------
+  # Advanced — inside / outside containment.
+  # ---------------------------------------------------------------------------
+  Scenario: Heading and list both inside body.
+    Given I define css selectors:
+      | body | body |
+    Then I see heading, list inside of body
+    And I see body outside of heading, list
+
+  # ---------------------------------------------------------------------------
+  # Advanced — "not over" negation (non-overlap).
+  # ---------------------------------------------------------------------------
+  Scenario: Block-level neighbours do not overlap.
+    Then I see heading not over list
+
+  # ---------------------------------------------------------------------------
+  # Advanced — breakpoint resize then layout reassert.
+  # ---------------------------------------------------------------------------
+  Scenario: After switching to xs, layout order still holds.
+    Given I am viewing the site on a xs screen
+    Then I see visible heading, subline, list
+    And I see heading above list
+
+  Scenario: Switch through multiple breakpoints in one scenario.
+    Given I am viewing the site on a xs screen
+    Then I see visible heading
+    Given I am viewing the site on a md screen
+    Then I see visible heading
+    Given I am viewing the site on a xl screen
+    Then I see visible heading
+    And I see heading above list
+    Given I am viewing the site on a xxxl screen
+    Then I see visible heading
+
+  # ---------------------------------------------------------------------------
+  # Advanced — click via xpath-registered selector.
+  # ---------------------------------------------------------------------------
+  Scenario: Click via an XPath-registered selector.
+    When I add "first heading xp" selector for "//h1[1]" xpath selector
+    And I click first heading xp
+
+  # ---------------------------------------------------------------------------
+  # Advanced — full input-field workflow (focus → select → re-fill).
+  # ---------------------------------------------------------------------------
+  Scenario: End-to-end field workflow — focus, select all, refill, partial select.
+    Given I am on "/test--when--i-fill-in.html"
+    And I add "username" selector for "[name='username']" css selector
+    And I fill in "username" with "varbase-e2e-initial"
+    When I move focus to "username" field
+    Then I see username has focus
+    When I select all text in "username" field
+    And I fill in "username" with "varbase-e2e-replacement-value"
+    And I select from 0 to 7 text in "username" field
+    And I select "replacement" text in "username" field

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

@@ -0,0 +1,13 @@
+Feature: An example to ensure that the input text does not contain a specific value based on its attribute
+  As a tester,
+  I want to ensure that the textbox does not contain a specific value based on its attributes.
+  
+  Scenario: Ensuring that a textbox does not contain a specific value based on its attributes.
+    Given I am on "/test--then--i-should--not--see-text-in-element.html"
+     When I fill in "Username" with "user1"
+      And I fill in "Password" with "1234"
+     Then I should see "user1" in the "Username" element
+     When I fill in "uname" with: by attr
+      And I fill in "Password" with:
+     Then I should not see "user1" in the "Username" element
+      And I should not see "1234" in the "pword" element by attr

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

@@ -0,0 +1,10 @@
+Feature: An example to ensure that the input text contain a specific value based on its attribute
+As a tester,
+I want to ensure that the textbox contain a specific value based on its attributes.
+
+  Scenario: Ensuring that a textbox contain a specific value based on its attributes.
+    Given I am on "/test--then--i-should--not--see-text-in-element.html"
+     When I fill in "Username" with "user1"
+      And I fill in "Password" with "1234"
+     Then I should see "user1" in the "uname" element by its "id" attr
+      And I should see "1234" in the "pwordcss" element by attr

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

@@ -0,0 +1,10 @@
+Feature: An example to ensure that the input text contain a specific value based on its label
+  As a tester,
+  I want to ensure thlabelat the textbox does not contain a specific value based on its label
+
+  Scenario: Ensuring that a textbox does not contain a specific value based on its label.
+    Given I am on "/test--then--i-should--not--see-text-in-element.html"
+     When I fill in "Username" with "user1"
+      And I fill in "Password" with "1234"
+     Then I should see "user1" in the "Username" element
+      And I should see "1234" in the "Password" element

package/tests/features/test--then--i-should--see-text-matching-pattern-in-element.feature

@@ -0,0 +1,13 @@
+Feature: An example of ensuring that a pattern matches the text in a specific element
+  As a developer,
+  I want to ensure that a pattern matches the text in a specific element.
+
+  Scenario: Ensuring that the text in an element matches the 12-hour time format pattern
+    Given I am on "/test--then--i-should--see-text-matching-pattern.html"
+      And I wait max of 3 seconds
+     Then I should see text matching "(((0[1-9])|(1[0-2])):([0-5])(0|5)\s(A|P|a|p)(M|m))" in the ".time" element
+
+  Scenario: Ensuring that the text in an element matches the DD/MM/YYYY or DD-MM-YYYY date format pattern
+    Given I am on "/test--then--i-should--see-text-matching-pattern.html"
+      And I wait max of 3 seconds
+     Then I should see text matching "(0?[1-9]|[12][0-9]|3[01])[\/\-](0?[1-9]|1[012])[\/\-]\d{4}" in the "#date" element

package/tests/features/test--then--i-should--see-text-matching-pattern.feature

@@ -0,0 +1,18 @@
+Feature: An example of ensuring that a pattern matches the text on a specific page.
+  As a developer,
+  I want to ensure that a pattern matches the text in a specific page.
+
+  Scenario: Ensure that there is a text matching the pattern of text starting with 'T' on a specific page
+    Given I am on "/test--then--i-should--see-text-matching-pattern.html"
+      And I wait max of 3 seconds
+     Then I should see text matching "^T\w+"
+
+  Scenario: Ensure that there is no text matching the pattern of text starting with 'O' on a specific page
+    Given I am on "/test--then--i-should--see-text-matching-pattern.html"
+      And I wait max of 3 seconds
+     Then I should not see text matching "^O\w+"
+
+  Scenario: Ensure that there is text matching the email pattern on a specific page
+    Given I am on "/test--then--i-should--see-text-matching-pattern.html"
+      And I wait max of 3 seconds
+     Then I should see text matching "[a-z0-9]+@[a-z]+\.[a-z]{2,3}"