Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make limits configurable #1137

Closed
brunabrk opened this issue Sep 13, 2024 · 3 comments
Closed

Make limits configurable #1137

brunabrk opened this issue Sep 13, 2024 · 3 comments

Comments

@brunabrk
Copy link

brunabrk commented Sep 13, 2024

Describe Feature
Right now, the History entries are limited to 20 and thread columns in each graph (https://allurereport.org/docs/history-and-retries/#how-to-enable-history). It would be nice if this could be configurable and not a fixed value.

Describe the solution
Allure could make this limit configurable via vitest.config.ts

Example:


import { defineConfig } from "vitest/config";

export default defineConfig({
  test: {
    dir: "./test/spec",
    testTimeout: 20000,
    setupFiles: ["allure-vitest/setup"],
    reporters: ["basic", ["allure-vitest/reporter", { resultsDir: "./out/allure-results",  allureResultsLimit: "100"}]],
    typecheck: {
      enabled: true,
      tsconfig: "./tsconfig.test.json",
    },
  },
});

Thank you!

@baev
Copy link
Member

baev commented Oct 2, 2024

The limits are enforced by the allure report generator and can't be changed via reporter config.

closed as a duplicate of allure-framework/allure2#1331

@baev baev closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2024
@brunabrk
Copy link
Author

brunabrk commented Oct 2, 2024

@baev is the plan to work on this allure-framework/allure2#1331? This is opened June 23 2021

@baev
Copy link
Member

baev commented Oct 2, 2024

The issue will be addressed in the upcoming Allure 3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants