@vardot/varbase-e2e 2.0.0

package/tests/features/api-step-definitions-individual.feature

@@ -0,0 +1,185 @@
+Feature: API Step Definitions Individual
+  As a developer,
+  I want to see individual examples of each API step definition
+  So that I can understand how to use each one.
+
+  # ======================
+  # SETUP STEP DEFINITIONS
+  # ======================
+
+  Scenario: Authentication Step
+    # Basic Authentication
+    Given I am authenticating as "admin" with "password123" password
+
+  Scenario: Base URL Setup
+    # Different ways to set base URL
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    # Alternative syntax:
+    # Given I set the API base URL to "https://api.example.com/v1"
+    # Given the base URL is "http://localhost:3000/api"
+
+  Scenario: Single Header Setup
+    # Different ways to set headers
+    Given I set header "Content-Type" with value "application/json"
+    # Alternative syntax:
+    # Given I set the header "Authorization" to "Bearer token123"
+    # Given the header "Accept" is "application/json"
+
+  Scenario: Multiple Headers Setup
+    Given I set the following headers:
+      | Content-Type  | application/json |
+      | Authorization | Bearer token123  |
+      | Accept        | application/json |
+
+  Scenario: Request Body with JSON String
+    Given I set the request body to '{"name": "John", "email": "john@example.com"}'
+
+  Scenario: Request Body with Table
+    Given I set the request body with:
+      | name  | John Doe           |
+      | email | john@example.com   |
+      | age   | 30                 |
+
+  Scenario: Placeholder Setup
+    Given I set placeholder "{{userId}}" to "123"
+    Given I set placeholder "{{baseUrl}}" to "https://api.example.com"
+
+  # ======================
+  # WHEN STEP DEFINITIONS (HTTP Requests)
+  # ======================
+
+  Scenario: Basic HTTP Requests
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    # Different HTTP methods
+    When I send a GET request to "/users"
+    When I send a POST request to "/posts" 
+    When I send a PUT request to "/users/1"
+    When I send a DELETE request to "/posts/1"
+    When I send a PATCH request to "/users/1"
+
+  Scenario: Request with Values Table
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    When I send a POST request to "/users" with values:
+      | name  | John Doe         |
+      | email | john@example.com |
+      | age   | 30               |
+
+  Scenario: Request with Body DocString
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    When I send a POST request to "/users" with body:
+      """
+      {
+        "name": "John Doe",
+        "email": "john@example.com"
+      }
+      """
+
+  Scenario: Request with Form Data
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    When I send a POST request to "/login" with form data:
+      """
+      username=admin
+      password=secret
+      remember=true
+      """
+
+  # ======================
+  # THEN STEP DEFINITIONS (Assertions)
+  # ======================
+
+  Scenario: Status Code Assertions
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    When I send a GET request to "/posts/1"
+    Then the API response code should be 200
+    # Alternative syntax:
+    # Then API response code should be 404
+
+  Scenario: Content Assertions
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    When I send a GET request to "/posts/1"
+    Then the API response should contain "userId"
+    Then the API response should not contain "password"
+    # Alternative syntax:
+    # Then API response should contain "John Doe"
+    # Then API response should not contain "failed"
+
+  Scenario: JSON Structure Assertions
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    When I send a GET request to "/posts/1"
+    Then the response should be valid JSON
+    Then the JSON response should have property "id"
+    Then the JSON response should not have property "password"
+    # Alternative syntax:
+    # Then the API response should be valid JSON
+    # Then the API response should contain property "user.email"
+    # Then the API response should not contain property "secret"
+
+  Scenario: JSON Property Value Assertions
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    When I send a GET request to "/posts/1"
+    Then the JSON property "userId" should be 1
+    Then the JSON property "id" equal to 1
+    # Alternative syntax:
+    # Then the JSON response should have "name" should be "John"
+    # Then the API response should have "active" equal to true
+
+  Scenario: JSON Content Assertion with DocString
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    And I set the request body to '{"title": "Test Post", "body": "Test content", "userId": 1}'
+    When I send a POST request to "/posts"
+    Then the API response should contain json:
+      """
+      {
+        "title": "Test Post",
+        "body": "Test content",
+        "userId": 1
+      }
+      """
+
+  Scenario: Header Assertions
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    When I send a GET request to "/posts/1"
+    Then the response header "Content-Type" should be "application/json"
+    # Alternative syntax:
+    # Then the header "Cache-Control" should contain "no-cache"
+
+  Scenario: Debug Step
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    When I send a GET request to "/posts/1"
+    Then print API response
+
+  # ======================
+  # COMPLETE WORKFLOW EXAMPLES
+  # ======================
+
+  Scenario: Complete CRUD Operations
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+    
+    # CREATE
+    And I set the request body to '{"title": "New Post", "body": "Post content", "userId": 1}'
+    When I send a POST request to "/posts"
+    Then the API response code should be 201
+    And the API response should contain "New Post"
+    
+    # READ
+    When I send a GET request to "/posts/1"
+    Then the API response code should be 200
+    And the JSON response should have property "title"
+    
+    # UPDATE
+    And I set the request body to '{"id": 1, "title": "Updated Post", "body": "Updated content", "userId": 1}'
+    When I send a PUT request to "/posts/1"
+    Then the API response code should be 200
+    
+    # DELETE
+    When I send a DELETE request to "/posts/1" 
+    Then the API response code should be 200
+
+  Scenario: Using Placeholders
+    Given I set placeholder "{{userId}}" to "1"
+    And I set placeholder "{{postTitle}}" to "Dynamic Title"
+    And the API base URL is "https://jsonplaceholder.typicode.com"
+    And I set the request body to '{"title": "{{postTitle}}", "body": "Content", "userId": {{userId}}}'
+    When I send a POST request to "/posts"
+    Then the API response code should be 201
+    And the API response should contain "Dynamic Title"

package/tests/features/complete-api-testing-examples.feature

@@ -0,0 +1,205 @@
+Feature: Complete API Testing Examples - All Step Definitions
+  As a developer,
+  I want to test all available API step definitions
+  So that I can verify comprehensive API testing capabilities.
+
+  Background:
+    Given the API base URL is "https://jsonplaceholder.typicode.com"
+
+  Scenario: Basic Authentication and Headers
+    Given I am authenticating as "admin" with "password123" password
+      And I set header "Content-Type" with value "application/json"
+      And I set header "Accept" with value "application/json"
+     When I send a GET request to "/posts/1"
+     Then the API response code should be 200
+
+  Scenario: Alternative Header Syntax
+    Given I set the header "Content-Type" to "application/json"
+      And the header "Accept" is "application/json"
+     When I send a GET request to "/posts/1"
+     Then the API response code should be 200
+
+  Scenario: Multiple Headers Using Table
+    Given I set the following headers:
+      | Content-Type  | application/json |
+      | Accept        | application/json |
+      | User-Agent    | VarbaseE2E/1.0   |
+    When I send a GET request to "/posts"
+    Then the API response code should be 200
+
+  Scenario: GET Request with Response Validation
+    When I send a GET request to "/posts/1"
+    Then the API response code should be 200
+    And the API response should contain "userId"
+    And the API response should contain "title"
+    And the API response should not contain "password"
+
+  Scenario: POST Request with JSON Body (String)
+    Given I set the request body to '{"title": "Test Post", "body": "This is a test post", "userId": 1}'
+    When I send a POST request to "/posts"
+    Then the API response code should be 201
+    And the API response should contain "Test Post"
+
+  Scenario: POST Request with Table Body
+    Given I set the request body with:
+      | title  | My New Post           |
+      | body   | This is the content   |
+      | userId | 1                     |
+    When I send a POST request to "/posts"
+    Then the API response code should be 201
+
+  Scenario: POST Request with Values Table
+    When I send a POST request to "/posts" with values:
+      | title  | Table Post            |
+      | body   | Created with table    |
+      | userId | 1                     |
+    Then the API response code should be 201
+    And the API response should contain "Table Post"
+
+  Scenario: POST Request with DocString Body
+    When I send a POST request to "/posts" with body:
+      """
+      {
+        "title": "DocString Post",
+        "body": "Created with docstring",
+        "userId": 1
+      }
+      """
+    Then the API response code should be 201
+    And the API response should contain "DocString Post"
+
+  Scenario: Form Data Request
+    When I send a POST request to "/posts" with form data:
+      """
+      title=Form Data Post
+      body=Created with form data
+      userId=1
+      """
+    Then the API response code should be 201
+
+  Scenario: PUT Request for Update
+    Given I set the request body to '{"id": 1, "title": "Updated Post", "body": "Updated content", "userId": 1}'
+    When I send a PUT request to "/posts/1"
+    Then the API response code should be 200
+    And the API response should contain "Updated Post"
+
+  Scenario: PATCH Request
+    Given I set the request body to '{"title": "Patched Title"}'
+    When I send a PATCH request to "/posts/1"
+    Then the API response code should be 200
+
+  Scenario: DELETE Request
+    When I send a DELETE request to "/posts/1"
+    Then the API response code should be 200
+
+  Scenario: JSON Response Structure Validation
+    When I send a GET request to "/posts/1"
+    Then the API response code should be 200
+    And the response should be valid JSON
+    And the JSON response should have property "id"
+    And the JSON response should have property "title"
+    And the JSON response should have property "body"
+    And the JSON response should have property "userId"
+    And the JSON response should not have property "password"
+
+  Scenario: Specific JSON Property Values
+    When I send a GET request to "/posts/1"
+    Then the API response code should be 200
+    And the JSON property "userId" should be 1
+    And the JSON property "id" should be 1
+
+  Scenario: JSON Structure Validation with DocString
+    When I send a POST request to "/posts" with body:
+      """
+      {
+        "title": "Test Title",
+        "body": "Test Body",
+        "userId": 1
+      }
+      """
+    Then the API response code should be 201
+    And the API response should contain json:
+      """
+      {
+        "title": "Test Title",
+        "body": "Test Body",
+        "userId": 1
+      }
+      """
+
+  Scenario: Response Header Validation
+    When I send a GET request to "/posts/1"
+    Then the API response code should be 200
+    And the response header "Content-Type" should be "application/json"
+
+  Scenario: Placeholder Usage
+    Given I set placeholder "{{postId}}" to "1"
+    And I set placeholder "{{userId}}" to "1"
+    When I send a GET request to "/posts/{{postId}}"
+    Then the API response code should be 200
+    And the JSON property "userId" should be {{userId}}
+    And the JSON property "id" should be {{postId}}
+
+  Scenario: Complex Scenario with All Features
+    Given I set placeholder "{{newTitle}}" to "Complex API Test"
+    And I set placeholder "{{newBody}}" to "Testing all features together"
+    And I set the following headers:
+      | Content-Type | application/json      |
+      | Accept       | application/json      |
+      | User-Agent   | VarbaseE2E-Testing/1.0 |
+    And I set the request body to '{"title": "{{newTitle}}", "body": "{{newBody}}", "userId": 1}'
+    When I send a POST request to "/posts"
+    Then the API response code should be 201
+    And the response should be valid JSON
+    And the API response should contain "Complex API Test"
+    And the API response should contain "Testing all features together"
+    And the JSON response should have property "id"
+    And the JSON response should have property "title"
+    And the JSON response should have property "body"
+    And the JSON response should have property "userId"
+    And print API response
+
+  Scenario: Error Handling Test
+    When I send a GET request to "/posts/999999"
+    Then the API response code should be 404
+
+  Scenario: Array Response Testing
+    When I send a GET request to "/posts"
+    Then the API response code should be 200
+    And the response should be valid JSON
+
+  Scenario: Different HTTP Methods Testing
+    # Test all supported HTTP methods
+    When I send a GET request to "/posts/1"
+    Then the API response code should be 200
+    
+    Given I set the request body to '{"title": "Test", "body": "Test", "userId": 1}'
+    When I send a POST request to "/posts"
+    Then the API response code should be 201
+    
+    Given I set the request body to '{"id": 1, "title": "Updated", "body": "Updated", "userId": 1}'
+    When I send a PUT request to "/posts/1"
+    Then the API response code should be 200
+    
+    Given I set the request body to '{"title": "Patched"}'
+    When I send a PATCH request to "/posts/1"
+    Then the API response code should be 200
+    
+    When I send a DELETE request to "/posts/1"
+    Then the API response code should be 200
+
+  Scenario: Nested JSON Property Testing
+    When I send a GET request to "/users/1"
+    Then the API response code should be 200
+    And the JSON response should have property "address.city"
+    And the JSON response should have property "company.name"
+
+  Scenario: Boolean and Number Property Testing
+    Given I set the request body with:
+      | title     | Test Post      |
+      | body      | Test content   |
+      | userId    | 1              |
+      | published | true           |
+      | views     | 100            |
+    When I send a POST request to "/posts"
+    Then the API response code should be 201

package/tests/features/cookie.feature

@@ -0,0 +1,13 @@
+Feature: Cookie step definitions
+
+  Scenario: Cookie existence and value matching
+    Given I am on "/cookies.html"
+     Then a cookie with the name "session_id" should exist
+      And a cookie with the name "session_id" and the value "abc123" should exist
+      And a cookie with the name "preferences" and a value containing "darkmode" should exist
+      And a cookie with a name containing "session" should exist
+      And a cookie with a name containing "pref" and a value containing "darkmode" should exist
+      And a cookie with the name "missing" should not exist
+      And a cookie with the name "language" and the value "fr" should not exist
+      And a cookie with the name "preferences" and a value containing "lightmode" should not exist
+      And a cookie with a name containing "old" should not exist

package/tests/features/date.feature

@@ -0,0 +1,11 @@
+Feature: Relative date token resolution
+
+  Tokens of the form [relative:OFFSET] and [relative:OFFSET#FORMAT]
+  are resolved before the step runs. OFFSET supports "+N unit", "-N unit",
+  "now", and "next/last <weekday>". Without FORMAT the value is a Unix
+  timestamp; with FORMAT it is rendered using YYYY/MM/DD/HH/mm/ss tokens.
+
+  Scenario: Resolve relative date tokens in step text
+    Given I am on "/date.html"
+     Then I should see "[relative:now#YYYY]"
+      And I should see "[relative:now#MM]"

package/tests/features/dynamic-content-examples.feature

@@ -0,0 +1,156 @@
+Feature: Dynamic Content Handling Examples
+  As a tester
+  I want to test dynamically loaded content
+  So that I can verify the application works with JavaScript-rendered elements
+
+  Background:
+    Given I am on "/dynamic-examples.html"
+
+  # Example 1: Clicking a button that appears after page load
+  Scenario: Click dynamically loaded button
+    When I wait 2 seconds
+    Then I should see "Dynamic Content Loaded"
+    When I press "Submit Form" button
+    Then I should see "Form submitted successfully"
+
+  # Example 2: Filling form fields that are added by JavaScript
+  Scenario: Fill in dynamically rendered form fields
+    When I click "Show Registration Form"
+    And I wait 1 second
+    When I fill in "john.doe@example.com" for "#email" by attr
+    And I fill in "John Doe" for "#fullname" by attr
+    And I fill in "SecurePass123" for "#password" by attr
+    And I press "Register" button
+    Then I should see "Registration successful"
+
+  # Example 3: Selecting options from dynamically populated dropdown
+  Scenario: Select from dynamically loaded dropdown options
+    When I scroll down 200
+    And I wait 1 second
+    When I click "Load Countries"
+    And I wait 2 seconds
+    When I select "United States" from "country"
+    Then I should see "You selected: United States"
+
+  # Example 4: Clicking links in dynamically loaded table rows
+  Scenario: Interact with dynamically loaded table rows
+    When I scroll down 400
+    And I wait 1 second
+    When I click "Load Users Table"
+    And I wait 2 seconds
+    Then I should see "John Smith" in the "john@example.com" row
+    When I click "Edit" in the "john@example.com" row
+    Then I should see "Editing user: john@example.com"
+
+  # Example 5: Checking dynamically added checkboxes
+  Scenario: Check dynamically rendered checkboxes
+    When I scroll down 600
+    And I wait 1 second
+    When I click "Show Preferences"
+    And I wait 1 second
+    When I check "#newsletter"
+    And I check "#notifications"
+    Then the "#newsletter" checkbox should be checked
+    And the "#notifications" checkbox should be checked
+
+  # Example 6: Uploading file to dynamically rendered input
+  Scenario: Upload file to dynamic file input
+    When I scroll down 800
+    And I wait 1 second
+    When I click "Enable File Upload"
+    And I wait 1 second
+    When I attach the file "test-document.pdf" to "#file-upload"
+    Then I should see "File selected: test-document.pdf"
+
+  # Example 7: Scrolling to dynamically added elements
+  Scenario: Scroll to dynamically loaded content section
+    When I scroll down 1200
+    And I wait 1 second
+    When I click "Load More Content"
+    And I wait 2 seconds
+    When I scroll to bottom of "#content-container"
+    Then I should see "End of dynamic content"
+
+  # Example 8: Handling removed elements (should not interact)
+  Scenario: Verify removed elements are not interacted with
+    When I scroll down 1400
+    And I wait 1 second
+    When I click "Show Temporary Button"
+    And I wait 1 second
+    Then I should see a "temp-action" element by its "id" attr
+    When I click "Remove Button"
+    And I wait 1 second
+    # This should fail gracefully if the button is removed
+    # Then I should not see a "temp-action" element by its "id" attr
+
+  # Example 9: Single Page Application navigation with dynamic content
+  Scenario: Navigate in SPA with dynamically loaded pages
+    When I scroll down 1600
+    And I wait 1 second
+    When I click "Products" by its "data-page" attribute
+    And I wait 1 second
+    Then I should see "Product Catalog"
+    When I click "Add to Cart" in the "Laptop Pro 15" row
+    Then I should see "Item added to cart"
+
+  # Example 10: Batch form filling with dynamically rendered fields
+  Scenario: Fill multiple dynamic form fields using table
+    When I scroll down 1800
+    And I wait 1 second
+    When I click "Show Contact Form"
+    And I wait 2 seconds
+    When I fill in the following: by attr
+      | #contact-name    | Jane Smith          |
+      | #contact-email   | jane@example.com    |
+      | #contact-phone   | +1-555-0123         |
+      | #contact-message | This is a test message |
+    And I press "Send Message" button
+    Then I should see "Message sent successfully"
+
+  # Example 11: Testing AJAX-loaded content after user action
+  Scenario: Interact with AJAX-loaded search results
+    When I scroll down 2200
+    And I wait 1 second
+    When I fill in "laptop" for "#search-input" by attr
+    And I press "Search" button
+    And I wait 2 seconds
+    Then I should see "Search Results"
+    When I click "View Details" in the "Laptop Pro 15" row
+    Then I should see "Product Details"
+
+  # Example 13: Infinite scroll content loading
+  Scenario: Load more content with infinite scroll
+    When I scroll down 2600
+    And I wait 1 second
+    When I scroll to bottom
+    And I wait 2 seconds
+    Then I should see "Loading more items"
+    And I wait 3 seconds
+    Then I should see "Item 21"
+    When I scroll to bottom
+    And I wait 2 seconds
+    Then I should see "Item 41"
+
+  # Example 14: React/Vue component interactions
+  Scenario: Interact with React component rendered buttons
+    When I scroll down 3000
+    And I wait 1 second
+    When I click "Initialize App"
+    And I wait 2 seconds
+    Then I should see "React App Loaded"
+    When I press "increment-btn" by its "id" attribute
+    And I press "increment-btn" by its "id" attribute
+    And I press "increment-btn" by its "id" attribute
+    Then I should see "Count: 3"
+
+  # Example 15: Conditional rendering based on user selection
+  Scenario: Handle conditionally rendered form fields
+    When I scroll down 3400
+    And I wait 1 second
+    When I select "Business" from "account-type"
+    And I wait 1 second
+    Then I should see a "company-name" element by attr
+    When I fill in "Acme Corporation" for "company-name" by attr
+    And I fill in "12-3456789" for "tax-id" by attr
+    And I press "Continue" button
+    Then I should see "Business account created"

package/tests/features/element.feature

@@ -0,0 +1,16 @@
+Feature: Element step definitions
+
+  Scenario: Element existence and attribute matching
+    Given I am on "/element.html"
+     Then the element "h1" with the attribute "data-test" and the value "hero" should exist
+      And the element "h1" with the attribute "data-test" and the value containing "her" should exist
+      And the element "h1" with the attribute "data-test" and the value "missing" should not exist
+      And the element "h1" should be displayed
+      And the element "#hidden" should not be displayed
+      And the element ".lead[data-role='outro']" should appear after the element ".lead[data-role='intro']"
+      And the text "Second paragraph" should appear after the text "First paragraph"
+
+  Scenario: Click and hover via element steps
+    Given I am on "/element.html"
+     When I click on the element "#btn"
+     Then I should see "clicked"

package/tests/features/field.feature

@@ -0,0 +1,25 @@
+Feature: Field step definitions
+
+  Scenario: Field state assertions
+    Given I am on "/field.html"
+     Then the field "username" should exist
+      And the field "username" should be empty
+      And the field "username" should be required
+      And the field "bio" should not be required
+      And the field "missing-field" should not exist
+      And the option "Admin" should exist within the select element "#role"
+      And the option "Manager" should not exist within the select element "#role"
+      And the option "Admin" should not be selected within the select element "#role"
+
+  Scenario: Field interactions
+    Given I am on "/field.html"
+     When I fill in the field "#username" with "alice"
+      And I check the checkbox "#agree"
+      And I choose the radio button "#r-red"
+      And I fill in the color field "fav" with the value "#ff0000"
+     Then the field "username" should not be empty
+      And the color field "fav" should have the value "#ff0000"
+
+  Scenario: Disable browser validation
+    Given I am on "/field.html"
+      And browser validation for the form "#f" is disabled

package/tests/features/keyboard.feature

@@ -0,0 +1,10 @@
+Feature: Keyboard step definitions
+
+  Scenario: Keyboard input
+    Given I am on "/keyboard.html"
+     When I focus on the element "#inp"
+      And I press the key "Enter"
+     Then I should see "Enter"
+     When I press the key "tab" on the element "#inp"
+      And I press the keys "Control+a"
+      And I press the keys "Control+a" on the element "#inp"

package/tests/features/link.feature

@@ -0,0 +1,11 @@
+Feature: Link step definitions
+
+  Scenario: Link href + title assertions
+    Given I am on "/links.html"
+     Then the link "About" with the href "/about" should exist
+      And the link "Contact" with the href "/contact" within the element "#nav" should exist
+      And the link "About" with the href "/missing" should not exist
+      And the link with the title "About us" should exist
+      And the link with the title "Nonexistent" should not exist
+      And the link "Example" should be an absolute link
+      And the link "About" should not be an absolute link