@keber/qa-framework 1.10.0 → 1.11.3

package/CHANGELOG.md

@@ -7,29 +7,59 @@ Versioning follows [Semantic Versioning](https://semver.org/).
 
 ---
 
-## [1.0.0] - 2026-03-04
+## [1.11.0] - 2026-06-24
 
 ### Added
 
-- **Framework scaffold** — initial `qa/` directory tree with 9 numbered folders (00–08)
-- **6-file submodule template set** — `00-inventory` through `05-test-scenarios`
-- **Agent instructions** — 7 purpose-specific Markdown instruction files for IDE agents
-- **Standards** — naming conventions, bug report template, test case template, test data guidelines
-- **Automation scaffold** — generalized Playwright `playwright.config.ts`, `global-setup.ts`, `.env.example`, `fixtures/auth.ts`
-- **Optional integrations** — stubs and READMEs for Playwright, `playwright-azure-reporter`, and ADO PowerShell
-- **CLI entry point** — `qa-framework init`, `generate`, `validate` commands
-- **Documentation** — architecture, comparison matrix, generalization decisions, installation guide, usage-with-agent guide, spec-driven philosophy, folder structure guide
-- **Migration notes** — `MIGRATION-NOTES.md` for projects moving from embedded to package-based framework
-
-### Source repositories
+- **`templates/automation-scaffold/fixtures/base.ts`** — new fixture with TTL-aware session
+  refresh. Replaces the plain `@playwright/test` import in long-running suites where the
+  server-side session may expire before the suite finishes.
+- **`templates/automation-scaffold/global-setup.ts`** — hardened login flow:
+  - `resolveVar()` with source logging (`param` / `env:KEY` / `default`)
+  - Login retry loop (up to 3 attempts) with crash-page detection and recovery
+  - `resolveAuthUsers()` — derives which users to authenticate from `QA_AUTH_USER` env var
+    or from configured `storageState` paths in `playwright.config.ts`
+  - `dismissOnboardingFlow()` — configurable via `QA_DISMISS_ONBOARDING_LABELS`
+    (comma-separated button labels); no-op by default
+  - Support for a second test user (`.auth/user-2.json`) via `QA_USER2_EMAIL` /
+    `QA_USER2_PASSWORD`
+- **`templates/automation-scaffold/playwright.config.ts`** — exports `SESSION_TTL_MS`
+  (default 2 h, overridable via `QA_SESSION_TTL_MS`); commented-out parallel 2-user variant
+  (`chromium-user1` / `chromium-user2`).
+- **`templates/automation-scaffold/.env.example`** — new variables: `QA_SESSION_TTL_MS`,
+  `QA_AUTH_USER`, `QA_USER2_EMAIL`, `QA_USER2_PASSWORD`, `QA_DISMISS_ONBOARDING_LABELS`,
+  `PLAYWRIGHT_SERVICE_URL`.
+- **`templates/integration-scaffold/`** — new scaffold for API testing with Playwright
+  `APIRequestContext`. Includes `package.json`, `playwright.config.ts`, `global-setup.ts`
+  (token-based or browser-login auth), `tests/example.spec.ts`, `README.md`, `.env.example`.
+  Deployed to `qa/07-automation/integration/` on `init` and `upgrade`.
+- **`templates/memory/`** — three semi-guided operational memory templates:
+  `ci-pipeline-findings.md`, `e2e-stabilization-patterns.md`, `data-volatility-strategies.md`.
+  Seeded into `qa/memory/` on `init` and `upgrade`.
+- **`qa/06-defects/disputed/`** — third defect state for cases where QA has evidence but the
+  business or dev team disputes the expected behavior. Created on `init` and `upgrade`.
+- **`integrations/ado-powershell/pipelines/azure-pipeline-qa.yml`** — operational hardening:
+  - `suiteFilter` pipeline parameter (default `all`); auto-overridden to `all` on scheduled runs
+  - Bash array (`GREP_ARGS`) for safe grep pattern expansion with bracket characters
+  - `PublishTestResults@2` scoped to exact XML path instead of `**/*.xml`
+  - `publishRunAttachments: false` on both E2E and API stages
+  - Artifact names suffixed with `$(System.JobAttempt)` to prevent collision on retries
+  - `QA_AUTH_USER` documented as commented example for the 2-job parallel model
+- **`integrations/playwright/README.md`** — new section: Visual AI helper optional pattern.
+- **`templates/qa-readme.md`** — new fields: `ADO Project`, `Last Run` summary table,
+  `Flaky Tests` inline annotation convention.
 
-This version was bootstrapped from analysis of two existing embedded QA implementations:
-
-- `redacted-repo` (Repo A) — ASP.NET MVC 5 + jQuery + toastr + Sprint-based E2E
-- `redacted-repo` (Repo B) — Blazor WebAssembly + Radzen + full ADO pipeline integration
+### Changed
 
-All project-specific content (URLs, ADO IDs, user credentials, module names, form selectors)
-has been removed or parameterized. See `docs/comparison-matrix.md` and `docs/generalization-decisions.md`.
+- **`scripts/init.js`** — `fixtures/base.ts` added to e2e scaffold copy list; integration
+  scaffold replaces the `integration/README.md` placeholder; memory template files seeded
+  from `templates/memory/` via `fs.readFileSync`.
+- **`scripts/upgrade.js`** — integration scaffold, `disputed/` defect folder, and memory
+  templates are all seeded idempotently on upgrade for existing projects.
+- **`docs/folder-structure-guide.md`** — `06-defects/` updated to document `disputed/`.
+- **`templates/defect-report.md`** — `Status` field extended with `Disputed` value.
+- **`qa/memory/INDEX.md`** template updated to pre-populate rows for the three new memory
+  template files.
 
 ---
 
@@ -300,3 +330,18 @@ See `MIGRATION-NOTES.md` — section "Upgrading from a version that used `.githu
 
 ---
 
+## [1.0.0] - 2026-03-04
+
+### Added
+
+- **Framework scaffold** — initial `qa/` directory tree with 9 numbered folders (00–08)
+- **6-file submodule template set** — `00-inventory` through `05-test-scenarios`
+- **Agent instructions** — 7 purpose-specific Markdown instruction files for IDE agents
+- **Standards** — naming conventions, bug report template, test case template, test data guidelines
+- **Automation scaffold** — generalized Playwright `playwright.config.ts`, `global-setup.ts`, `.env.example`, `fixtures/auth.ts`
+- **Optional integrations** — stubs and READMEs for Playwright, `playwright-azure-reporter`, and ADO PowerShell
+- **CLI entry point** — `qa-framework init`, `generate`, `validate` commands
+- **Documentation** — architecture, comparison matrix, generalization decisions, installation guide, usage-with-agent guide, spec-driven philosophy, folder structure guide
+- **Migration notes** — `MIGRATION-NOTES.md` for projects moving from embedded to package-based framework
+
+---

package/README.md

@@ -1,7 +1,7 @@
 # qa-framework
 
 > Reusable, installable, agent-oriented QA framework for spec-driven automated testing.
-> Current version: **v1.9.1**
+> Current version: **v1.10.0**
 
 ---
 

package/docs/folder-structure-guide.md

@@ -260,10 +260,16 @@ Each skill folder contains:
 ├── README.md
 ├── open/
 │   └── DEF-{NNN}-{slug}.md
+├── disputed/
+│   └── DEF-{NNN}-{slug}.md
 └── resolved/
     └── DEF-{NNN}-{slug}.md
 ```
 
+- `open/` - confirmed defect, fix pending
+- `disputed/` - QA has evidence but business or dev team disputes the expected behavior; pending functional decision
+- `resolved/` - closed by fix or formal decision
+
 **Decision guide**:
 - ADO enabled → use ADO Work Items. `06-defects/` contains lightweight references only
 - ADO disabled → use this folder as primary defect tracker

package/integrations/ado-powershell/pipelines/azure-pipeline-qa.yml

@@ -1,5 +1,5 @@
 # -----------------------------------------------------------------------
-# keber/qa-framework — Azure Pipeline QA Template
+# keber/qa-framework - Azure Pipeline QA Template
 # -----------------------------------------------------------------------
 # Parameterized CI pipeline for running Playwright E2E and API tests and
 # syncing results to Azure DevOps Test Plans via SYSTEM_ACCESSTOKEN.
@@ -8,28 +8,28 @@
 # Update 'resources.repositories.name' to match your org/project/repo.
 #
 # Required Pipeline Library Variable Group: "QA-Variables"
-# Create this group in ADO → Pipelines → Library and add the following:
+# Create this group in ADO -> Pipelines -> Library and add the following:
 #
-#   QA_BASE_URL          — Target application URL  (e.g. https://app-qa.example.com)
-#   QA_USER_EMAIL        — Test user email / RUT
-#   QA_USER_PASSWORD     — Test user password                        [secret]
-#   ADO_ORG              — ADO organization slug  (e.g. garcesfruit-desarrollo)
-#   ADO_PROJECT          — ADO project name        (e.g. gf-portalproveedores)
-#   ADO_E2E_PLAN_ID      — Test Plan ID for the E2E suite            (e.g. 27044)
-#   ADO_API_PLAN_ID      — Test Plan ID for the API/integration suite (e.g. 27046)
+#   QA_BASE_URL          - Target application URL  (e.g. https://app-qa.example.com)
+#   QA_USER_EMAIL        - Test user email / RUT
+#   QA_USER_PASSWORD     - Test user password                        [secret]
+#   ADO_ORG              - ADO organization slug  (e.g. my-org)
+#   ADO_PROJECT          - ADO project name        (e.g. my-project)
+#   ADO_E2E_PLAN_ID      - Test Plan ID for the E2E suite
+#   ADO_API_PLAN_ID      - Test Plan ID for the API/integration suite
 #
-#   NOTE on multiple Plan IDs: ADO variable groups store plain strings — there
+#   NOTE on multiple Plan IDs: ADO variable groups store plain strings - there
 #   is no array type. Use one variable per suite (ADO_E2E_PLAN_ID / ADO_API_PLAN_ID).
 #   If the project has only one suite, a single ADO_PLAN_ID variable is enough.
 #   Results are reported to ADO via System.AccessToken (OAuth); no PAT required.
 # -----------------------------------------------------------------------
 
-# Cross-project repository — update <ADO_SOURCE_PROJECT>/<REPO_NAME> as needed
+# Cross-project repository - update <ADO_SOURCE_PROJECT>/<REPO_NAME> as needed
 resources:
   repositories:
     - repository: source
       type: git
-      name: <ADO_SOURCE_PROJECT>/<REPO_NAME>   # e.g. gf-gestion-qa/gf-portalproveedores
+      name: <ADO_SOURCE_PROJECT>/<REPO_NAME>   # e.g. my-qa-project/my-repo
       ref: refs/heads/main
 
 # Trigger: push and PR to main.
@@ -44,15 +44,34 @@ pr:
     include:
       - main
 
-# Optional scheduled run — uncomment and adjust if a nightly regression is needed:
+# Optional scheduled run - uncomment and adjust if a nightly regression is needed:
 # schedules:
-#   - cron: '0 6 * * 1-5'   # 06:00 UTC Mon–Fri (03:00 CLT / 02:00 CLST)
+#   - cron: '0 6 * * 1-5'   # 06:00 UTC Mon-Fri (03:00 CLT / 02:00 CLST)
 #     displayName: Nightly regression
 #     branches:
 #       include:
 #         - main
 #     always: true
 
+# -----------------------------------------------------------------------
+# Pipeline parameters
+# -----------------------------------------------------------------------
+# suiteFilter controls which tests run when the pipeline is triggered manually
+# or from a PR. Scheduled runs always override this to 'all' automatically
+# (see the "Resolve suite filter" step in each test job).
+#
+# Default is 'all' so a plain manual run executes the full suite.
+# Override at queue time to run a subset (e.g. 'smoke', '[P0]', 'login').
+#
+# The value is passed to Playwright via --grep. Special regex characters such
+# as '[' and ']' are escaped by the bash array pattern in the run step, so
+# values like '[P0]' are safe.
+parameters:
+  - name: suiteFilter
+    displayName: 'Test suite filter (grep pattern, or "all" to skip filtering)'
+    type: string
+    default: 'all'
+
 pool:
   vmImage: 'ubuntu-latest'
 
@@ -111,6 +130,21 @@ stages:
   # -----------------------------------------------------------------------
   # Stage 2: E2E Tests (Playwright/Chromium)
   # -----------------------------------------------------------------------
+  # Single-job configuration. For parallel execution with two test users,
+  # split this into two jobs and set QA_AUTH_USER per job:
+  #
+  #   - job: E2E_User1
+  #     variables:
+  #       QA_AUTH_USER: '1'
+  #     ...
+  #   - job: E2E_User2
+  #     variables:
+  #       QA_AUTH_USER: '2'
+  #     ...
+  #
+  # Each job must use a distinct Playwright project (--project=chromium-user1 /
+  # --project=chromium-user2) to avoid session conflicts between parallel users.
+  # -----------------------------------------------------------------------
   - stage: E2E
     displayName: 'E2E Tests (Playwright/Chromium)'
     dependsOn: Setup
@@ -138,11 +172,11 @@ stages:
               HTTP_CODE=$(curl -o /dev/null -s -w "%{http_code}" --max-time 30 "$(QA_BASE_URL)")
               echo "HTTP response: $HTTP_CODE"
               if [ "$HTTP_CODE" -lt 200 ] || [ "$HTTP_CODE" -ge 400 ]; then
-                echo "##[error]Smoke test failed — $(QA_BASE_URL) returned HTTP $HTTP_CODE"
+                echo "##[error]Smoke test failed - $(QA_BASE_URL) returned HTTP $HTTP_CODE"
                 exit 1
               fi
               echo "Smoke test passed (HTTP $HTTP_CODE)"
-            displayName: 'Smoke test — verify QA_BASE_URL is reachable'
+            displayName: 'Smoke test - verify QA_BASE_URL is reachable'
 
           # ---------------------------------------------------------------
           # Playwright Workspaces (Azure App Testing)
@@ -159,9 +193,28 @@ stages:
           #     inlineScript: echo "Authenticated via Entra ID"
 
           - script: |
+              # Scheduled runs always execute the full suite, regardless of the
+              # suiteFilter parameter. This prevents accidental partial runs in
+              # nightly regressions when the parameter was changed by a prior
+              # manual queue.
+              SUITE_FILTER="${{ parameters.suiteFilter }}"
+              if [ "$(Build.Reason)" = "Schedule" ]; then
+                SUITE_FILTER="all"
+                echo "Scheduled run detected - overriding suiteFilter to 'all'"
+              fi
+              echo "Effective suiteFilter: $SUITE_FILTER"
+
+              # Build --grep args as a bash array to safely handle patterns that
+              # contain special regex characters such as '[' and ']'. Inline
+              # string interpolation would break those patterns at the shell level.
+              GREP_ARGS=()
+              if [ "$SUITE_FILTER" != "all" ]; then
+                GREP_ARGS=(--grep "$SUITE_FILTER")
+              fi
+
               cd $(E2E_DIR)
               npx playwright test --project=chromium --ignore-snapshots \
-                --grep-invert "_inspect|_diag"
+                --grep-invert "_inspect|_diag" "${GREP_ARGS[@]}"
             displayName: 'Run E2E tests'
             continueOnError: true
             env:
@@ -173,31 +226,40 @@ stages:
               ADO_PLAN_ID:        $(ADO_E2E_PLAN_ID)
               SYSTEM_ACCESSTOKEN: $(System.AccessToken)
               CI:                 'true'
-              # PLAYWRIGHT_SERVICE_URL: $(PLAYWRIGHT_SERVICE_URL)  # Playwright Workspaces endpoint — enable together with the login task
+              # QA_AUTH_USER: '1'  # Set explicitly when running parallel jobs (user-1 / user-2 model)
+              # PLAYWRIGHT_SERVICE_URL: $(PLAYWRIGHT_SERVICE_URL)  # Playwright Workspaces endpoint - enable together with the login task
 
+          # publishRunAttachments is false because screenshots and traces are
+          # already uploaded as pipeline artifacts below. Setting it to true
+          # would double-publish the same files.
           - task: PublishTestResults@2
             condition: always()
             inputs:
               testResultsFormat:     'JUnit'
-              testResultsFiles:      '**/test-results/**/*.xml'
+              testResultsFiles:      'test-results/junit-results.xml'
               searchFolder:          $(E2E_DIR)
               mergeTestResults:      true
+              publishRunAttachments: false
               failTaskOnFailedTests: true
               testRunTitle:          '[Auto E2E] $(Build.BuildNumber)'
             displayName: 'Publish E2E test results (JUnit)'
 
+          # Artifact names include $(System.JobAttempt) to avoid name collisions
+          # when the job is retried. ADO rejects duplicate artifact names within
+          # the same pipeline run, so without the suffix a retry always fails at
+          # the publish step.
           - task: PublishPipelineArtifact@1
             condition: always()
             inputs:
               targetPath: '$(E2E_DIR)/playwright-report'
-              artifact:   'e2e-playwright-report'
+              artifact:   'e2e-playwright-report-attempt-$(System.JobAttempt)'
             displayName: 'Publish E2E HTML report'
 
           - task: PublishPipelineArtifact@1
             condition: always()
             inputs:
               targetPath: '$(E2E_DIR)/test-results'
-              artifact:   'e2e-test-results'
+              artifact:   'e2e-test-results-attempt-$(System.JobAttempt)'
             displayName: 'Publish E2E trace artifacts'
 
   # -----------------------------------------------------------------------
@@ -237,6 +299,7 @@ stages:
           #     inlineScript: echo "Authenticated via Entra ID"
 
           - script: |
+              # API integration tests do not use suite tags - always run all.
               cd $(API_DIR)
               npx playwright test --grep-invert "_inspect|_diag"
             displayName: 'Run API integration tests'
@@ -250,29 +313,33 @@ stages:
               ADO_PLAN_ID:        $(ADO_API_PLAN_ID)
               SYSTEM_ACCESSTOKEN: $(System.AccessToken)
               CI:                 'true'
-              # PLAYWRIGHT_SERVICE_URL: $(PLAYWRIGHT_SERVICE_URL)  # Playwright Workspaces endpoint — enable together with the login task
+              # PLAYWRIGHT_SERVICE_URL: $(PLAYWRIGHT_SERVICE_URL)  # Playwright Workspaces endpoint - enable together with the login task
 
+          # publishRunAttachments is false because trace artifacts are already
+          # uploaded as pipeline artifacts below.
           - task: PublishTestResults@2
             condition: always()
             inputs:
               testResultsFormat:     'JUnit'
-              testResultsFiles:      '**/test-results/**/*.xml'
+              testResultsFiles:      'test-results/junit-results.xml'
               searchFolder:          $(API_DIR)
               mergeTestResults:      true
+              publishRunAttachments: false
               failTaskOnFailedTests: true
               testRunTitle:          '[Auto API] $(Build.BuildNumber)'
             displayName: 'Publish API test results (JUnit)'
 
+          # Artifact names include $(System.JobAttempt) to prevent collision on retries.
           - task: PublishPipelineArtifact@1
             condition: always()
             inputs:
               targetPath: '$(API_DIR)/playwright-report'
-              artifact:   'api-playwright-report'
+              artifact:   'api-playwright-report-attempt-$(System.JobAttempt)'
             displayName: 'Publish API HTML report'
 
           - task: PublishPipelineArtifact@1
             condition: always()
             inputs:
               targetPath: '$(API_DIR)/test-results'
-              artifact:   'api-test-results'
+              artifact:   'api-test-results-attempt-$(System.JobAttempt)'
             displayName: 'Publish API trace artifacts'

package/integrations/playwright/README.md

@@ -66,3 +66,127 @@ test.describe('[TC-M-S-NNN] Module > Submodule @P0', () => {
   });
 });
 ```
+
+## Visual AI helper (optional advanced pattern)
+
+> **Advanced / optional.** This pattern is not part of the default scaffold and requires
+> an AI vision API key. Use it when a selector-based assertion is too brittle or the
+> element structure changes frequently (e.g. PDF previews, dashboard charts, export outputs).
+
+Instead of asserting specific selectors, take a screenshot and ask an AI vision model to
+verify that the expected content is visually present. This decouples the assertion from DOM
+structure and is useful for generated documents or complex layouts.
+
+```typescript
+// fixtures/vision-helper.ts
+import * as https from 'https';
+
+export interface VisionResult {
+  passes: boolean;
+  reason: string;
+  raw?: string;
+}
+
+/**
+ * Sends a screenshot to an AI vision model and asks whether the described
+ * content is visually present. Degrades gracefully when the API key is absent.
+ *
+ * Requires an API key in the environment (e.g. OPENAI_API_KEY for GPT-4o,
+ * or adapt the request body for any other vision-capable model).
+ */
+export async function assertScreenshotShowsContent(
+  screenshotBuffer: Buffer,
+  contentDescription: string,
+  options: { model?: string; degradeOnMissingKey?: boolean } = {}
+): Promise<VisionResult> {
+  const apiKey = process.env.AI_VISION_API_KEY;
+  const degrade = options.degradeOnMissingKey ?? true;
+
+  if (!apiKey) {
+    if (degrade) {
+      console.warn('[vision-helper] AI_VISION_API_KEY not set. Skipping visual assertion.');
+      return { passes: true, reason: 'SKIPPED: AI_VISION_API_KEY not configured' };
+    }
+    return { passes: false, reason: 'AI_VISION_API_KEY not set in environment' };
+  }
+
+  const base64Image = screenshotBuffer.toString('base64');
+  const model = options.model ?? 'gpt-4o';
+
+  const prompt = `You are a QA assistant verifying screenshots of a web application.
+Answer YES or NO: Does the screenshot clearly show ${contentDescription}?
+Reply in exactly this format:
+VERDICT: YES
+REASON: <one short sentence>`;
+
+  const body = JSON.stringify({
+    model,
+    max_tokens: 150,
+    messages: [{
+      role: 'user',
+      content: [
+        { type: 'text', text: prompt },
+        { type: 'image_url', image_url: { url: `data:image/png;base64,${base64Image}`, detail: 'low' } },
+      ],
+    }],
+  });
+
+  const raw = await new Promise<string>((resolve, reject) => {
+    const req = https.request({
+      hostname: 'api.openai.com',
+      path: '/v1/chat/completions',
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/json',
+        'Authorization': `Bearer ${apiKey}`,
+        'Content-Length': Buffer.byteLength(body),
+      },
+    }, (res) => {
+      let data = '';
+      res.on('data', (chunk) => { data += chunk; });
+      res.on('end', () => resolve(data));
+    });
+    req.on('error', reject);
+    req.write(body);
+    req.end();
+  });
+
+  const parsed = JSON.parse(raw);
+  const text: string = parsed.choices?.[0]?.message?.content ?? '';
+  const verdict = text.match(/VERDICT:\s*(YES|NO)/i);
+  const reason  = text.match(/REASON:\s*(.+)/i);
+
+  if (!verdict) return { passes: false, reason: `Unexpected response: ${text}`, raw: text };
+  return {
+    passes: verdict[1].toUpperCase() === 'YES',
+    reason: reason?.[1]?.trim() ?? text,
+    raw: text,
+  };
+}
+```
+
+**Usage in a test:**
+
+```typescript
+import { assertScreenshotShowsContent } from '../fixtures/vision-helper';
+
+test('[TC-MOD-001] Export PDF contains expected content', async ({ page }) => {
+  // ... trigger export ...
+  const screenshot = await page.screenshot();
+  const result = await assertScreenshotShowsContent(
+    screenshot,
+    'a completed export confirmation message with a download link'
+  );
+  expect(result.passes, result.reason).toBe(true);
+});
+```
+
+**Setup notes:**
+
+- Copy `vision-helper.ts` into your `fixtures/` directory.
+- Set `AI_VISION_API_KEY` in your `.env` file (not committed). The example uses the OpenAI
+  API; adapt the request body for any other vision model.
+- By default, the helper degrades to a skip (passes: true) when the key is absent, so CI
+  runs without the key do not fail on this assertion.
+- `pdf-parse` (v2+) exports a `PDFParse` class rather than a function. Use
+  `new PDFParse({ data: buffer })` and call `.getText()` on the instance.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@keber/qa-framework",
-  "version": "1.10.0",
+  "version": "1.11.3",
   "description": "Reusable spec-driven QA framework for IDE-agent-assisted automated testing. Installable as an npm package. Provides structure, templates, agent instructions, and optional integrations for Playwright and Azure DevOps.",
   "keywords": [
     "qa",
@@ -38,10 +38,9 @@
   "engines": {
     "node": ">=18"
   },
-  "devDependencies": {},
   "peerDependencies": {
-    "@playwright/test": ">=1.40.0",
-    "@keber/ado-qa": ">=1.0.0"
+    "@keber/ado-qa": ">=1.0.0",
+    "@playwright/test": ">=1.40.0"
   },
   "peerDependenciesMeta": {
     "@playwright/test": {

package/qa-framework.config.json

@@ -1,6 +1,6 @@
 {
   "$schema": "./qa-framework.config.schema.json",
-  "frameworkVersion": "1.1.3",
+  "frameworkVersion": "1.10.0",
 
   "project": {
     "name": "{{PROJECT_NAME}}",