[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7YM2ACS38HTF2GXZ5DQY2":3,"skill-same:01M7D7YM2ACS38HTF2GXZ5DQY2":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":14,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M7D7YM2ACS38HTF2GXZ5DQY2","Allure Report Generator",null,"Configure and generate rich Allure test reports with test categorization, historical trends, environment details, and CI\u002FCD integration for comprehensive test visibility","GrupoANDevelopment-m\u002Falberto-ai","GrupoANDevelopment-m","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F257455179?v=4","01M7D69X2N2KEVN0SJF6WGM6SH","Antônio  Ndombe","01M7D69X3P5JTT8H8S904N3888",0,"MIT","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Fallure-report-generator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Allure Report Generator\ndescription: Configure and generate rich Allure test reports with test categorization, historical trends, environment details, and CI\u002FCD integration for comprehensive test visibility\nversion: 1.0.0\nauthor: Pramod\nlicense: MIT\ntags: [allure, test-reporting, test-results, ci-reporting, test-history, test-dashboard, reporting-framework]\ntestingTypes: [e2e, integration]\nframeworks: [playwright, jest, pytest]\nlanguages: [typescript, javascript, python, java]\ndomains: [devops]\nagents: [claude-code, cursor, github-copilot, windsurf, codex, aider, continue, cline, zed, bolt, gemini-cli, amp]\n---\n\n# Allure Report Generator\n\nAllure is an open-source test reporting framework that produces rich, interactive HTML reports from test execution results. Unlike basic test reporters that show pass\u002Ffail summaries, Allure provides detailed test categorization, step-by-step execution breakdowns, attachment support for screenshots, logs, and videos, historical trend tracking across builds, and environment metadata. This skill guides AI coding agents through configuring Allure reporters for popular testing frameworks, annotating tests with meaningful metadata, integrating with CI\u002FCD pipelines, and establishing report hosting strategies that give teams comprehensive test visibility.\n\n## Core Principles\n\n1. **Reports Serve Multiple Audiences**: A good test report provides quick pass\u002Ffail summaries for managers, detailed failure analysis for developers, trend data for QA leads, and categorized views for test strategists. Allure's multi-view design supports all these personas from a single report.\n\n2. **Annotations Are Documentation**: Test step annotations, severity labels, and feature\u002Fstory categorization serve as living documentation of test intent. Well-annotated tests in Allure reports communicate what is being tested and why without requiring code access.\n\n3. **Attachments Accelerate Debugging**: Screenshots, DOM snapshots, network logs, and video recordings attached to test steps eliminate the need to reproduce failures locally. Every failure should carry sufficient attachments for diagnosis from the report alone.\n\n4. **History Reveals Patterns**: A single test run is a snapshot. Historical trend data across builds reveals flaky tests that oscillate between pass and fail, degrading tests with gradually increasing failures, and regression patterns that correlate with specific changes.\n\n5. **Categories Group Failures by Root Cause**: Allure categories classify failures by type (product defect, test defect, infrastructure issue) rather than by test name. This grouping accelerates triage by surfacing the most common failure modes across the entire suite.\n\n6. **Environment Context Is Non-Negotiable**: Test results without environment information (browser version, OS, API version, deployment target) are incomplete. The same test can produce different results across environments, and the report must capture this context.\n\n7. **Reports Must Be Accessible**: Test reports that exist only on a developer's local machine provide no team value. Reports must be published to a shared location where all stakeholders can access them without technical setup.\n\n## Project Structure\n\n```\nproject-root\u002F\n├── tests\u002F\n│   ├── e2e\u002F\n│   │   ├── checkout.spec.ts\n│   │   ├── search.spec.ts\n│   │   └── user-management.spec.ts\n│   ├── integration\u002F\n│   │   ├── api-orders.test.ts\n│   │   └── api-users.test.ts\n│   └── fixtures\u002F\n│       └── allure-fixture.ts\n├── allure-results\u002F                    # Raw test results (JSON + attachments)\n│   ├── *-result.json\n│   ├── *-container.json\n│   └── *-attachment.*\n├── allure-report\u002F                     # Generated HTML report\n│   ├── index.html\n│   ├── data\u002F\n│   └── widgets\u002F\n├── config\u002F\n│   ├── playwright.config.ts\n│   ├── jest.config.ts\n│   ├── allure-categories.json\n│   └── allure-environment.properties\n├── scripts\u002F\n│   ├── generate-report.sh\n│   ├── publish-report.ts\n│   └── setup-history.sh\n├── .github\u002F\n│   └── workflows\u002F\n│       └── test-and-report.yml\n└── package.json\n```\n\n## Allure Reporter Setup for Playwright\n\n### Installation and Configuration\n\n```bash\nnpm install --save-dev allure-playwright allure-commandline\n```\n\n```typescript\n\u002F\u002F config\u002Fplaywright.config.ts\nimport { defineConfig, devices } from '@playwright\u002Ftest';\n\nexport default defineConfig({\n  testDir: '.\u002Ftests\u002Fe2e',\n  timeout: 30000,\n  retries: 1,\n\n  reporter: [\n    \u002F\u002F Console output for local development\n    ['list'],\n\n    \u002F\u002F Allure reporter for rich reports\n    [\n      'allure-playwright',\n      {\n        detail: true,\n        outputFolder: 'allure-results',\n        suiteTitle: true,\n\n        \u002F\u002F Attach environment info\n        environmentInfo: {\n          'Node Version': process.version,\n          OS: process.platform,\n          'Test Environment': process.env.TEST_ENV || 'local',\n          'Base URL': process.env.BASE_URL || 'http:\u002F\u002Flocalhost:3000',\n          Browser: 'Chromium',\n          'Playwright Version': require('@playwright\u002Ftest\u002Fpackage.json').version,\n        },\n\n        \u002F\u002F Categories for failure classification\n        categories: [\n          {\n            name: 'Product Defects',\n            matchedStatuses: ['failed'],\n            messageRegex: '.*Expected.*to (be|have|contain).*',\n          },\n          {\n            name: 'Test Infrastructure',\n            matchedStatuses: ['broken'],\n            messageRegex: '.*timeout|ECONNREFUSED|net::ERR.*',\n          },\n          {\n            name: 'Flaky Tests',\n            matchedStatuses: ['failed'],\n            messageRegex: '.*flaky|intermittent.*',\n            traceRegex: '.*retry.*',\n          },\n        ],\n      },\n    ],\n  ],\n\n  use: {\n    baseURL: process.env.BASE_URL || 'http:\u002F\u002Flocalhost:3000',\n    screenshot: 'only-on-failure',\n    video: 'retain-on-failure',\n    trace: 'retain-on-failure',\n  },\n\n  projects: [\n    {\n      name: 'chromium',\n      use: { ...devices['Desktop Chrome'] },\n    },\n    {\n      name: 'firefox',\n      use: { ...devices['Desktop Firefox'] },\n    },\n  ],\n});\n```\n\n### Custom Step Annotations in Playwright\n\n```typescript\n\u002F\u002F tests\u002Fe2e\u002Fcheckout.spec.ts\nimport { test, expect } from '@playwright\u002Ftest';\nimport { allure } from 'allure-playwright';\n\ntest.describe('Checkout Flow', () => {\n  test.beforeEach(async ({ page }) => {\n    await allure.epic('E-Commerce');\n    await allure.feature('Checkout');\n    await allure.owner('team-payments');\n  });\n\n  test('should complete purchase with credit card', async ({ page }) => {\n    await allure.severity('critical');\n    await allure.story('Credit Card Payment');\n    await allure.tag('smoke');\n    await allure.tag('payments');\n\n    \u002F\u002F Add link to test case management system\n    await allure.link('https:\u002F\u002Fjira.example.com\u002Fbrowse\u002FQA-100', 'Test Case', 'tms');\n    await allure.issue('BUG-456', 'https:\u002F\u002Fjira.example.com\u002Fbrowse\u002FBUG-456');\n\n    \u002F\u002F Step 1: Add item to cart\n    await allure.step('Add product to cart', async () => {\n      await page.goto('\u002Fproducts\u002F1');\n      await page.click('[data-testid=\"add-to-cart\"]');\n      await expect(page.locator('[data-testid=\"cart-count\"]')).toHaveText('1');\n\n      \u002F\u002F Attach product page screenshot\n      const screenshot = await page.screenshot();\n      await allure.attachment('Product Page', screenshot, 'image\u002Fpng');\n    });\n\n    \u002F\u002F Step 2: Navigate to checkout\n    await allure.step('Navigate to checkout page', async () => {\n      await page.click('[data-testid=\"cart-icon\"]');\n      await page.click('[data-testid=\"proceed-to-checkout\"]');\n      await expect(page).toHaveURL('\u002Fcheckout');\n    });\n\n    \u002F\u002F Step 3: Fill payment details\n    await allure.step('Enter payment information', async () => {\n      await allure.step('Fill card number', async () => {\n        await page.fill('[data-testid=\"card-number\"]', '4242424242424242');\n      });\n      await allure.step('Fill expiry date', async () => {\n        await page.fill('[data-testid=\"card-expiry\"]', '12\u002F28');\n      });\n      await allure.step('Fill CVV', async () => {\n        await page.fill('[data-testid=\"card-cvv\"]', '123');\n      });\n    });\n\n    \u002F\u002F Step 4: Submit order\n    await allure.step('Place order', async () => {\n      await page.click('[data-testid=\"place-order\"]');\n      await expect(page.locator('[data-testid=\"order-confirmation\"]')).toBeVisible({\n        timeout: 15000,\n      });\n\n      \u002F\u002F Capture confirmation details\n      const confirmationText = await page\n        .locator('[data-testid=\"order-confirmation\"]')\n        .textContent();\n      await allure.attachment('Order Confirmation', confirmationText || '', 'text\u002Fplain');\n    });\n\n    \u002F\u002F Step 5: Verify order details\n    await allure.step('Verify order details', async () => {\n      const orderId = await page.locator('[data-testid=\"order-id\"]').textContent();\n      expect(orderId).toBeTruthy();\n\n      \u002F\u002F Attach full page screenshot\n      const fullPage = await page.screenshot({ fullPage: true });\n      await allure.attachment('Confirmation Page', fullPage, 'image\u002Fpng');\n\n      \u002F\u002F Attach API response for debugging\n      const orderDetails = await page.evaluate(async (id) => {\n        const res = await fetch(`\u002Fapi\u002Forders\u002F${id}`);\n        return res.json();\n      }, orderId);\n      await allure.attachment(\n        'Order API Response',\n        JSON.stringify(orderDetails, null, 2),\n        'application\u002Fjson'\n      );\n    });\n  });\n\n  test('should show validation errors for invalid card', async ({ page }) => {\n    await allure.severity('normal');\n    await allure.story('Payment Validation');\n\n    await page.goto('\u002Fcheckout');\n\n    await allure.step('Submit empty payment form', async () => {\n      await page.click('[data-testid=\"place-order\"]');\n    });\n\n    await allure.step('Verify validation errors displayed', async () => {\n      await expect(page.locator('[data-testid=\"card-error\"]')).toHaveText(\n        'Card number is required'\n      );\n      await expect(page.locator('[data-testid=\"expiry-error\"]')).toHaveText(\n        'Expiry date is required'\n      );\n    });\n  });\n});\n```\n\n### Custom Allure Fixture for Reusable Annotations\n\n```typescript\n\u002F\u002F tests\u002Ffixtures\u002Fallure-fixture.ts\nimport { test as base } from '@playwright\u002Ftest';\nimport { allure } from 'allure-playwright';\n\ninterface AllureOptions {\n  epic: string;\n  feature: string;\n  severity: 'blocker' | 'critical' | 'normal' | 'minor' | 'trivial';\n}\n\nexport const test = base.extend\u003C{ allureConfig: AllureOptions }>({\n  allureConfig: [\n    async ({}, use, testInfo) => {\n      \u002F\u002F Auto-derive categorization from test file path\n      const filePath = testInfo.file;\n      let epic = 'General';\n      let feature = 'Uncategorized';\n\n      if (filePath.includes('checkout')) {\n        epic = 'E-Commerce';\n        feature = 'Checkout';\n      } else if (filePath.includes('search')) {\n        epic = 'Discovery';\n        feature = 'Search';\n      } else if (filePath.includes('user')) {\n        epic = 'Account';\n        feature = 'User Management';\n      }\n\n      await allure.epic(epic);\n      await allure.feature(feature);\n\n      \u002F\u002F Attach test metadata\n      await allure.parameter('Browser', testInfo.project.name);\n      await allure.parameter('Retry Attempt', String(testInfo.retry));\n\n      const options: AllureOptions = {\n        epic,\n        feature,\n        severity: 'normal',\n      };\n\n      await use(options);\n\n      \u002F\u002F After test: attach trace on failure\n      if (testInfo.status !== 'passed') {\n        const tracePath = testInfo.outputPath('trace.zip');\n        try {\n          const traceBuffer = require('fs').readFileSync(tracePath);\n          await allure.attachment('Playwright Trace', traceBuffer, 'application\u002Fzip');\n        } catch {\n          \u002F\u002F Trace not available\n        }\n      }\n    },\n    { auto: true },\n  ],\n});\n\nexport { expect } from '@playwright\u002Ftest';\n```\n\n## Allure Reporter Setup for Jest\n\n```bash\nnpm install --save-dev allure-jest allure-js-commons allure-commandline\n```\n\n```typescript\n\u002F\u002F config\u002Fjest.config.ts\nimport type { Config } from 'jest';\n\nconst config: Config = {\n  preset: 'ts-jest',\n  testEnvironment: 'allure-jest\u002Fnode',\n  testEnvironmentOptions: {\n    resultsDir: 'allure-results',\n    environmentInfo: {\n      'Node Version': process.version,\n      OS: process.platform,\n      'Test Environment': process.env.TEST_ENV || 'local',\n    },\n  },\n  reporters: ['default'],\n};\n\nexport default config;\n```\n\n### Jest Test with Allure Annotations\n\n```typescript\n\u002F\u002F tests\u002Fintegration\u002Fapi-orders.test.ts\nimport { allure } from 'allure-js-commons';\n\ndescribe('Orders API', () => {\n  beforeAll(async () => {\n    await allure.epic('API');\n    await allure.feature('Orders');\n  });\n\n  it('should create a new order', async () => {\n    await allure.severity('critical');\n    await allure.story('Order Creation');\n    await allure.owner('team-orders');\n    await allure.tag('api');\n    await allure.tag('smoke');\n\n    await allure.step('Prepare order payload', async () => {\n      const payload = {\n        customerId: 42,\n        items: [{ productId: 'prod-001', quantity: 2 }],\n        shippingAddress: {\n          street: '123 Main St',\n          city: 'Portland',\n          state: 'OR',\n          zip: '97201',\n        },\n      };\n      await allure.attachment(\n        'Request Payload',\n        JSON.stringify(payload, null, 2),\n        'application\u002Fjson'\n      );\n\n      await allure.step('Send POST request', async () => {\n        const response = await fetch('http:\u002F\u002Flocalhost:3000\u002Fapi\u002Forders', {\n          method: 'POST',\n          headers: { 'Content-Type': 'application\u002Fjson' },\n          body: JSON.stringify(payload),\n        });\n\n        expect(response.status).toBe(201);\n\n        const body = await response.json();\n        await allure.attachment(\n          'Response Body',\n          JSON.stringify(body, null, 2),\n          'application\u002Fjson'\n        );\n\n        await allure.step('Verify order ID assigned', async () => {\n          expect(body.id).toBeDefined();\n          expect(typeof body.id).toBe('string');\n        });\n\n        await allure.step('Verify order total calculated', async () => {\n          expect(body.total).toBeGreaterThan(0);\n        });\n      });\n    });\n  });\n\n  it('should return 400 for invalid order', async () => {\n    await allure.severity('normal');\n    await allure.story('Order Validation');\n\n    await allure.step('Send order without required fields', async () => {\n      const response = await fetch('http:\u002F\u002Flocalhost:3000\u002Fapi\u002Forders', {\n        method: 'POST',\n        headers: { 'Content-Type': 'application\u002Fjson' },\n        body: JSON.stringify({}),\n      });\n\n      expect(response.status).toBe(400);\n\n      const body = await response.json();\n      await allure.attachment(\n        'Error Response',\n        JSON.stringify(body, null, 2),\n        'application\u002Fjson'\n      );\n\n      await allure.step('Verify error details', async () => {\n        expect(body.errors).toBeDefined();\n        expect(body.errors.length).toBeGreaterThan(0);\n      });\n    });\n  });\n});\n```\n\n## Allure Reporter Setup for pytest\n\n```bash\npip install allure-pytest\n```\n\n```ini\n# pytest.ini\n[pytest]\naddopts = --alluredir=allure-results --clean-alluredir\n```\n\n### Python Test with Allure Annotations\n\n```python\n# tests\u002Ftest_user_api.py\nimport allure\nimport pytest\nimport requests\nimport json\n\nBASE_URL = \"http:\u002F\u002Flocalhost:8000\"\n\n\n@allure.epic(\"API\")\n@allure.feature(\"User Management\")\nclass TestUserAPI:\n\n    @allure.severity(allure.severity_level.CRITICAL)\n    @allure.story(\"User Registration\")\n    @allure.title(\"Register a new user with valid data\")\n    @allure.tag(\"api\", \"smoke\", \"registration\")\n    @allure.link(\"https:\u002F\u002Fjira.example.com\u002Fbrowse\u002FQA-200\", name=\"Test Case\")\n    def test_register_user(self):\n        payload = {\n            \"name\": \"Jane Doe\",\n            \"email\": \"jane@example.com\",\n            \"password\": \"SecureP@ss123\",\n        }\n\n        with allure.step(\"Prepare registration payload\"):\n            allure.attach(\n                json.dumps(payload, indent=2),\n                name=\"Request Payload\",\n                attachment_type=allure.attachment_type.JSON,\n            )\n\n        with allure.step(\"Send POST \u002Fapi\u002Fusers\u002Fregister\"):\n            response = requests.post(\n                f\"{BASE_URL}\u002Fapi\u002Fusers\u002Fregister\", json=payload\n            )\n\n            allure.attach(\n                json.dumps(response.json(), indent=2),\n                name=\"Response Body\",\n                attachment_type=allure.attachment_type.JSON,\n            )\n\n            allure.attach(\n                str(response.status_code),\n                name=\"Status Code\",\n                attachment_type=allure.attachment_type.TEXT,\n            )\n\n        with allure.step(\"Verify registration succeeded\"):\n            assert response.status_code == 201\n            body = response.json()\n            assert \"id\" in body\n            assert body[\"email\"] == \"jane@example.com\"\n\n        with allure.step(\"Verify user can authenticate\"):\n            login_response = requests.post(\n                f\"{BASE_URL}\u002Fapi\u002Fauth\u002Flogin\",\n                json={\n                    \"email\": \"jane@example.com\",\n                    \"password\": \"SecureP@ss123\",\n                },\n            )\n            assert login_response.status_code == 200\n            assert \"token\" in login_response.json()\n\n    @allure.severity(allure.severity_level.NORMAL)\n    @allure.story(\"User Registration\")\n    @allure.title(\"Reject registration with duplicate email\")\n    def test_register_duplicate_email(self):\n        payload = {\n            \"name\": \"Duplicate\",\n            \"email\": \"existing@example.com\",\n            \"password\": \"Pass123!\",\n        }\n\n        with allure.step(\"Register user with existing email\"):\n            response = requests.post(\n                f\"{BASE_URL}\u002Fapi\u002Fusers\u002Fregister\", json=payload\n            )\n\n        with allure.step(\"Verify conflict error returned\"):\n            assert response.status_code == 409\n            assert \"already exists\" in response.json()[\"message\"]\n\n    @allure.severity(allure.severity_level.CRITICAL)\n    @allure.story(\"User Profile\")\n    @allure.title(\"Retrieve user profile with valid token\")\n    def test_get_user_profile(self, auth_token):\n        with allure.step(\"Send GET \u002Fapi\u002Fusers\u002Fme with auth token\"):\n            response = requests.get(\n                f\"{BASE_URL}\u002Fapi\u002Fusers\u002Fme\",\n                headers={\"Authorization\": f\"Bearer {auth_token}\"},\n            )\n\n            allure.attach(\n                json.dumps(response.json(), indent=2),\n                name=\"Profile Response\",\n                attachment_type=allure.attachment_type.JSON,\n            )\n\n        with allure.step(\"Verify profile data\"):\n            assert response.status_code == 200\n            profile = response.json()\n            assert \"id\" in profile\n            assert \"name\" in profile\n            assert \"email\" in profile\n            assert \"password\" not in profile  # Verify password not exposed\n\n\n@pytest.fixture\ndef auth_token():\n    \"\"\"Fixture that provides an authenticated user token.\"\"\"\n    with allure.step(\"Authenticate test user\"):\n        response = requests.post(\n            f\"{BASE_URL}\u002Fapi\u002Fauth\u002Flogin\",\n            json={\n                \"email\": \"test@example.com\",\n                \"password\": \"TestPass123!\",\n            },\n        )\n        return response.json()[\"token\"]\n```\n\n## Environment Info Configuration\n\n```properties\n# config\u002Fallure-environment.properties\n# This file is copied to allure-results\u002F before report generation\nBrowser=Chromium 120\nOS=Ubuntu 22.04\nNode.Version=20.10.0\nTest.Environment=staging\nAPI.Base.URL=https:\u002F\u002Fstaging-api.example.com\nApp.Version=2.5.0\nBuild.Number=${BUILD_NUMBER}\nGit.Commit=${GIT_COMMIT}\nGit.Branch=${GIT_BRANCH}\nDeployment.Region=us-east-1\nDatabase=PostgreSQL 16\n```\n\n### Dynamic Environment Properties Script\n\n```typescript\n\u002F\u002F scripts\u002Fgenerate-environment.ts\nimport * as fs from 'fs';\nimport { execSync } from 'child_process';\n\nconst gitCommit = execSync('git rev-parse --short HEAD', { encoding: 'utf-8' }).trim();\nconst gitBranch = execSync('git rev-parse --abbrev-ref HEAD', { encoding: 'utf-8' }).trim();\n\nconst properties = [\n  `Browser=${process.env.BROWSER || 'Chromium'}`,\n  `OS=${process.platform} ${process.arch}`,\n  `Node.Version=${process.version}`,\n  `Test.Environment=${process.env.TEST_ENV || 'local'}`,\n  `Base.URL=${process.env.BASE_URL || 'http:\u002F\u002Flocalhost:3000'}`,\n  `Git.Commit=${gitCommit}`,\n  `Git.Branch=${gitBranch}`,\n  `Build.Number=${process.env.BUILD_NUMBER || 'local'}`,\n  `Timestamp=${new Date().toISOString()}`,\n].join('\\n');\n\nfs.writeFileSync('allure-results\u002Fenvironment.properties', properties);\nconsole.log('Environment properties written to allure-results\u002Fenvironment.properties');\n```\n\n## Categories and Severity Labeling\n\n### Categories Configuration\n\n```json\n\u002F\u002F config\u002Fallure-categories.json\n[\n  {\n    \"name\": \"Product Defects\",\n    \"description\": \"Failures caused by actual application bugs\",\n    \"matchedStatuses\": [\"failed\"],\n    \"messageRegex\": \".*Expected .* (to be|to have|to contain|to equal).*\"\n  },\n  {\n    \"name\": \"Test Infrastructure Issues\",\n    \"description\": \"Failures caused by test environment problems\",\n    \"matchedStatuses\": [\"broken\"],\n    \"messageRegex\": \".*(timeout|ECONNREFUSED|ENOTFOUND|ETIMEDOUT|net::ERR|Navigation).*\"\n  },\n  {\n    \"name\": \"Element Not Found\",\n    \"description\": \"Failures where expected UI elements are missing\",\n    \"matchedStatuses\": [\"failed\"],\n    \"messageRegex\": \".*(locator|selector|element).*(not found|not visible|not attached).*\"\n  },\n  {\n    \"name\": \"API Errors\",\n    \"description\": \"Failures in API response validation\",\n    \"matchedStatuses\": [\"failed\"],\n    \"messageRegex\": \".*(status code|response|4\\\\d{2}|5\\\\d{2}).*\"\n  },\n  {\n    \"name\": \"Data Setup Failures\",\n    \"description\": \"Failures in test fixture or data preparation\",\n    \"matchedStatuses\": [\"broken\"],\n    \"traceRegex\": \".*(beforeAll|beforeEach|fixture|setup).*\"\n  },\n  {\n    \"name\": \"Outdated Tests\",\n    \"description\": \"Tests that need updating due to application changes\",\n    \"matchedStatuses\": [\"failed\"],\n    \"messageRegex\": \".*(deprecated|removed|changed|no longer).*\"\n  }\n]\n```\n\n### Copying Categories to Results\n\n```bash\n#!\u002Fbin\u002Fbash\n# scripts\u002Fgenerate-report.sh\n\n# Copy categories to allure-results (must be present before generation)\ncp config\u002Fallure-categories.json allure-results\u002Fcategories.json\n\n# Generate environment properties\nnpx ts-node scripts\u002Fgenerate-environment.ts\n\n# Copy history from previous report (for trends)\nif [ -d \"allure-report\u002Fhistory\" ]; then\n  cp -r allure-report\u002Fhistory allure-results\u002Fhistory\nfi\n\n# Generate the report\nnpx allure generate allure-results --clean -o allure-report\n\necho \"Report generated at allure-report\u002Findex.html\"\n```\n\n## Historical Trend Tracking\n\n### Preserving History Across Builds\n\n```bash\n#!\u002Fbin\u002Fbash\n# scripts\u002Fsetup-history.sh\n# Run before each test execution to preserve historical data\n\nHISTORY_DIR=\"allure-results\u002Fhistory\"\nREPORT_HISTORY=\"allure-report\u002Fhistory\"\n\n# If a previous report exists, copy its history to the new results directory\nif [ -d \"$REPORT_HISTORY\" ]; then\n  mkdir -p \"$HISTORY_DIR\"\n  cp -r \"$REPORT_HISTORY\u002F\"* \"$HISTORY_DIR\u002F\"\n  echo \"History preserved from previous report\"\nelse\n  echo \"No previous history found (first run)\"\nfi\n```\n\n### CI History Preservation with Artifacts\n\n```yaml\n# In a GitHub Actions workflow, history is preserved via artifacts\n- name: Download previous report history\n  uses: actions\u002Fdownload-artifact@v4\n  with:\n    name: allure-report-history\n    path: allure-results\u002Fhistory\n  continue-on-error: true  # First run will not have history\n\n# After report generation\n- name: Save report history\n  uses: actions\u002Fupload-artifact@v4\n  with:\n    name: allure-report-history\n    path: allure-report\u002Fhistory\n    retention-days: 30\n```\n\n## CI Integration\n\n### GitHub Actions Complete Workflow\n\n```yaml\n# .github\u002Fworkflows\u002Ftest-and-report.yml\nname: Test and Report\non:\n  push:\n    branches: [main, develop]\n  pull_request:\n    branches: [main]\n\npermissions:\n  contents: read\n  pages: write\n  id-token: write\n\njobs:\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: 20\n      - run: npm ci\n      - run: npx playwright install --with-deps\n\n      # Download previous Allure history for trends\n      - name: Restore Allure history\n        uses: actions\u002Fdownload-artifact@v4\n        with:\n          name: allure-history\n          path: allure-results\u002Fhistory\n        continue-on-error: true\n\n      # Run tests\n      - name: Run Playwright tests\n        run: npx playwright test\n        continue-on-error: true\n        env:\n          BASE_URL: ${{ secrets.STAGING_URL }}\n          TEST_ENV: ci\n\n      # Generate environment properties\n      - name: Generate environment info\n        run: |\n          cat > allure-results\u002Fenvironment.properties \u003C\u003C EOF\n          Browser=Chromium\n          OS=Ubuntu (CI)\n          Node.Version=$(node --version)\n          Test.Environment=CI\n          Git.Commit=${{ github.sha }}\n          Git.Branch=${{ github.ref_name }}\n          Build.Number=${{ github.run_number }}\n          PR.Number=${{ github.event.pull_request.number || 'N\u002FA' }}\n          EOF\n\n      # Copy categories\n      - name: Setup Allure categories\n        run: cp config\u002Fallure-categories.json allure-results\u002Fcategories.json\n\n      # Generate report\n      - name: Generate Allure Report\n        run: |\n          npm install -g allure-commandline\n          allure generate allure-results --clean -o allure-report\n\n      # Save history for next run\n      - name: Save Allure history\n        uses: actions\u002Fupload-artifact@v4\n        if: always()\n        with:\n          name: allure-history\n          path: allure-report\u002Fhistory\n          retention-days: 60\n\n      # Upload full report\n      - name: Upload Allure Report\n        uses: actions\u002Fupload-artifact@v4\n        if: always()\n        with:\n          name: allure-report\n          path: allure-report\u002F\n          retention-days: 30\n\n  # Deploy report to GitHub Pages\n  deploy-report:\n    needs: test\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    runs-on: ubuntu-latest\n    environment:\n      name: github-pages\n      url: ${{ steps.deployment.outputs.page_url }}\n    steps:\n      - uses: actions\u002Fdownload-artifact@v4\n        with:\n          name: allure-report\n          path: allure-report\n\n      - uses: actions\u002Fconfigure-pages@v4\n      - uses: actions\u002Fupload-pages-artifact@v3\n        with:\n          path: allure-report\n      - id: deployment\n        uses: actions\u002Fdeploy-pages@v4\n```\n\n### Jenkins Pipeline Integration\n\n```groovy\n\u002F\u002F Jenkinsfile\npipeline {\n    agent any\n\n    stages {\n        stage('Test') {\n            steps {\n                sh 'npm ci'\n                sh 'npx playwright install --with-deps'\n                sh 'npx playwright test || true'\n            }\n            post {\n                always {\n                    \u002F\u002F Copy environment properties\n                    sh '''\n                        echo \"Browser=Chromium\" > allure-results\u002Fenvironment.properties\n                        echo \"Build.Number=${BUILD_NUMBER}\" >> allure-results\u002Fenvironment.properties\n                        echo \"Git.Commit=${GIT_COMMIT}\" >> allure-results\u002Fenvironment.properties\n                        echo \"Node.Version=$(node --version)\" >> allure-results\u002Fenvironment.properties\n                    '''\n\n                    \u002F\u002F Jenkins Allure plugin generates report and preserves history\n                    allure([\n                        includeProperties: true,\n                        jdk: '',\n                        properties: [],\n                        reportBuildPolicy: 'ALWAYS',\n                        results: [[path: 'allure-results']]\n                    ])\n                }\n            }\n        }\n    }\n}\n```\n\n## Allure TestOps Overview\n\nAllure TestOps is the commercial companion to Allure Report, providing centralized test management, real-time dashboards, and analytics across multiple projects.\n\n```typescript\n\u002F\u002F Integration with Allure TestOps (if available)\n\u002F\u002F config\u002Fallure-testops.config.ts\nexport const testOpsConfig = {\n  \u002F\u002F TestOps server configuration\n  endpoint: process.env.ALLURE_TESTOPS_URL || 'https:\u002F\u002Fallure.example.com',\n  token: process.env.ALLURE_TESTOPS_TOKEN,\n  projectId: parseInt(process.env.ALLURE_PROJECT_ID || '1'),\n\n  \u002F\u002F Launch configuration\n  launchName: `${process.env.GIT_BRANCH || 'local'} - ${new Date().toISOString()}`,\n  launchTags: [process.env.TEST_ENV || 'local', process.env.GIT_BRANCH || 'unknown'],\n};\n\n\u002F\u002F Upload results to TestOps after test execution:\n\u002F\u002F npx allurectl upload allure-results \\\n\u002F\u002F   --endpoint $ALLURE_TESTOPS_URL \\\n\u002F\u002F   --token $ALLURE_TESTOPS_TOKEN \\\n\u002F\u002F   --project-id 1\n```\n\n## Custom Widgets\n\nAllure reports support custom widgets that display aggregated data on the report overview page.\n\n```json\n\u002F\u002F allure-results\u002Fwidgets\u002Fsummary.json (custom widget data)\n{\n  \"reportName\": \"E-Commerce Test Suite\",\n  \"testRuns\": [\n    {\n      \"name\": \"Smoke Tests\",\n      \"total\": 25,\n      \"passed\": 24,\n      \"failed\": 1,\n      \"broken\": 0,\n      \"skipped\": 0\n    },\n    {\n      \"name\": \"Regression Tests\",\n      \"total\": 150,\n      \"passed\": 142,\n      \"failed\": 5,\n      \"broken\": 2,\n      \"skipped\": 1\n    }\n  ],\n  \"environment\": \"Staging\",\n  \"duration\": \"12m 34s\"\n}\n```\n\n## Report Hosting Strategies\n\n### Strategy 1: GitHub Pages (Free, Public)\n\n```bash\n# Deploy to GitHub Pages using gh-pages package\nnpm install -g gh-pages\n\n# Generate and deploy\nallure generate allure-results -o allure-report\ngh-pages -d allure-report -m \"Allure Report $(date +%Y-%m-%d)\"\n```\n\n### Strategy 2: S3 Static Hosting (Private, Scalable)\n\n```typescript\n\u002F\u002F scripts\u002Fpublish-report.ts\nimport { S3Client, PutObjectCommand } from '@aws-sdk\u002Fclient-s3';\nimport * as fs from 'fs';\nimport * as path from 'path';\nimport * as mime from 'mime-types';\n\nconst s3 = new S3Client({ region: process.env.AWS_REGION || 'us-east-1' });\nconst BUCKET = process.env.REPORT_BUCKET || 'test-reports';\nconst PREFIX = `allure\u002F${process.env.GIT_BRANCH || 'main'}\u002F${Date.now()}`;\n\nasync function uploadDirectory(dirPath: string, s3Prefix: string): Promise\u003Cvoid> {\n  const entries = fs.readdirSync(dirPath, { withFileTypes: true });\n\n  for (const entry of entries) {\n    const fullPath = path.join(dirPath, entry.name);\n    const s3Key = `${s3Prefix}\u002F${entry.name}`;\n\n    if (entry.isDirectory()) {\n      await uploadDirectory(fullPath, s3Key);\n    } else {\n      const contentType = mime.lookup(entry.name) || 'application\u002Foctet-stream';\n      await s3.send(\n        new PutObjectCommand({\n          Bucket: BUCKET,\n          Key: s3Key,\n          Body: fs.readFileSync(fullPath),\n          ContentType: contentType,\n        })\n      );\n    }\n  }\n}\n\nasync function main() {\n  console.log(`Uploading report to s3:\u002F\u002F${BUCKET}\u002F${PREFIX}\u002F`);\n  await uploadDirectory('allure-report', PREFIX);\n  console.log(`Report available at: https:\u002F\u002F${BUCKET}.s3.amazonaws.com\u002F${PREFIX}\u002Findex.html`);\n}\n\nmain().catch(console.error);\n```\n\n### Strategy 3: Docker Container (Self-Hosted)\n\n```yaml\n# docker-compose.yml for self-hosted Allure report server\nversion: '3.8'\nservices:\n  allure-server:\n    image: frankescobar\u002Fallure-docker-service:latest\n    ports:\n      - \"5050:5050\"\n    environment:\n      CHECK_RESULTS_EVERY_SECONDS: 5\n      KEEP_HISTORY: 25\n    volumes:\n      - .\u002Fallure-results:\u002Fapp\u002Fallure-results\n      - .\u002Fallure-reports:\u002Fapp\u002Fdefault-reports\n```\n\n## Configuration\n\n### Package.json Scripts\n\n```json\n{\n  \"scripts\": {\n    \"test\": \"playwright test\",\n    \"test:report\": \"playwright test && npm run allure:generate\",\n    \"allure:generate\": \"bash scripts\u002Fgenerate-report.sh\",\n    \"allure:open\": \"allure open allure-report\",\n    \"allure:serve\": \"allure serve allure-results\",\n    \"allure:clean\": \"rm -rf allure-results allure-report\",\n    \"allure:history\": \"bash scripts\u002Fsetup-history.sh\",\n    \"allure:publish\": \"ts-node scripts\u002Fpublish-report.ts\"\n  }\n}\n```\n\n### Allure Commandline Installation\n\n```bash\n# Via npm (recommended for JavaScript projects)\nnpm install -g allure-commandline\n\n# Via Homebrew (macOS)\nbrew install allure\n\n# Via scoop (Windows)\nscoop install allure\n\n# Verify installation\nallure --version\n```\n\n## Best Practices\n\n1. **Annotate every test with severity.** Use Allure severity levels (blocker, critical, normal, minor, trivial) consistently. This enables filtering the report by severity during triage sessions.\n\n2. **Organize tests with epic\u002Ffeature\u002Fstory hierarchy.** Map tests to the product feature hierarchy so the Allure Behaviors view reflects the actual product structure. This helps stakeholders navigate reports by business functionality.\n\n3. **Attach screenshots and videos on failure only.** Recording screenshots and videos for all tests inflates report size without benefit. Configure `screenshot: 'only-on-failure'` and `video: 'retain-on-failure'`.\n\n4. **Use meaningful step descriptions.** Steps should describe intent (\"Add product to cart\"), not implementation (\"Click button with data-testid add-to-cart\"). Report readers may not have code access.\n\n5. **Configure categories to match your failure taxonomy.** Customize `categories.json` to classify failures into actionable groups. Default categories are too generic for effective triage.\n\n6. **Preserve history across CI builds.** Without history, trend charts are empty and test retries lack context. Use CI artifacts or external storage to maintain history for at least 20-30 builds.\n\n7. **Generate environment properties dynamically.** Hardcoded environment files become stale. Generate them from CI environment variables and git metadata at report generation time.\n\n8. **Attach API request\u002Fresponse pairs for API tests.** When API tests fail, the request payload and response body attached to the report step eliminate the need to reproduce the failure locally.\n\n9. **Include links to test case management and issue tracking.** Use `allure.link()` and `allure.issue()` to connect report entries to external systems. This creates bidirectional traceability between reports and project management tools.\n\n10. **Host reports on a persistent URL.** Ephemeral reports in CI artifacts are hard to share. Deploy to GitHub Pages, S3, or a dedicated report server where stakeholders can always find the latest report.\n\n11. **Set up Slack or email notifications for report availability.** After CI generates a report, notify the team with a direct link. Reports that nobody opens provide no value.\n\n12. **Review report trends weekly.** Schedule a brief weekly review of the Allure trend view to catch increasing failure rates, growing test suite duration, or emerging flaky test patterns before they become systemic problems.\n\n## Anti-Patterns to Avoid\n\n1. **Generating reports without categories configuration.** Without categories, all failures appear in a single undifferentiated list. Categories enable meaningful failure classification that accelerates triage.\n\n2. **Over-attaching large files to every test.** Attaching multi-megabyte videos or full HAR files to every test (including passing tests) creates enormous reports that are slow to generate, upload, and browse.\n\n3. **Using generic step names.** Steps labeled \"Step 1\", \"Step 2\", or \"Verification\" provide no value. Each step name should clearly describe what is happening and why.\n\n4. **Ignoring the Allure report trend view.** Running Allure without preserving history across builds discards the most valuable feature: the ability to see trends and identify degradation over time.\n\n5. **Skipping environment configuration.** A report without environment details cannot be interpreted correctly. The same test result means different things on Chrome vs Firefox, or staging vs production.\n\n6. **Treating report generation as an afterthought.** Report configuration should be established early in the project, not bolted on when stakeholders demand visibility. Retrofit is always harder than upfront setup.\n\n7. **Not cleaning allure-results between runs.** If old results are not cleared before new test runs, the report will contain stale data from previous executions, creating confusion about current test status.\n\n## Debugging Tips\n\n1. **Check allure-results directory for raw data.** If the report looks wrong, inspect the JSON files in `allure-results\u002F`. Each test produces a `-result.json` file containing all metadata, steps, and attachment references.\n\n2. **Verify categories.json is in allure-results before generation.** The categories file must be present in the results directory when the report is generated. Placing it only in the config directory without copying produces a report with no category classifications.\n\n3. **Validate environment.properties format.** The file must use `key=value` format with no quotes around values. Malformed properties are silently ignored, resulting in missing environment information in the report.\n\n4. **Check attachment file references.** If attachments show as broken links in the report, verify that the attachment files exist in `allure-results\u002F` and that the file names in the result JSON match the actual files on disk.\n\n5. **Use allure serve for quick local preview.** The `allure serve allure-results` command generates a temporary report and opens it in a browser without creating the persistent `allure-report` directory. This is the fastest way to preview results during development.\n\n6. **Verify allure-commandline version compatibility.** Allure Report and the framework reporters must use compatible versions. Check the compatibility matrix in the Allure documentation if reports appear empty or malformatted.\n\n7. **Inspect the history directory structure.** Trend charts require a specific directory structure in `allure-results\u002Fhistory\u002F`. If trends are not appearing, verify that `history.json` and `history-trend.json` from the previous report were correctly copied to the results directory.\n\n8. **Check for conflicting reporters.** Running multiple reporters that write to the same output directory can cause data corruption. Ensure each reporter writes to a distinct directory or uses the framework's built-in multi-reporter support.\n\n9. **Review CI artifact retention policies.** If history suddenly stops working in CI, check whether artifact retention policies expired. History artifacts need to persist across builds, so set retention days appropriately (30-60 days minimum).\n\n10. **Test report generation locally before CI.** Always verify that `allure generate allure-results -o allure-report` works locally with representative test data before debugging CI-specific report issues.\n","# Allure Report Generator\n\nAllure is an open-source test reporting framework that produces rich, interactive HTML reports from test execution results. Unlike basic test reporters that show pass\u002Ffail summaries, Allure provides detailed test categorization, step-by-step execution breakdowns, attachment support for screenshots, logs, and videos, historical trend tracking across builds, and environment metadata. This skill guides AI coding agents through configuring Allure reporters for popular testing frameworks, annotating tests with meaningful metadata, integrating with CI\u002FCD pipelines, and establishing report hosting strategies that give teams comprehensive test visibility.\n\n## Core Principles\n\n1. **Reports Serve Multiple Audiences**: A good test report provides quick pass\u002Ffail summaries for managers, detailed failure analysis for developers, trend data for QA leads, and categorized views for test strategists. Allure's multi-view design supports all these personas from a single report.\n\n2. **Annotations Are Documentation**: Test step annotations, severity labels, and feature\u002Fstory categorization serve as living documentation of test intent. Well-annotated tests in Allure reports communicate what is being tested and why without requiring code access.\n\n3. **Attachments Accelerate Debugging**: Screenshots, DOM snapshots, network logs, and video recordings attached to test steps eliminate the need to reproduce failures locally. Every failure should carry sufficient attachments for diagnosis from the report alone.\n\n4. **History Reveals Patterns**: A single test run is a snapshot. Historical trend data across builds reveals flaky tests that oscillate between pass and fail, degrading tests with gradually increasing failures, and regression patterns that correlate with specific changes.\n\n5. **Categories Group Failures by Root Cause**: Allure categories classify failures by type (product defect, test defect, infrastructure issue) rather than by test name. This grouping accelerates triage by surfacing the most common failure modes across the entire suite.\n\n6. **Environment Context Is Non-Negotiable**: Test results without environment information (browser version, OS, API version, deployment target) are incomplete. The same test can produce different results across environments, and the report must capture this context.\n\n7. **Reports Must Be Accessible**: Test reports that exist only on a developer's local machine provide no team value. Reports must be published to a shared location where all stakeholders can access them without technical setup.\n\n## Project Structure\n\n```\nproject-root\u002F\n├── tests\u002F\n│   ├── e2e\u002F\n│   │   ├── checkout.spec.ts\n│   │   ├── search.spec.ts\n│   │   └── user-management.spec.ts\n│   ├── integration\u002F\n│   │   ├── api-orders.test.ts\n│   │   └── api-users.test.ts\n│   └── fixtures\u002F\n│       └── allure-fixture.ts\n├── allure-results\u002F                    # Raw test results (JSON + attachments)\n│   ├── *-result.json\n│   ├── *-container.json\n│   └── *-attachment.*\n├── allure-report\u002F                     # Generated HTML report\n│   ├── index.html\n│   ├── data\u002F\n│   └── widgets\u002F\n├── config\u002F\n│   ├── playwright.config.ts\n│   ├── jest.config.ts\n│   ├── allure-categories.json\n│   └── allure-environment.properties\n├── scripts\u002F\n│   ├── generate-report.sh\n│   ├── publish-report.ts\n│   └── setup-history.sh\n├── .github\u002F\n│   └── workflows\u002F\n│       └── test-and-report.yml\n└── package.json\n```\n\n## Allure Reporter Setup for Playwright\n\n### Installation and Configuration\n\n```bash\nnpm install --save-dev allure-playwright allure-commandline\n```\n\n```typescript\n\u002F\u002F config\u002Fplaywright.config.ts\nimport { defineConfig, devices } from '@playwright\u002Ftest';\n\nexport default defineConfig({\n  testDir: '.\u002Ftests\u002Fe2e',\n  timeout: 30000,\n  retries: 1,\n\n  reporter: [\n    \u002F\u002F Console output for local development\n    ['list'],\n\n    \u002F\u002F Allure reporter for rich reports\n    [\n      'allure-playwright',\n      {\n        detail: true,\n        outputFolder: 'allure-results',\n        suiteTitle: true,\n\n        \u002F\u002F Attach environment info\n        environmentInfo: {\n          'Node Version': process.version,\n          OS: process.platform,\n          'Test Environment': process.env.TEST_ENV || 'local',\n          'Base URL': process.env.BASE_URL || 'http:\u002F\u002Flocalhost:3000',\n          Browser: 'Chromium',\n          'Playwright Version': require('@playwright\u002Ftest\u002Fpackage.json').version,\n        },\n\n        \u002F\u002F Categories for failure classification\n        categories: [\n          {\n            name: 'Product Defects',\n            matchedStatuses: ['failed'],\n            messageRegex: '.*Expected.*to (be|have|contain).*',\n          },\n          {\n            name: 'Test Infrastructure',\n            matchedStatuses: ['broken'],\n            messageRegex: '.*timeout|ECONNREFUSED|net::ERR.*',\n          },\n          {\n            name: 'Flaky Tests',\n            matchedStatuses: ['failed'],\n            messageRegex: '.*flaky|intermittent.*',\n            traceRegex: '.*retry.*',\n          },\n        ],\n      },\n    ],\n  ],\n\n  use: {\n    baseURL: process.env.BASE_URL || 'http:\u002F\u002Flocalhost:3000',\n    screenshot: 'only-on-failure',\n    video: 'retain-on-failure',\n    trace: 'retain-on-failure',\n  },\n\n  projects: [\n    {\n      name: 'chromium',\n      use: { ...devices['Desktop Chrome'] },\n    },\n    {\n      name: 'firefox',\n      use: { ...devices['Desktop Firefox'] },\n    },\n  ],\n});\n```\n\n### Custom Step Annotations in Playwright\n\n```typescript\n\u002F\u002F tests\u002Fe2e\u002Fcheckout.spec.ts\nimport { test, expect } from '@playwright\u002Ftest';\nimport { allure } from 'allure-playwright';\n\ntest.describe('Checkout Flow', () => {\n  test.beforeEach(async ({ page }) => {\n    await allure.epic('E-Commerce');\n    await allure.feature('Checkout');\n    await allure.owner('team-payments');\n  });\n\n  test('should complete purchase with credit card', async ({ page }) => {\n    await allure.severity('critical');\n    await allure.story('Credit Card Payment');\n    await allure.tag('smoke');\n    await allure.tag('payments');\n\n    \u002F\u002F Add link to test case management system\n    await allure.link('https:\u002F\u002Fjira.example.com\u002Fbrowse\u002FQA-100', 'Test Case', 'tms');\n    await allure.issue('BUG-456', 'https:\u002F\u002Fjira.example.com\u002Fbrowse\u002FBUG-456');\n\n    \u002F\u002F Step 1: Add item to cart\n    await allure.step('Add product to cart', async () => {\n      await page.goto('\u002Fproducts\u002F1');\n      await page.click('[data-testid=\"add-to-cart\"]');\n      await expect(page.locator('[data-testid=\"cart-count\"]')).toHaveText('1');\n\n      \u002F\u002F Attach product page screenshot\n      const screenshot = await page.screenshot();\n      await allure.attachment('Product Page', screenshot, 'image\u002Fpng');\n    });\n\n    \u002F\u002F Step 2: Navigate to checkout\n    await allure.step('Navigate to checkout page', async () => {\n      await page.click('[data-testid=\"cart-icon\"]');\n      await page.click('[data-testid=\"proceed-to-checkout\"]');\n      await expect(page).toHaveURL('\u002Fcheckout');\n    });\n\n    \u002F\u002F Step 3: Fill payment details\n    await allure.step('Enter payment information', async () => {\n      await allure.step('Fill card number', async () => {\n        await page.fill('[data-testid=\"card-number\"]', '4242424242424242');\n      });\n      await allure.step('Fill expiry date', async () => {\n        await page.fill('[data-testid=\"card-expiry\"]', '12\u002F28');\n      });\n      await allure.step('Fill CVV', async () => {\n        await page.fill('[data-testid=\"card-cvv\"]', '123');\n      });\n    });\n\n    \u002F\u002F Step 4: Submit order\n    await allure.step('Place order', async () => {\n      await page.click('[data-testid=\"place-order\"]');\n      await expect(page.locator('[data-testid=\"order-confirmation\"]')).toBeVisible({\n        timeout: 15000,\n      });\n\n      \u002F\u002F Capture confirmation details\n      const confirmationText = await page\n        .locator('[data-testid=\"order-confirmation\"]')\n        .textContent();\n      await allure.attachment('Order Confirmation', confirmationText || '', 'text\u002Fplain');\n    });\n\n    \u002F\u002F Step 5: Verify order details\n    await allure.step('Verify order details', async () => {\n      const orderId = await page.locator('[data-testid=\"order-id\"]').textContent();\n      expect(orderId).toBeTruthy();\n\n      \u002F\u002F Attach full page screenshot\n      const fullPage = await page.screenshot({ fullPage: true });\n      await allure.attachment('Confirmation Page', fullPage, 'image\u002Fpng');\n\n      \u002F\u002F Attach API response for debugging\n      const orderDetails = await page.evaluate(async (id) => {\n        const res = await fetch(`\u002Fapi\u002Forders\u002F${id}`);\n        return res.json();\n      }, orderId);\n      await allure.attachment(\n        'Order API Response',\n        JSON.stringify(orderDetails, null, 2),\n        'application\u002Fjson'\n      );\n    });\n  });\n\n  test('should show validation errors for invalid card', async ({ page }) => {\n    await allure.severity('normal');\n    await allure.story('Payment Validation');\n\n    await page.goto('\u002Fcheckout');\n\n    await allure.step('Submit empty payment form', async () => {\n      await page.click('[data-testid=\"place-order\"]');\n    });\n\n    await allure.step('Verify validation errors displayed', async () => {\n      await expect(page.locator('[data-testid=\"card-error\"]')).toHaveText(\n        'Card number is required'\n      );\n      await expect(page.locator('[data-testid=\"expiry-error\"]')).toHaveText(\n        'Expiry date is required'\n      );\n    });\n  });\n});\n```\n\n### Custom Allure Fixture for Reusable Annotations\n\n```typescript\n\u002F\u002F tests\u002Ffixtures\u002Fallure-fixture.ts\nimport { test as base } from '@playwright\u002Ftest';\nimport { allure } from 'allure-playwright';\n\ninterface AllureOptions {\n  epic: string;\n  feature: string;\n  severity: 'blocker' | 'critical' | 'normal' | 'minor' | 'trivial';\n}\n\nexport const test = base.extend\u003C{ allureConfig: AllureOptions }>({\n  allureConfig: [\n    async ({}, use, testInfo) => {\n      \u002F\u002F Auto-derive categorization from test file path\n      const filePath = testInfo.file;\n      let epic = 'General';\n      let feature = 'Uncategorized';\n\n      if (filePath.includes('checkout')) {\n        epic = 'E-Commerce';\n        feature = 'Checkout';\n      } else if (filePath.includes('search')) {\n        epic = 'Discovery';\n        feature = 'Search';\n      } else if (filePath.includes('user')) {\n        epic = 'Account';\n        feature = 'User Management';\n      }\n\n      await allure.epic(epic);\n      await allure.feature(feature);\n\n      \u002F\u002F Attach test metadata\n      await allure.parameter('Browser', testInfo.project.name);\n      await allure.parameter('Retry Attempt', String(testInfo.retry));\n\n      const options: AllureOptions = {\n        epic,\n        feature,\n        severity: 'normal',\n      };\n\n      await use(options);\n\n      \u002F\u002F After test: attach trace on failure\n      if (testInfo.status !== 'passed') {\n        const tracePath = testInfo.outputPath('trace.zip');\n        try {\n          const traceBuffer = require('fs').readFileSync(tracePath);\n          await allure.attachment('Playwright Trace', traceBuffer, 'application\u002Fzip');\n        } catch {\n          \u002F\u002F Trace not available\n        }\n      }\n    },\n    { auto: true },\n  ],\n});\n\nexport { expect } from '@playwright\u002Ftest';\n```\n\n## Allure Reporter Setup for Jest\n\n```bash\nnpm install --save-dev allure-jest allure-js-commons allure-commandline\n```\n\n```typescript\n\u002F\u002F config\u002Fjest.config.ts\nimport type { Config } from 'jest';\n\nconst config: Config = {\n  preset: 'ts-jest',\n  testEnvironment: 'allure-jest\u002Fnode',\n  testEnvironmentOptions: {\n    resultsDir: 'allure-results',\n    environmentInfo: {\n      'Node Version': process.version,\n      OS: process.platform,\n      'Test Environment': process.env.TEST_ENV || 'local',\n    },\n  },\n  reporters: ['default'],\n};\n\nexport default config;\n```\n\n### Jest Test with Allure Annotations\n\n```typescript\n\u002F\u002F tests\u002Fintegration\u002Fapi-orders.test.ts\nimport { allure } from 'allure-js-commons';\n\ndescribe('Orders API', () => {\n  beforeAll(async () => {\n    await allure.epic('API');\n    await allure.feature('Orders');\n  });\n\n  it('should create a new order', async () => {\n    await allure.severity('critical');\n    await allure.story('Order Creation');\n    await allure.owner('team-orders');\n    await allure.tag('api');\n    await allure.tag('smoke');\n\n    await allure.step('Prepare order payload', async () => {\n      const payload = {\n        customerId: 42,\n        items: [{ productId: 'prod-001', quantity: 2 }],\n        shippingAddress: {\n          street: '123 Main St',\n          city: 'Portland',\n          state: 'OR',\n          zip: '97201',\n        },\n      };\n      await allure.attachment(\n        'Request Payload',\n        JSON.stringify(payload, null, 2),\n        'application\u002Fjson'\n      );\n\n      await allure.step('Send POST request', async () => {\n        const response = await fetch('http:\u002F\u002Flocalhost:3000\u002Fapi\u002Forders', {\n          method: 'POST',\n          headers: { 'Content-Type': 'application\u002Fjson' },\n          body: JSON.stringify(payload),\n        });\n\n        expect(response.status).toBe(201);\n\n        const body = await response.json();\n        await allure.attachment(\n          'Response Body',\n          JSON.stringify(body, null, 2),\n          'application\u002Fjson'\n        );\n\n        await allure.step('Verify order ID assigned', async () => {\n          expect(body.id).toBeDefined();\n          expect(typeof body.id).toBe('string');\n        });\n\n        await allure.step('Verify order total calculated', async () => {\n          expect(body.total).toBeGreaterThan(0);\n        });\n      });\n    });\n  });\n\n  it('should return 400 for invalid order', async () => {\n    await allure.severity('normal');\n    await allure.story('Order Validation');\n\n    await allure.step('Send order without required fields', async () => {\n      const response = await fetch('http:\u002F\u002Flocalhost:3000\u002Fapi\u002Forders', {\n        method: 'POST',\n        headers: { 'Content-Type': 'application\u002Fjson' },\n        body: JSON.stringify({}),\n      });\n\n      expect(response.status).toBe(400);\n\n      const body = await response.json();\n      await allure.attachment(\n        'Error Response',\n        JSON.stringify(body, null, 2),\n        'application\u002Fjson'\n      );\n\n      await allure.step('Verify error details', async () => {\n        expect(body.errors).toBeDefined();\n        expect(body.errors.length).toBeGreaterThan(0);\n      });\n    });\n  });\n});\n```\n\n## Allure Reporter Setup for pytest\n\n```bash\npip install allure-pytest\n```\n\n```ini\n# pytest.ini\n[pytest]\naddopts = --alluredir=allure-results --clean-alluredir\n```\n\n### Python Test with Allure Annotations\n\n```python\n# tests\u002Ftest_user_api.py\nimport allure\nimport pytest\nimport requests\nimport json\n\nBASE_URL = \"http:\u002F\u002Flocalhost:8000\"\n\n\n@allure.epic(\"API\")\n@allure.feature(\"User Management\")\nclass TestUserAPI:\n\n    @allure.severity(allure.severity_level.CRITICAL)\n    @allure.story(\"User Registration\")\n    @allure.title(\"Register a new user with valid data\")\n    @allure.tag(\"api\", \"smoke\", \"registration\")\n    @allure.link(\"https:\u002F\u002Fjira.example.com\u002Fbrowse\u002FQA-200\", name=\"Test Case\")\n    def test_register_user(self):\n        payload = {\n            \"name\": \"Jane Doe\",\n            \"email\": \"jane@example.com\",\n            \"password\": \"SecureP@ss123\",\n        }\n\n        with allure.step(\"Prepare registration payload\"):\n            allure.attach(\n                json.dumps(payload, indent=2),\n                name=\"Request Payload\",\n                attachment_type=allure.attachment_type.JSON,\n            )\n\n        with allure.step(\"Send POST \u002Fapi\u002Fusers\u002Fregister\"):\n            response = requests.post(\n                f\"{BASE_URL}\u002Fapi\u002Fusers\u002Fregister\", json=payload\n            )\n\n            allure.attach(\n                json.dumps(response.json(), indent=2),\n                name=\"Response Body\",\n                attachment_type=allure.attachment_type.JSON,\n            )\n\n            allure.attach(\n                str(response.status_code),\n                name=\"Status Code\",\n                attachment_type=allure.attachment_type.TEXT,\n            )\n\n        with allure.step(\"Verify registration succeeded\"):\n            assert response.status_code == 201\n            body = response.json()\n            assert \"id\" in body\n            assert body[\"email\"] == \"jane@example.com\"\n\n        with allure.step(\"Verify user can authenticate\"):\n            login_response = requests.post(\n                f\"{BASE_URL}\u002Fapi\u002Fauth\u002Flogin\",\n                json={\n                    \"email\": \"jane@example.com\",\n                    \"password\": \"SecureP@ss123\",\n                },\n            )\n            assert login_response.status_code == 200\n            assert \"token\" in login_response.json()\n\n    @allure.severity(allure.severity_level.NORMAL)\n    @allure.story(\"User Registration\")\n    @allure.title(\"Reject registration with duplicate email\")\n    def test_register_duplicate_email(self):\n        payload = {\n            \"name\": \"Duplicate\",\n            \"email\": \"existing@example.com\",\n            \"password\": \"Pass123!\",\n        }\n\n        with allure.step(\"Register user with existing email\"):\n            response = requests.post(\n                f\"{BASE_URL}\u002Fapi\u002Fusers\u002Fregister\", json=payload\n            )\n\n        with allure.step(\"Verify conflict error returned\"):\n            assert response.status_code == 409\n            assert \"already exists\" in response.json()[\"message\"]\n\n    @allure.severity(allure.severity_level.CRITICAL)\n    @allure.story(\"User Profile\")\n    @allure.title(\"Retrieve user profile with valid token\")\n    def test_get_user_profile(self, auth_token):\n        with allure.step(\"Send GET \u002Fapi\u002Fusers\u002Fme with auth token\"):\n            response = requests.get(\n                f\"{BASE_URL}\u002Fapi\u002Fusers\u002Fme\",\n                headers={\"Authorization\": f\"Bearer {auth_token}\"},\n            )\n\n            allure.attach(\n                json.dumps(response.json(), indent=2),\n                name=\"Profile Response\",\n                attachment_type=allure.attachment_type.JSON,\n            )\n\n        with allure.step(\"Verify profile data\"):\n            assert response.status_code == 200\n            profile = response.json()\n            assert \"id\" in profile\n            assert \"name\" in profile\n            assert \"email\" in profile\n            assert \"password\" not in profile  # Verify password not exposed\n\n\n@pytest.fixture\ndef auth_token():\n    \"\"\"Fixture that provides an authenticated user token.\"\"\"\n    with allure.step(\"Authenticate test user\"):\n        response = requests.post(\n            f\"{BASE_URL}\u002Fapi\u002Fauth\u002Flogin\",\n            json={\n                \"email\": \"test@example.com\",\n                \"password\": \"TestPass123!\",\n            },\n        )\n        return response.json()[\"token\"]\n```\n\n## Environment Info Configuration\n\n```properties\n# config\u002Fallure-environment.properties\n# This file is copied to allure-results\u002F before report generation\nBrowser=Chromium 120\nOS=Ubuntu 22.04\nNode.Version=20.10.0\nTest.Environment=staging\nAPI.Base.URL=https:\u002F\u002Fstaging-api.example.com\nApp.Version=2.5.0\nBuild.Number=${BUILD_NUMBER}\nGit.Commit=${GIT_COMMIT}\nGit.Branch=${GIT_BRANCH}\nDeployment.Region=us-east-1\nDatabase=PostgreSQL 16\n```\n\n### Dynamic Environment Properties Script\n\n```typescript\n\u002F\u002F scripts\u002Fgenerate-environment.ts\nimport * as fs from 'fs';\nimport { execSync } from 'child_process';\n\nconst gitCommit = execSync('git rev-parse --short HEAD', { encoding: 'utf-8' }).trim();\nconst gitBranch = execSync('git rev-parse --abbrev-ref HEAD', { encoding: 'utf-8' }).trim();\n\nconst properties = [\n  `Browser=${process.env.BROWSER || 'Chromium'}`,\n  `OS=${process.platform} ${process.arch}`,\n  `Node.Version=${process.version}`,\n  `Test.Environment=${process.env.TEST_ENV || 'local'}`,\n  `Base.URL=${process.env.BASE_URL || 'http:\u002F\u002Flocalhost:3000'}`,\n  `Git.Commit=${gitCommit}`,\n  `Git.Branch=${gitBranch}`,\n  `Build.Number=${process.env.BUILD_NUMBER || 'local'}`,\n  `Timestamp=${new Date().toISOString()}`,\n].join('\\n');\n\nfs.writeFileSync('allure-results\u002Fenvironment.properties', properties);\nconsole.log('Environment properties written to allure-results\u002Fenvironment.properties');\n```\n\n## Categories and Severity Labeling\n\n### Categories Configuration\n\n```json\n\u002F\u002F config\u002Fallure-categories.json\n[\n  {\n    \"name\": \"Product Defects\",\n    \"description\": \"Failures caused by actual application bugs\",\n    \"matchedStatuses\": [\"failed\"],\n    \"messageRegex\": \".*Expected .* (to be|to have|to contain|to equal).*\"\n  },\n  {\n    \"name\": \"Test Infrastructure Issues\",\n    \"description\": \"Failures caused by test environment problems\",\n    \"matchedStatuses\": [\"broken\"],\n    \"messageRegex\": \".*(timeout|ECONNREFUSED|ENOTFOUND|ETIMEDOUT|net::ERR|Navigation).*\"\n  },\n  {\n    \"name\": \"Element Not Found\",\n    \"description\": \"Failures where expected UI elements are missing\",\n    \"matchedStatuses\": [\"failed\"],\n    \"messageRegex\": \".*(locator|selector|element).*(not found|not visible|not attached).*\"\n  },\n  {\n    \"name\": \"API Errors\",\n    \"description\": \"Failures in API response validation\",\n    \"matchedStatuses\": [\"failed\"],\n    \"messageRegex\": \".*(status code|response|4\\\\d{2}|5\\\\d{2}).*\"\n  },\n  {\n    \"name\": \"Data Setup Failures\",\n    \"description\": \"Failures in test fixture or data preparation\",\n    \"matchedStatuses\": [\"broken\"],\n    \"traceRegex\": \".*(beforeAll|beforeEach|fixture|setup).*\"\n  },\n  {\n    \"name\": \"Outdated Tests\",\n    \"description\": \"Tests that need updating due to application changes\",\n    \"matchedStatuses\": [\"failed\"],\n    \"messageRegex\": \".*(deprecated|removed|changed|no longer).*\"\n  }\n]\n```\n\n### Copying Categories to Results\n\n```bash\n#!\u002Fbin\u002Fbash\n# scripts\u002Fgenerate-report.sh\n\n# Copy categories to allure-results (must be present before generation)\ncp config\u002Fallure-categories.json allure-results\u002Fcategories.json\n\n# Generate environment properties\nnpx ts-node scripts\u002Fgenerate-environment.ts\n\n# Copy history from previous report (for trends)\nif [ -d \"allure-report\u002Fhistory\" ]; then\n  cp -r allure-report\u002Fhistory allure-results\u002Fhistory\nfi\n\n# Generate the report\nnpx allure generate allure-results --clean -o allure-report\n\necho \"Report generated at allure-report\u002Findex.html\"\n```\n\n## Historical Trend Tracking\n\n### Preserving History Across Builds\n\n```bash\n#!\u002Fbin\u002Fbash\n# scripts\u002Fsetup-history.sh\n# Run before each test execution to preserve historical data\n\nHISTORY_DIR=\"allure-results\u002Fhistory\"\nREPORT_HISTORY=\"allure-report\u002Fhistory\"\n\n# If a previous report exists, copy its history to the new results directory\nif [ -d \"$REPORT_HISTORY\" ]; then\n  mkdir -p \"$HISTORY_DIR\"\n  cp -r \"$REPORT_HISTORY\u002F\"* \"$HISTORY_DIR\u002F\"\n  echo \"History preserved from previous report\"\nelse\n  echo \"No previous history found (first run)\"\nfi\n```\n\n### CI History Preservation with Artifacts\n\n```yaml\n# In a GitHub Actions workflow, history is preserved via artifacts\n- name: Download previous report history\n  uses: actions\u002Fdownload-artifact@v4\n  with:\n    name: allure-report-history\n    path: allure-results\u002Fhistory\n  continue-on-error: true  # First run will not have history\n\n# After report generation\n- name: Save report history\n  uses: actions\u002Fupload-artifact@v4\n  with:\n    name: allure-report-history\n    path: allure-report\u002Fhistory\n    retention-days: 30\n```\n\n## CI Integration\n\n### GitHub Actions Complete Workflow\n\n```yaml\n# .github\u002Fworkflows\u002Ftest-and-report.yml\nname: Test and Report\non:\n  push:\n    branches: [main, develop]\n  pull_request:\n    branches: [main]\n\npermissions:\n  contents: read\n  pages: write\n  id-token: write\n\njobs:\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: 20\n      - run: npm ci\n      - run: npx playwright install --with-deps\n\n      # Download previous Allure history for trends\n      - name: Restore Allure history\n        uses: actions\u002Fdownload-artifact@v4\n        with:\n          name: allure-history\n          path: allure-results\u002Fhistory\n        continue-on-error: true\n\n      # Run tests\n      - name: Run Playwright tests\n        run: npx playwright test\n        continue-on-error: true\n        env:\n          BASE_URL: ${{ secrets.STAGING_URL }}\n          TEST_ENV: ci\n\n      # Generate environment properties\n      - name: Generate environment info\n        run: |\n          cat > allure-results\u002Fenvironment.properties \u003C\u003C EOF\n          Browser=Chromium\n          OS=Ubuntu (CI)\n          Node.Version=$(node --version)\n          Test.Environment=CI\n          Git.Commit=${{ github.sha }}\n          Git.Branch=${{ github.ref_name }}\n          Build.Number=${{ github.run_number }}\n          PR.Number=${{ github.event.pull_request.number || 'N\u002FA' }}\n          EOF\n\n      # Copy categories\n      - name: Setup Allure categories\n        run: cp config\u002Fallure-categories.json allure-results\u002Fcategories.json\n\n      # Generate report\n      - name: Generate Allure Report\n        run: |\n          npm install -g allure-commandline\n          allure generate allure-results --clean -o allure-report\n\n      # Save history for next run\n      - name: Save Allure history\n        uses: actions\u002Fupload-artifact@v4\n        if: always()\n        with:\n          name: allure-history\n          path: allure-report\u002Fhistory\n          retention-days: 60\n\n      # Upload full report\n      - name: Upload Allure Report\n        uses: actions\u002Fupload-artifact@v4\n        if: always()\n        with:\n          name: allure-report\n          path: allure-report\u002F\n          retention-days: 30\n\n  # Deploy report to GitHub Pages\n  deploy-report:\n    needs: test\n    if: github.ref == 'refs\u002Fheads\u002Fmain'\n    runs-on: ubuntu-latest\n    environment:\n      name: github-pages\n      url: ${{ steps.deployment.outputs.page_url }}\n    steps:\n      - uses: actions\u002Fdownload-artifact@v4\n        with:\n          name: allure-report\n          path: allure-report\n\n      - uses: actions\u002Fconfigure-pages@v4\n      - uses: actions\u002Fupload-pages-artifact@v3\n        with:\n          path: allure-report\n      - id: deployment\n        uses: actions\u002Fdeploy-pages@v4\n```\n\n### Jenkins Pipeline Integration\n\n```groovy\n\u002F\u002F Jenkinsfile\npipeline {\n    agent any\n\n    stages {\n        stage('Test') {\n            steps {\n                sh 'npm ci'\n                sh 'npx playwright install --with-deps'\n                sh 'npx playwright test || true'\n            }\n            post {\n                always {\n                    \u002F\u002F Copy environment properties\n                    sh '''\n                        echo \"Browser=Chromium\" > allure-results\u002Fenvironment.properties\n                        echo \"Build.Number=${BUILD_NUMBER}\" >> allure-results\u002Fenvironment.properties\n                        echo \"Git.Commit=${GIT_COMMIT}\" >> allure-results\u002Fenvironment.properties\n                        echo \"Node.Version=$(node --version)\" >> allure-results\u002Fenvironment.properties\n                    '''\n\n                    \u002F\u002F Jenkins Allure plugin generates report and preserves history\n                    allure([\n                        includeProperties: true,\n                        jdk: '',\n                        properties: [],\n                        reportBuildPolicy: 'ALWAYS',\n                        results: [[path: 'allure-results']]\n                    ])\n                }\n            }\n        }\n    }\n}\n```\n\n## Allure TestOps Overview\n\nAllure TestOps is the commercial companion to Allure Report, providing centralized test management, real-time dashboards, and analytics across multiple projects.\n\n```typescript\n\u002F\u002F Integration with Allure TestOps (if available)\n\u002F\u002F config\u002Fallure-testops.config.ts\nexport const testOpsConfig = {\n  \u002F\u002F TestOps server configuration\n  endpoint: process.env.ALLURE_TESTOPS_URL || 'https:\u002F\u002Fallure.example.com',\n  token: process.env.ALLURE_TESTOPS_TOKEN,\n  projectId: parseInt(process.env.ALLURE_PROJECT_ID || '1'),\n\n  \u002F\u002F Launch configuration\n  launchName: `${process.env.GIT_BRANCH || 'local'} - ${new Date().toISOString()}`,\n  launchTags: [process.env.TEST_ENV || 'local', process.env.GIT_BRANCH || 'unknown'],\n};\n\n\u002F\u002F Upload results to TestOps after test execution:\n\u002F\u002F npx allurectl upload allure-results \\\n\u002F\u002F   --endpoint $ALLURE_TESTOPS_URL \\\n\u002F\u002F   --token $ALLURE_TESTOPS_TOKEN \\\n\u002F\u002F   --project-id 1\n```\n\n## Custom Widgets\n\nAllure reports support custom widgets that display aggregated data on the report overview page.\n\n```json\n\u002F\u002F allure-results\u002Fwidgets\u002Fsummary.json (custom widget data)\n{\n  \"reportName\": \"E-Commerce Test Suite\",\n  \"testRuns\": [\n    {\n      \"name\": \"Smoke Tests\",\n      \"total\": 25,\n      \"passed\": 24,\n      \"failed\": 1,\n      \"broken\": 0,\n      \"skipped\": 0\n    },\n    {\n      \"name\": \"Regression Tests\",\n      \"total\": 150,\n      \"passed\": 142,\n      \"failed\": 5,\n      \"broken\": 2,\n      \"skipped\": 1\n    }\n  ],\n  \"environment\": \"Staging\",\n  \"duration\": \"12m 34s\"\n}\n```\n\n## Report Hosting Strategies\n\n### Strategy 1: GitHub Pages (Free, Public)\n\n```bash\n# Deploy to GitHub Pages using gh-pages package\nnpm install -g gh-pages\n\n# Generate and deploy\nallure generate allure-results -o allure-report\ngh-pages -d allure-report -m \"Allure Report $(date +%Y-%m-%d)\"\n```\n\n### Strategy 2: S3 Static Hosting (Private, Scalable)\n\n```typescript\n\u002F\u002F scripts\u002Fpublish-report.ts\nimport { S3Client, PutObjectCommand } from '@aws-sdk\u002Fclient-s3';\nimport * as fs from 'fs';\nimport * as path from 'path';\nimport * as mime from 'mime-types';\n\nconst s3 = new S3Client({ region: process.env.AWS_REGION || 'us-east-1' });\nconst BUCKET = process.env.REPORT_BUCKET || 'test-reports';\nconst PREFIX = `allure\u002F${process.env.GIT_BRANCH || 'main'}\u002F${Date.now()}`;\n\nasync function uploadDirectory(dirPath: string, s3Prefix: string): Promise\u003Cvoid> {\n  const entries = fs.readdirSync(dirPath, { withFileTypes: true });\n\n  for (const entry of entries) {\n    const fullPath = path.join(dirPath, entry.name);\n    const s3Key = `${s3Prefix}\u002F${entry.name}`;\n\n    if (entry.isDirectory()) {\n      await uploadDirectory(fullPath, s3Key);\n    } else {\n      const contentType = mime.lookup(entry.name) || 'application\u002Foctet-stream';\n      await s3.send(\n        new PutObjectCommand({\n          Bucket: BUCKET,\n          Key: s3Key,\n          Body: fs.readFileSync(fullPath),\n          ContentType: contentType,\n        })\n      );\n    }\n  }\n}\n\nasync function main() {\n  console.log(`Uploading report to s3:\u002F\u002F${BUCKET}\u002F${PREFIX}\u002F`);\n  await uploadDirectory('allure-report', PREFIX);\n  console.log(`Report available at: https:\u002F\u002F${BUCKET}.s3.amazonaws.com\u002F${PREFIX}\u002Findex.html`);\n}\n\nmain().catch(console.error);\n```\n\n### Strategy 3: Docker Container (Self-Hosted)\n\n```yaml\n# docker-compose.yml for self-hosted Allure report server\nversion: '3.8'\nservices:\n  allure-server:\n    image: frankescobar\u002Fallure-docker-service:latest\n    ports:\n      - \"5050:5050\"\n    environment:\n      CHECK_RESULTS_EVERY_SECONDS: 5\n      KEEP_HISTORY: 25\n    volumes:\n      - .\u002Fallure-results:\u002Fapp\u002Fallure-results\n      - .\u002Fallure-reports:\u002Fapp\u002Fdefault-reports\n```\n\n## Configuration\n\n### Package.json Scripts\n\n```json\n{\n  \"scripts\": {\n    \"test\": \"playwright test\",\n    \"test:report\": \"playwright test && npm run allure:generate\",\n    \"allure:generate\": \"bash scripts\u002Fgenerate-report.sh\",\n    \"allure:open\": \"allure open allure-report\",\n    \"allure:serve\": \"allure serve allure-results\",\n    \"allure:clean\": \"rm -rf allure-results allure-report\",\n    \"allure:history\": \"bash scripts\u002Fsetup-history.sh\",\n    \"allure:publish\": \"ts-node scripts\u002Fpublish-report.ts\"\n  }\n}\n```\n\n### Allure Commandline Installation\n\n```bash\n# Via npm (recommended for JavaScript projects)\nnpm install -g allure-commandline\n\n# Via Homebrew (macOS)\nbrew install allure\n\n# Via scoop (Windows)\nscoop install allure\n\n# Verify installation\nallure --version\n```\n\n## Best Practices\n\n1. **Annotate every test with severity.** Use Allure severity levels (blocker, critical, normal, minor, trivial) consistently. This enables filtering the report by severity during triage sessions.\n\n2. **Organize tests with epic\u002Ffeature\u002Fstory hierarchy.** Map tests to the product feature hierarchy so the Allure Behaviors view reflects the actual product structure. This helps stakeholders navigate reports by business functionality.\n\n3. **Attach screenshots and videos on failure only.** Recording screenshots and videos for all tests inflates report size without benefit. Configure `screenshot: 'only-on-failure'` and `video: 'retain-on-failure'`.\n\n4. **Use meaningful step descriptions.** Steps should describe intent (\"Add product to cart\"), not implementation (\"Click button with data-testid add-to-cart\"). Report readers may not have code access.\n\n5. **Configure categories to match your failure taxonomy.** Customize `categories.json` to classify failures into actionable groups. Default categories are too generic for effective triage.\n\n6. **Preserve history across CI builds.** Without history, trend charts are empty and test retries lack context. Use CI artifacts or external storage to maintain history for at least 20-30 builds.\n\n7. **Generate environment properties dynamically.** Hardcoded environment files become stale. Generate them from CI environment variables and git metadata at report generation time.\n\n8. **Attach API request\u002Fresponse pairs for API tests.** When API tests fail, the request payload and response body attached to the report step eliminate the need to reproduce the failure locally.\n\n9. **Include links to test case management and issue tracking.** Use `allure.link()` and `allure.issue()` to connect report entries to external systems. This creates bidirectional traceability between reports and project management tools.\n\n10. **Host reports on a persistent URL.** Ephemeral reports in CI artifacts are hard to share. Deploy to GitHub Pages, S3, or a dedicated report server where stakeholders can always find the latest report.\n\n11. **Set up Slack or email notifications for report availability.** After CI generates a report, notify the team with a direct link. Reports that nobody opens provide no value.\n\n12. **Review report trends weekly.** Schedule a brief weekly review of the Allure trend view to catch increasing failure rates, growing test suite duration, or emerging flaky test patterns before they become systemic problems.\n\n## Anti-Patterns to Avoid\n\n1. **Generating reports without categories configuration.** Without categories, all failures appear in a single undifferentiated list. Categories enable meaningful failure classification that accelerates triage.\n\n2. **Over-attaching large files to every test.** Attaching multi-megabyte videos or full HAR files to every test (including passing tests) creates enormous reports that are slow to generate, upload, and browse.\n\n3. **Using generic step names.** Steps labeled \"Step 1\", \"Step 2\", or \"Verification\" provide no value. Each step name should clearly describe what is happening and why.\n\n4. **Ignoring the Allure report trend view.** Running Allure without preserving history across builds discards the most valuable feature: the ability to see trends and identify degradation over time.\n\n5. **Skipping environment configuration.** A report without environment details cannot be interpreted correctly. The same test result means different things on Chrome vs Firefox, or staging vs production.\n\n6. **Treating report generation as an afterthought.** Report configuration should be established early in the project, not bolted on when stakeholders demand visibility. Retrofit is always harder than upfront setup.\n\n7. **Not cleaning allure-results between runs.** If old results are not cleared before new test runs, the report will contain stale data from previous executions, creating confusion about current test status.\n\n## Debugging Tips\n\n1. **Check allure-results directory for raw data.** If the report looks wrong, inspect the JSON files in `allure-results\u002F`. Each test produces a `-result.json` file containing all metadata, steps, and attachment references.\n\n2. **Verify categories.json is in allure-results before generation.** The categories file must be present in the results directory when the report is generated. Placing it only in the config directory without copying produces a report with no category classifications.\n\n3. **Validate environment.properties format.** The file must use `key=value` format with no quotes around values. Malformed properties are silently ignored, resulting in missing environment information in the report.\n\n4. **Check attachment file references.** If attachments show as broken links in the report, verify that the attachment files exist in `allure-results\u002F` and that the file names in the result JSON match the actual files on disk.\n\n5. **Use allure serve for quick local preview.** The `allure serve allure-results` command generates a temporary report and opens it in a browser without creating the persistent `allure-report` directory. This is the fastest way to preview results during development.\n\n6. **Verify allure-commandline version compatibility.** Allure Report and the framework reporters must use compatible versions. Check the compatibility matrix in the Allure documentation if reports appear empty or malformatted.\n\n7. **Inspect the history directory structure.** Trend charts require a specific directory structure in `allure-results\u002Fhistory\u002F`. If trends are not appearing, verify that `history.json` and `history-trend.json` from the previous report were correctly copied to the results directory.\n\n8. **Check for conflicting reporters.** Running multiple reporters that write to the same output directory can cause data corruption. Ensure each reporter writes to a distinct directory or uses the framework's built-in multi-reporter support.\n\n9. **Review CI artifact retention policies.** If history suddenly stops working in CI, check whether artifact retention policies expired. History artifacts need to persist across builds, so set retention days appropriately (30-60 days minimum).\n\n10. **Test report generation locally before CI.** Always verify that `allure generate allure-results -o allure-report` works locally with representative test data before debugging CI-specific report issues.\n",{"name":5,"tags":24,"agents":32,"author":45,"domains":46,"license":15,"version":48,"languages":49,"frameworks":54,"description":7,"testingTypes":58},[25,26,27,28,29,30,31],"allure","test-reporting","test-results","ci-reporting","test-history","test-dashboard","reporting-framework",[33,34,35,36,37,38,39,40,41,42,43,44],"claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp","Pramod",[47],"devops","1.0.0",[50,51,52,53],"typescript","javascript","python","java",[55,56,57],"playwright","jest","pytest",[59,60],"e2e","integration","main","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Fqa\u002Fallure-report-generator","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m","https:\u002F\u002Fid-preview--d5bef06d-6c9e-4563-a3d4-a855b9d61610.lovable.app\u002F","Eu sou Antonio B. B. Ndombe \r\nEu sou um Pesquisador e desenvolvedor de sistema autonomia cognitivos, fundador de sistemas ODCs ( organismos digital conscientes)","2026-11-04 06:53:39",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Allure Report Generator\"",{"tool":75,"command":76},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Allure Report Generator\"",{"tool":78,"command":79},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill \"Allure Report Generator\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Fqa\u002Fallure-report-generator\u002FSKILL.md",true,[],[84,92,99,106,113,120],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7DASC6FSCJP49JZBSK0NY1Z","nemoclaw-user-reference","Describes the NemoClaw integration layer and blueprint architecture and how they orchestrate compatible agent sandboxes. Use when looking up architecture, agent integration, plugin structure, or blueprint design. Trigger keywords - nemoclaw architecture, nemoclaw agent architecture, nemoclaw plugin blueprint structure, nemoclaw vs openshell, which cli, nemoclaw cli, openshell cli, sandbox commands, nemoclaw cli commands, nemoclaw command reference, nemoclaw network policy, sandbox egress control operator approval, nemoclaw troubleshooting, nemoclaw debug sandbox issues.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-reference\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7DAS5S79VK33XFGVAM2TFWF","nemoclaw-user-overview","Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Trigger keywords - nemoclaw ecosystem, openclaw openshell, nemoclaw vs openshell, sandboxed openclaw, how nemoclaw works, nemoclaw sandbox lifecycle blueprint, nemoclaw overview, openclaw always-on assistants, nvidia openshell, nvidia nemotron, nemoclaw release notes, nemoclaw changelog.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-overview\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7DAS0PQEMET5MNGZ1ABSZVS","nemoclaw-user-monitor-sandbox","Inspects sandbox health, traces agent behavior, and diagnoses problems. Use when monitoring a running sandbox, debugging agent issues, or checking sandbox logs. Trigger keywords - monitor nemoclaw sandbox, debug nemoclaw agent issues.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-monitor-sandbox\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7DARQYGF7E9A69VH6S3CGN9","nemoclaw-user-manage-sandboxes","Explains operational tasks after the quickstart: listing sandboxes, status and health checks, logs, diagnostics, port forwards, multiple sandboxes, credential reset, rebuilds, network presets, upgrades, and uninstall. Trigger keywords - manage nemoclaw sandboxes, nemoclaw status, nemoclaw list, nemoclaw dashboard port, nemoclaw rebuild, nemoclaw upgrade sandboxes, nemoclaw uninstall, sandbox mutability, sandbox runtime configuration, sandbox rebuild, nemoclaw backup, nemoclaw restore, workspace backup, openshell sandbox download upload, nemoclaw messaging channels, nemoclaw telegram, nemoclaw discord, nemoclaw slack, nemoclaw wechat, nemoclaw whatsapp, openshell channel messaging, nemoclaw workspace files, soul.md, user.md, identity.md, agents.md, sandbox persistence.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-manage-sandboxes\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7DARH8BRTG51TRCAB7YWDJ4","nemoclaw-user-manage-policy","Adds, removes, or modifies allowed endpoints in the sandbox policy. Use when customizing network policy, changing egress rules, or configuring sandbox endpoint access. Trigger keywords - customize nemoclaw network policy, sandbox egress policy configuration, nemoclaw integration policy examples, post-install policy setup, openshell approval workflow, policy preset, nemoclaw approve network requests, sandbox egress approval tui.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-manage-policy\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7DARAT62M2VR37590VCZ5NS","nemoclaw-user-get-started","Installs NemoClaw, launches a sandbox, and runs the first agent prompt. Use when onboarding, installing, or launching a NemoClaw sandbox for the first time. Trigger keywords - nemoclaw quickstart, install nemoclaw openclaw sandbox, nemohermes quickstart, hermes agent nemoclaw, run hermes openshell sandbox, nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-get-started\u002FSKILL.md",[],[]]