Every SDODS capability in one walkthrough

name: staging
ui:
  baseUrl: https://www.saucedemo.com
api:
  baseUrl: https://jsonplaceholder.typicode.com
  # For a real API:
  # auth: { type: bearer, token: '${API_TOKEN}' }
users:
  poolSize: 4
vars:
  defaultProduct: Sauce Labs Backpack
  standardPassword: '${DEMO_SHOP_PASSWORD:-secret_sauce}'
perf:
  budgets: { pageLoadMs: 5000 }

@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>"

@Fixture<typeof test>('loginPage')
export class LoginPage extends BasePage {
  readonly submit = this.h(this.page.locator('#login-button'), {
    description: 'login button',
    role: 'button',
    name: 'Login',
    testId: 'login-button',
  });

  @Given('I am on the login page')
  async open() {
    await this.goto('login');
  }

  @When('I login with {string} and {string}')
  async login(username: string, password: string) {
    await this.username.fill(this.render(username));
    await this.password.fill(this.render(password));
    await this.submit.click();
  }
}

@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"

@hybrid @hybrid-demo
Feature: Seed through the API, verify in the browser

  @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"

@ui @auth @data-driven
Feature: Data-driven login

  @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

# projects/demo-shop/features/auth/user-pool.feature
  @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

@ui @inventory @mock
Feature: Network interception

  @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"

@ui @inventory @visual
Feature: Inventory visual baseline

  @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"

@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

processes:
  - name: pr-check
    trigger: pr
    tags: '@smoke'
    browsers: [chromium]
    harMode: replay
    gates: { minPassRate: 100 }
  - name: release-gate
    trigger: release
    tags: '@smoke or @regression'
    browsers: [chromium, firefox, webkit]
    failOnFlaky: true
    gates: { minPassRate: 100, maxFlaky: 0, perfBudgets: true, a11y: true }