allure 3.0.0-beta.7 → 3.0.0-beta.9

package/README.md

@@ -1,33 +1,165 @@
-# Allure CLI
- 
+# Allure 3
+
+**Allure 3** is the next evolution of the Allure reporting framework, rebuilt from the ground up with a new architecture and expanded capabilities. Unlike its predecessor, **Allure 2**, this version is developed in **TypeScript** and introduces a modular plugin system for greater flexibility. A key addition is the **Awesome** plugin, which delivers an enhanced UI for better report visualization.
+
+> 🚧 **Allure 3 is currently in beta and under active development.**  
+> Although not production-ready, we encourage users to install, explore, and share feedback with the development team.
+
+The **Allure 3 CLI** provides a comprehensive suite of commands designed to streamline the generation, serving, and management of test reports.
+
 [<img src="https://allurereport.org/public/img/allure-report.svg" height="85px" alt="Allure Report logo" align="right" />](https://allurereport.org "Allure Report")
 
 - Learn more about Allure Report at https://allurereport.org
 - 📚 [Documentation](https://allurereport.org/docs/) – discover official documentation for Allure Report
 - ❓ [Questions and Support](https://github.com/orgs/allure-framework/discussions/categories/questions-support) – get help from the team and community
-- 📢 [Official announcements](https://github.com/orgs/allure-framework/discussions/categories/announcements) – be in touch with the latest updates
+- 📢 [Official annoucements](https://github.com/orgs/allure-framework/discussions/categories/announcements) – be in touch with the latest updates
 - 💬 [General Discussion ](https://github.com/orgs/allure-framework/discussions/categories/general-discussion) – engage in casual conversations, share insights and ideas with the community
 
----
+## Key Features
+
+Allure 3 introduces several notable improvements. The framework has been entirely rewritten in **TypeScript**, making it more extensible and easier to maintain. Its **plugin system** allows you to customize and extend reporting functionality to fit your specific needs. Configuration has been simplified with a **single file** managing all report settings, making it more convenient to handle multiple reports.
+
+One of the standout features is **real-time reporting**, which lets you view live updates during test execution using the `watch` command. The report interface itself has been redesigned to enhance usability and clarity. Moreover, Allure 3 maintains **compatibility with the entire Allure ecosystem**, supporting all major test frameworks.
+
+> 🚧 Please note that **official CI/CD integrations and IDE plugins are not yet available** for Allure 3.
+
+## Installation
+
+To install Allure 3 globally, you can use [`npm`](https://docs.npmjs.com/downloading-and-installing-packages-globally). Simply run:
+
+```bash
+npm install -g allure
+```
+
+However, we recommend using `npx` for running Allure commands without needing a global installation:
+
+```bash
+npx allure run -- <test_command>
+```
+
+This approach ensures you always use the latest version without managing global dependencies.
 
-## Overview
+## Commands
 
-The Allure CLI is a main entry point which includes many sub-commands
+### Running Tests and Generating Reports
 
-## Install
+Running tests and generating a report with Allure 3 is straightforward. Using the `run` command, you can execute your test suite and automatically generate a report:
 
-Use your favorite package manager to install the package:
+```bash
+npx allure run -- <test_command>
+```
+
+For example, if you're using `npm` as your test runner, the command would be:
 
-```shell
-npm add allure
-yarn add allure
-pnpm add allure
+```bash
+npx allure run -- npm test
 ```
 
-## Usage
+To successfully generate a report, ensure that your test setup outputs results into an `allure-results` directory, which is automatically detected by Allure 3. This directory can be placed at any nested level within your project (e.g., `out/tests/allure-results`), provided it retains the correct name.
+
+After the tests complete, the report is generated automatically. Existing results from previous runs are ignored, as Allure 3 focuses solely on new data to ensure accurate and up-to-date reporting.
+
+### Generating Reports Manually
 
-The CLI provides a set of commands to work with Allure Report features. To see the list of available commands, run:
+If you already have test results and wish to generate a report manually, use the `generate` command:
 
-```shell
-allure --help
+```bash
+npx allure generate <resultsDir>
 ```
+
+By default, this command produces an **Allure 3 Awesome** report. You can customize output settings, such as the destination directory, through the configuration file. If you prefer a **Classic** or **Allure 2-style** report, or need to disable certain plugins, these adjustments can also be made via configuration.
+
+### Viewing Reports
+
+To view a previously generated report locally, the `open` command serves it in your default browser:
+
+```bash
+npx allure open <reportDir>
+```
+
+If you’ve defined the output directory in your configuration file, specifying `<reportDir>` is optional. By default, Allure 3 looks for a directory named `allure-report`. To open the Awesome report directly, point to the nested directory:
+
+```bash
+npx allure open allure-report/awesome
+```
+
+### Real-time Report Monitoring
+
+When you need to monitor test execution live, the `watch` command provides dynamic report updates. It continuously monitors the specified results directory for changes and refreshes the report automatically:
+
+```bash
+npx allure watch <allureResultsDir>
+```
+
+This command is ideal for iterative development and debugging, allowing you to see immediate feedback as you modify and rerun tests. The browser tab updates seamlessly whenever new results are detected.
+
+### Command-line Options
+
+The Allure CLI includes several helpful global options. Use `--help` to explore available commands or get detailed usage information for a specific command:
+
+```bash
+npx allure run --help
+npx allure watch --help
+```
+
+To check your installed version of Allure 3, use:
+
+```bash
+npx allure --version
+```
+
+
+## Configuration
+
+Allure 3 uses an `allurerc.mjs` configuration file to manage report settings, including the report name, output directory, and plugin options.
+
+> 💡 **Tip:** We recommend using the **Awesome** plugin for the best experience.  
+> Support for Classic and Allure 2-style reports is currently experimental.
+
+### Example Configuration File
+
+```js
+import { defineConfig } from "allure";
+
+export default defineConfig({
+  name: "Allure Report Example",
+  output: "./out/allure-report",
+  plugins: {
+    awesome: {
+      options: {
+        singleFile: true,
+        reportLanguage: "en",
+      },
+    },
+  },
+});
+```
+
+In this example, the generated report is named *Allure Report Example* and saved to the `./out/allure-report` directory. The **Awesome** plugin is enabled with options to produce a single-file HTML report in English.
+
+### Configuration Options
+
+The configuration file allows you to fine-tune report generation. Key options include:
+
+- **`name`**: Specifies the report’s display name.
+- **`output`**: Defines the directory where the report will be saved.
+- **`plugins`**: Enables and configures plugins, with each supporting various options.
+
+### Awesome Plugin Options
+
+The **Awesome** plugin offers several customizable options:
+
+- **`singleFile`** *(boolean)*: If set to `true`, generates the report as a single standalone HTML file.
+- **`reportName`** *(string)*: Overrides the default report name.
+- **`open`** *(boolean)*: Automatically opens the report after generation if enabled.
+- **`reportLanguage`** *(string)*: Sets the UI language of the report. Supported languages include:
+
+  `az`, `br`, `de`, `en`, `es`, `fr`, `he`, `ja`, `kr`, `nl`, `pl`, `ru`, `sv`, `tr`, `zh`.
+
+For example, setting `"reportLanguage": "fr"` will render the report interface in French.
+
+## Final Notes
+
+Allure 3 represents a significant step forward in test reporting, offering improved performance, flexibility, and an enhanced user interface. While it remains in beta, the framework is stable enough for exploration and feedback. We encourage you to experiment with the **Awesome** plugin and share your insights to help us refine the experience.
+
+Stay updated with the latest features, and don’t hesitate to contribute or report issues. Together, we can make Allure 3 the best it can be!

package/dist/commands/allure2.d.ts

@@ -0,0 +1,11 @@
+type ClassicCommandOptions = {
+    output?: string;
+    reportName?: string;
+    reportLanguage?: string;
+    singleFile?: boolean;
+    historyPath?: string;
+    knownIssues?: string;
+};
+export declare const ClassicLegacyCommandAction: (resultsDir: string, options: ClassicCommandOptions) => Promise<void>;
+export declare const ClassicLegacyCommand: (cli: import("cac").CAC) => void;
+export {};

package/dist/commands/allure2.js

@@ -0,0 +1,70 @@
+import { AllureReport, resolveConfig } from "@allurereport/core";
+import * as console from "node:console";
+import { createCommand } from "../utils/commands.js";
+export const ClassicLegacyCommandAction = async (resultsDir, options) => {
+    const before = new Date().getTime();
+    const { output, reportName: name, historyPath, knownIssues: knownIssuesPath, ...rest } = options;
+    const config = await resolveConfig({
+        output,
+        name,
+        historyPath,
+        knownIssuesPath,
+        plugins: {
+            "@allurereport/plugin-allure2": {
+                options: rest,
+            },
+        },
+    });
+    const allureReport = new AllureReport(config);
+    await allureReport.start();
+    await allureReport.readDirectory(resultsDir);
+    await allureReport.done();
+    const after = new Date().getTime();
+    console.log(`the report successfully generated (${after - before}ms)`);
+};
+export const ClassicLegacyCommand = createCommand({
+    name: "allure2 <resultsDir>",
+    description: "Generates Allure Classic report based on provided Allure Results",
+    options: [
+        [
+            "--output, -o <file>",
+            {
+                description: "The output directory name. Absolute paths are accepted as well",
+                default: "allure-report",
+            },
+        ],
+        [
+            "--report-name, --name <string>",
+            {
+                description: "The report name",
+                default: "Allure Report",
+            },
+        ],
+        [
+            "--report-language, --lang <string>",
+            {
+                description: "Default language of the report (default: OS language)",
+            },
+        ],
+        [
+            "--single-file",
+            {
+                description: "Generate single file report",
+                default: false,
+            },
+        ],
+        [
+            "--history-path, -h <file>",
+            {
+                description: "The path to history file",
+            },
+        ],
+        [
+            "--known-issues <file>",
+            {
+                description: "Path to the known issues file. Updates the file and quarantines failed tests when specified",
+            },
+        ],
+    ],
+    action: ClassicLegacyCommandAction,
+});

package/dist/commands/index.d.ts

@@ -1,6 +1,7 @@
 export * from "./history.js";
 export * from "./testplan.js";
 export * from "./classic.js";
+export * from "./allure2.js";
 export * from "./awesome.js";
 export * from "./csv.js";
 export * from "./history.js";

package/dist/commands/index.js

@@ -1,6 +1,7 @@
 export * from "./history.js";
 export * from "./testplan.js";
 export * from "./classic.js";
+export * from "./allure2.js";
 export * from "./awesome.js";
 export * from "./csv.js";
 export * from "./history.js";

package/dist/commands/run.js

@@ -54,6 +54,7 @@ const runTests = async (allureReport, cwd, command, commandArgs, environment, si
         allureResultsWatchers.delete(ar);
     }
     await processWatcher.abort();
+    return code;
 };
 export const RunCommandAction = async (options) => {
     const args = options["--"];
@@ -61,9 +62,9 @@ export const RunCommandAction = async (options) => {
         throw new Error("expecting command to be specified after --, e.g. allure run -- npm run test");
     }
     const before = new Date().getTime();
-    process.on("exit", (code) => {
+    process.on("exit", (exitCode) => {
         const after = new Date().getTime();
-        console.log(`exit code ${code} (${after - before}ms)`);
+        console.log(`exit code ${exitCode} (${after - before}ms)`);
     });
     const command = args[0];
     const commandArgs = args.slice(1);
@@ -98,7 +99,7 @@ export const RunCommandAction = async (options) => {
         ],
     });
     await allureReport.start();
-    await runTests(allureReport, cwd, command, commandArgs, {}, silent);
+    let code = await runTests(allureReport, cwd, command, commandArgs, {}, silent);
     for (let rerun = 0; rerun < maxRerun; rerun++) {
         const failed = await allureReport.store.failedTestResults();
         if (failed.length === 0) {
@@ -111,7 +112,7 @@ export const RunCommandAction = async (options) => {
         const tmpDir = await mkdtemp(join(tmpdir(), "allure-run-"));
         const testPlanPath = resolve(tmpDir, `${rerun}-testplan.json`);
         await writeFile(testPlanPath, JSON.stringify(testPlan));
-        await runTests(allureReport, cwd, command, commandArgs, {
+        code = await runTests(allureReport, cwd, command, commandArgs, {
             ALLURE_TESTPLAN_PATH: testPlanPath,
             ALLURE_RERUN: `${rerun}`,
         }, silent);
@@ -120,7 +121,7 @@ export const RunCommandAction = async (options) => {
     }
     await allureReport.done();
     await allureReport.validate();
-    process.exit(allureReport.exitCode);
+    process.exit(code ?? allureReport.exitCode);
 };
 export const RunCommand = createCommand({
     name: "run",

package/dist/index.js

@@ -2,11 +2,12 @@ import { cac } from "cac";
 import console from "node:console";
 import { readFileSync } from "node:fs";
 import { cwd } from "node:process";
-import { AwesomeCommand, ClassicCommand, CsvCommand, GenerateCommand, HistoryCommand, KnownIssueCommand, LogCommand, OpenCommand, QualityGateCommand, RunCommand, SlackCommand, TestPlanCommand, WatchCommand, } from "./commands/index.js";
+import { AwesomeCommand, ClassicCommand, ClassicLegacyCommand, CsvCommand, GenerateCommand, HistoryCommand, KnownIssueCommand, LogCommand, OpenCommand, QualityGateCommand, RunCommand, SlackCommand, TestPlanCommand, WatchCommand, } from "./commands/index.js";
 const pkg = JSON.parse(readFileSync(new URL("../package.json", import.meta.url), "utf8"));
 const cli = cac(pkg.name).usage(pkg.description).help().version(pkg.version);
 const commands = [
     ClassicCommand,
+    ClassicLegacyCommand,
     AwesomeCommand,
     CsvCommand,
     GenerateCommand,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "allure",
-  "version": "3.0.0-beta.7",
+  "version": "3.0.0-beta.9",
   "description": "Allure Commandline Tool",
   "keywords": [
     "allure",
@@ -30,16 +30,18 @@
     "test": "vitest run"
   },
   "dependencies": {
-    "@allurereport/core": "3.0.0-beta.7",
-    "@allurereport/core-api": "3.0.0-beta.7",
-    "@allurereport/directory-watcher": "3.0.0-beta.7",
-    "@allurereport/plugin-api": "3.0.0-beta.7",
-    "@allurereport/plugin-awesome": "3.0.0-beta.7",
-    "@allurereport/plugin-progress": "3.0.0-beta.7",
-    "@allurereport/plugin-server-reload": "3.0.0-beta.7",
-    "@allurereport/plugin-slack": "3.0.0-beta.7",
-    "@allurereport/reader-api": "3.0.0-beta.7",
-    "@allurereport/static-server": "3.0.0-beta.7",
+    "@allurereport/core": "3.0.0-beta.9",
+    "@allurereport/core-api": "3.0.0-beta.9",
+    "@allurereport/directory-watcher": "3.0.0-beta.9",
+    "@allurereport/plugin-allure2": "3.0.0-beta.9",
+    "@allurereport/plugin-api": "3.0.0-beta.9",
+    "@allurereport/plugin-awesome": "3.0.0-beta.9",
+    "@allurereport/plugin-classic": "3.0.0-beta.9",
+    "@allurereport/plugin-progress": "3.0.0-beta.9",
+    "@allurereport/plugin-server-reload": "3.0.0-beta.9",
+    "@allurereport/plugin-slack": "3.0.0-beta.9",
+    "@allurereport/reader-api": "3.0.0-beta.9",
+    "@allurereport/static-server": "3.0.0-beta.9",
     "cac": "^6.7.14",
     "lodash.omit": "^4.5.0",
     "yoctocolors": "^2.1.1"
@@ -52,7 +54,8 @@
     "@typescript-eslint/eslint-plugin": "^8.0.0",
     "@typescript-eslint/parser": "^8.0.0",
     "@vitest/runner": "^2.1.8",
-    "allure-vitest": "^3.0.7",
+    "@vitest/snapshot": "^2.1.8",
+    "allure-vitest": "^3.0.9",
     "eslint": "^8.57.0",
     "eslint-config-prettier": "^9.1.0",
     "eslint-plugin-import": "^2.29.1",