@sdods/cli 0.2.0

package/templates/projects/demo-shop/data/common/users.csv

@@ -0,0 +1,7 @@
+id,username,password,role,displayName
+1,standard_user,${DEMO_SHOP_PASSWORD:-secret_sauce},standard,Standard user
+2,problem_user,${DEMO_SHOP_PASSWORD:-secret_sauce},problem,Problem user
+3,performance_glitch_user,${DEMO_SHOP_PASSWORD:-secret_sauce},performance,Performance glitch user
+4,locked_out_user,${DEMO_SHOP_PASSWORD:-secret_sauce},locked,Locked out user
+5,error_user,${DEMO_SHOP_PASSWORD:-secret_sauce},standard,Error user
+6,visual_user,${DEMO_SHOP_PASSWORD:-secret_sauce},standard,Visual user

package/templates/projects/demo-shop/data/factories.ts

@@ -0,0 +1,16 @@
+import { defineFactories } from '@sdods/core/data';
+
+/** Faker factories, seeded per scenario fingerprint so retries regenerate identical data. */
+export default defineFactories({
+  user: (f) => ({
+    email: f.internet.email(),
+    firstName: f.person.firstName(),
+    lastName: f.person.lastName(),
+    zip: f.location.zipCode('#####'),
+  }),
+  post: (f) => ({
+    title: `SDODS ${f.lorem.words(3)}`,
+    body: f.lorem.sentence(),
+    userId: f.number.int({ min: 1, max: 10 }),
+  }),
+});

package/templates/projects/demo-shop/data/staging/users.csv

@@ -0,0 +1,6 @@
+id,username,password,role,displayName
+1,standard_user,${DEMO_SHOP_PASSWORD:-secret_sauce},standard,Standard user (staging)
+2,problem_user,${DEMO_SHOP_PASSWORD:-secret_sauce},problem,Problem user (staging)
+3,performance_glitch_user,${DEMO_SHOP_PASSWORD:-secret_sauce},performance,Performance glitch user (staging)
+4,locked_out_user,${DEMO_SHOP_PASSWORD:-secret_sauce},locked,Locked out user (staging)
+5,visual_user,${DEMO_SHOP_PASSWORD:-secret_sauce},standard,Visual user (staging)

package/templates/projects/demo-shop/envs/local.yaml

@@ -0,0 +1,17 @@
+name: local
+description: Same public sandboxes, smaller pool, headed-friendly timeouts. Override URLs via SDODS_UI_BASE_URL / SDODS_API_BASE_URL.
+ui:
+  baseUrl: https://www.saucedemo.com
+api:
+  baseUrl: https://jsonplaceholder.typicode.com
+  headers: { Accept: application/json }
+  auth: { type: none }
+users:
+  poolSize: 2
+vars:
+  defaultProduct: Sauce Labs Bike Light
+  standardPassword: '${DEMO_SHOP_PASSWORD:-secret_sauce}'
+timeouts:
+  test: 90000
+screenshots:
+  onlyOnFailure: false

package/templates/projects/demo-shop/envs/staging.yaml

@@ -0,0 +1,23 @@
+name: staging
+description: Public sandboxes (SauceDemo + JSONPlaceholder). No secrets except the demo password.
+ui:
+  baseUrl: https://www.saucedemo.com
+api:
+  baseUrl: https://jsonplaceholder.typicode.com
+  headers: { Accept: application/json }
+  auth: { type: none }
+  # For a real API:
+  # auth: { type: bearer, token: '${API_TOKEN}' }
+  # openapi: ./openapi/staging.json
+users:
+  poolSize: 4
+vars:
+  defaultProduct: Sauce Labs Backpack
+  standardPassword: '${DEMO_SHOP_PASSWORD:-secret_sauce}'
+use:
+  locale: en-US
+  timezoneId: America/New_York
+screenshots:
+  onlyOnFailure: false
+perf:
+  budgets: { pageLoadMs: 5000 }

package/templates/projects/demo-shop/features/api/posts.feature

@@ -0,0 +1,90 @@
+@api @posts @har:posts
+Feature: Posts API
+  JSONPlaceholder CRUD through the shared API step library: status codes, JSON-path assertions,
+  schema validation, variable chaining and response-time budgets.
+
+  @smoke
+  Scenario: List posts
+    When I send a GET request to "/posts"
+    Then the response status should be 200
+    And the response body should be an array
+    And the response JSON path "$.length" should equal "100"
+    And the response JSON path "[0].id" should equal "1"
+    And the response time should be under 3000 ms
+
+  @smoke @contract
+  Scenario: Get a single post and validate its shape
+    When I send a GET request to "/posts/1"
+    Then the response status should be 200
+    And the response JSON path "id" should equal "1"
+    And the response JSON path "userId" should equal "1"
+    And the response JSON path "title" should match ".+"
+    And the response should match the JSON schema "post"
+    And the response header "content-type" should contain "application/json"
+
+  @regression
+  Scenario: Nested resource - comments of a post
+    When I send a GET request to "/posts/1/comments"
+    Then the response status should be 200
+    And the response JSON path "$.length" should equal "5"
+    And the response JSON path "[0].postId" should equal "1"
+    And the response JSON path "[0].email" should match "@"
+
+  @regression
+  Scenario: Query parameters filter posts by user
+    Given I set the query parameter "userId" to "2"
+    When I send a GET request to "/posts"
+    Then the response status should be 200
+    And the response JSON path "$.length" should equal "10"
+    And the response JSON path "[0].userId" should equal "2"
+
+  @regression @contract
+  Scenario: Create a post and chain its id
+    Given I set the variable "title" to "SDODS created this"
+    When I send a POST request to "/posts" with body:
+      """json
+      { "title": "{{title}}", "body": "hello from SDODS", "userId": 1 }
+      """
+    Then the response status should be 201
+    And the response JSON path "title" should equal "{{title}}"
+    And the response should match the JSON schema "post"
+    When I save the response JSON path "id" as "postId"
+    And I send a GET request to "/posts/{{postId}}"
+    Then the response status should be one of "200, 404"
+
+  @regression
+  Scenario: Update a post
+    When I send a PUT request to "/posts/1" with body:
+      """json
+      { "id": 1, "title": "updated by SDODS", "body": "changed", "userId": 1 }
+      """
+    Then the response status should be 200
+    And the response JSON path "title" should equal "updated by SDODS"
+    When I send a PATCH request to "/posts/1" with body:
+      """json
+      { "title": "patched by SDODS" }
+      """
+    Then the response status should be 200
+    And the response JSON path "title" should equal "patched by SDODS"
+
+  @regression
+  Scenario: Delete a post
+    When I send a DELETE request to "/posts/1"
+    Then the response status should be 200
+
+  @regression
+  Scenario: Unknown post returns 404
+    When I send a GET request to "/posts/999999"
+    Then the response status should be 404
+
+  @regression
+  Scenario: Data-driven request from the posts dataset
+    Given I load dataset "posts" row 0
+    When I send a GET request to "/posts/{{id}}"
+    Then the response status should be 200
+    And the response JSON path "userId" should equal "{{userId}}"
+
+  @regression
+  Scenario: Polling until a condition holds
+    When I poll GET "/posts/2" until JSON path "id" equals "2" within 10 seconds
+    Then the response status should be 200

package/templates/projects/demo-shop/features/auth/data-driven-login.feature

@@ -0,0 +1,17 @@
+@ui @auth @data-driven
+Feature: Data-driven login
+  Credentials come from the users dataset (data/<env>/users.csv with data/common fallback).
+
+  @regression
+  Scenario: Login with the first user of the dataset
+    Given I load dataset "users" row 0
+    And I am on the login page
+    When I login with "{{username}}" and "{{password}}"
+    Then I should be on the inventory page
+
+  @regression
+  Scenario: Login with the user whose role is problem
+    Given I load dataset "users" where "role" is "problem"
+    And I am on the login page
+    When I login with "{{username}}" and "{{password}}"
+    Then I should be on the inventory page

package/templates/projects/demo-shop/features/auth/login.feature

@@ -0,0 +1,32 @@
+@ui @auth
+Feature: Login
+  As a shopper I want to sign in so that I can see the inventory.
+
+  Background:
+    Given I am on the login page
+
+  @smoke @har:login
+  Scenario: Successful login shows the products
+    When I login with "standard_user" and "{{standardPassword}}"
+    Then I should be on the inventory page
+    And the inventory title should be "Products"
+
+  @regression
+  Scenario Outline: Failed login shows a clear error
+    When I login with "<username>" and "<password>"
+    Then I should see the login error "<error>"
+
+    # title-format: <username> → <error>
+    Examples:
+      | username        | password     | error                                                                     |
+      | locked_out_user | secret_sauce | Epic sadface: Sorry, this user has been locked out.                       |
+      | standard_user   | wrong        | Epic sadface: Username and password do not match any user in this service |
+      |                 | secret_sauce | Epic sadface: Username is required                                        |
+      | standard_user   |              | Epic sadface: Password is required                                        |
+
+  @regression
+  Scenario: Generic UI steps work against the login form
+    When I fill the element with test id "username" with "standard_user"
+    And I fill the element with test id "password" with "{{standardPassword}}"
+    And I click the element with test id "login-button"
+    Then the page URL should contain "/inventory.html"

package/templates/projects/demo-shop/features/auth/user-pool.feature

@@ -0,0 +1,20 @@
+@ui @auth @pool
+Feature: User pool
+  Accounts are leased per worker from the pool dataset; login state is cached as storageState.
+
+  @sanity @user:standard
+  Scenario: A leased standard user starts logged in through cached storage state
+    Given I navigate to the "inventory" page
+    Then I should be on the inventory page
+    And the inventory title should be "Products"
+
+  @sanity
+  Scenario: Leasing a user by role inside the scenario
+    Given I use a leased user with role "problem"
+    And I navigate to the "inventory" page
+    Then I should be on the inventory page
+
+  @sanity @user:performance
+  Scenario: A second role leases a different account
+    Given I navigate to the "inventory" page
+    Then I should be on the inventory page

package/templates/projects/demo-shop/features/cart/cart.feature

@@ -0,0 +1,33 @@
+@ui @cart
+Feature: Cart
+  Adding products and reviewing them in the cart.
+
+  Background:
+    Given I am on the login page
+    And I login with "standard_user" and "{{standardPassword}}"
+
+  @smoke @har:cart
+  Scenario: A product added on the inventory page appears in the cart
+    When I add "Sauce Labs Backpack" to the cart
+    And I open the cart
+    Then the cart should list "Sauce Labs Backpack"
+
+  @regression
+  Scenario: Continue shopping returns to the inventory
+    When I open the cart
+    And I click the "Continue Shopping" button
+    Then I should be on the inventory page
+
+  @regression
+  Scenario: Checkout form is reachable from the cart
+    When I add "Sauce Labs Bolt T-Shirt" to the cart
+    And I open the cart
+    And I click the "Checkout" button
+    Then the page URL should contain "/checkout-step-one.html"
+    When I fill the form:
+      | field           | value |
+      | First Name      | Auto  |
+      | Last Name       | Max   |
+      | Zip/Postal Code | 12345 |
+    And I click the "Continue" button
+    Then the page URL should contain "/checkout-step-two.html"

package/templates/projects/demo-shop/features/hybrid/seed-then-verify.feature

@@ -0,0 +1,28 @@
+@hybrid @hybrid-demo
+Feature: Seed through the API, verify in the browser
+  One scenario, both layers: the API client and the page share the same fixtures and variables.
+
+  @regression
+  Scenario: A post created through the API is rendered by the UI
+    Given I use a leased user with role "standard"
+    When I seed via POST "/posts" with body:
+      """json
+      { "title": "SDODS hybrid {{username}}", "body": "seeded", "userId": 1 }
+      """
+    Then the response status should be 201
+    When I save the response JSON path "title" as "title"
+    And I mock "**/inventory.html" with HTML:
+      """
+      <main><h1>{{title}}</h1><p>rendered from the seeded API response</p></main>
+      """
+    And I navigate to the "inventory" page
+    Then the UI should show the text from JSON path "title"
+
+  @regression
+  Scenario: API state and UI state in one flow
+    When I send a GET request to "/users/1"
+    Then the response status should be 200
+    When I save the response JSON path "username" as "apiUser"
+    Given I am on the login page
+    When I fill the element with test id "username" with "{{apiUser}}"
+    Then the element with test id "username" should be visible

package/templates/projects/demo-shop/features/inventory/inventory.feature

@@ -0,0 +1,38 @@
+@ui @inventory
+Feature: Inventory
+  Products page: listing, cart badge and sorting.
+
+  Background:
+    Given I am on the login page
+    And I login with "standard_user" and "{{standardPassword}}"
+
+  @smoke @har:products
+  Scenario: Products are displayed
+    Then the inventory title should be "Products"
+    And there should be 6 products listed
+
+  @regression
+  Scenario: Add a product to the cart
+    When I add "{{defaultProduct}}" to the cart
+    Then the cart badge should show 1 item
+
+  @regression
+  Scenario: Remove a product from the cart
+    When I add "Sauce Labs Bike Light" to the cart
+    And I remove "Sauce Labs Bike Light" from the cart
+    Then the cart badge should be hidden
+
+  @regression
+  Scenario: Sort products by price ascending
+    When I sort products by "Price (low to high)"
+    Then the product prices should be sorted ascending
+
+  @regression
+  Scenario: Sort products by name descending
+    When I sort products by "Name (Z to A)"
+    Then the product names should be sorted descending
+
+  @regression @skip:webkit
+  Scenario: Open the menu (browser-specific exclusion example)
+    When I click the "Open Menu" button
+    Then the "Logout" link should be visible

package/templates/projects/demo-shop/features/inventory/network-intercept.feature

@@ -0,0 +1,29 @@
+@ui @inventory @mock
+Feature: Network interception
+  Route mocking with the shared steps, and a direct API check from a UI scenario.
+
+  @regression
+  Scenario: A mocked page is rendered instead of the real one
+    Given I mock "**/mocked/**" with HTML:
+      """
+      <h1 data-test="banner">Mocked by SDODS</h1>
+      """
+    When I navigate to the "/mocked/banner.html" page
+    Then I should see the text "Mocked by SDODS"
+    And the element with test id "banner" should be visible
+
+  @regression
+  Scenario: A mocked JSON API response is observed through the API client
+    Given I am on the login page
+    And I mock "**/api/health" with JSON:
+      """json
+      { "status": "mocked" }
+      """
+    When I send a GET request to "https://www.saucedemo.com/"
+    Then the response status should be 200
+
+  @smoke @har:site
+  Scenario: The site answers over HTTP
+    When I send a GET request to "https://www.saucedemo.com/"
+    Then the response status should be 200
+    And the response time should be under 5000 ms

package/templates/projects/demo-shop/features/inventory/visual.feature

@@ -0,0 +1,10 @@
+@ui @inventory @visual
+Feature: Inventory visual baseline
+  Pixel comparison against a per-browser baseline (run once with --update-snapshots).
+
+  @regression
+  Scenario: Inventory page matches its baseline
+    Given I am on the login page
+    And I login with "standard_user" and "{{standardPassword}}"
+    Then I should be on the inventory page
+    And the page should match the visual baseline "inventory"