Conversation
Co-authored-by: dreamquality <130073078+dreamquality@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This pull request migrates the test reporting infrastructure from Allure 2 (Java-based) to Allure 3 (TypeScript-based), eliminating the Java runtime dependency and modernizing the reporting stack.
Changes:
- Replaced
allure-commandlinewith theallurenpm package (v3.0.1) - Updated package.json scripts to use new Allure 3 CLI syntax (removed
--cleanflag, added--outputflag) - Enhanced Allure reporter configuration in playwright.config.ts with detailed options and environment info capture
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Updated dependency from allure-commandline@^2.36.0 to allure@^3.0.0 and modified npm scripts for Allure 3 CLI compatibility |
| playwright.config.ts | Expanded allure-playwright reporter configuration with detailed reporting options and environment information capture |
| package-lock.json | Full dependency tree update reflecting the new Allure 3 package and its TypeScript-based dependencies |
| .github/workflows/playwright.yml | Updated report generation command to use new Allure 3 CLI syntax |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
.github/workflows/playwright.yml
Outdated
| - name: Generate Allure Report | ||
| if: always() | ||
| run: npm run allure-report | ||
| run: npx allure generate ./allure-results --output ./allure-report |
There was a problem hiding this comment.
The workflow uses npx allure generate command directly instead of using the npm script defined in package.json. Consider using npm run allure-report for consistency and maintainability. This way, if the command needs to change in the future, it only needs to be updated in one place (package.json).
| run: npx allure generate ./allure-results --output ./allure-report | |
| run: npm run allure-report |
There was a problem hiding this comment.
Applied in 04a22a2. The workflow now uses npm run allure-report for consistency.
|
@copilot reports's view is still the same as before in v2 |
… overwriting with Allure 2 Co-authored-by: dreamquality <130073078+dreamquality@users.noreply.github.com>
Fixed in 04a22a2. The issue was that Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
@copilot verify allure 3 has history as allure 2 has trends by history runs |
Co-authored-by: dreamquality <130073078+dreamquality@users.noreply.github.com>
Verified and added in dc0dafc. Allure 3 supports history and trends via
This provides the same trend/history functionality as Allure 2 had. |
Migrates reporting infrastructure from the legacy Java-based Allure 2 CLI to the modern TypeScript-based Allure 3 CLI.
Changes
allure-commandlinewithallurepackage; update scripts to usenpx allure(Allure 3 removes--cleanflag—auto-overwrites output)yuvalgabay/allure-v3-report-action@v3.2.2for Allure 3 report generation with history/trends support; retrieve previous history from gh-pages branch; keep last 20 reports for trend visualization; deploy report with full history to GitHub PagesBenefits
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.