allure-framework / allure-framework/allure3
Tests history not visible on UI when using allurerc.mjs
- Dominant language
- HTML
- Stars
- 401
- Forks
- 58
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
[allure-missing-tests-history.zip](https://github.com/user-attachments/files/28641162/allure-missing-tests-history.zip)
**Describe the bug**
Tests history is not visible on the report UI (awesome).
Using pytest as tests framework with python3.
Having the following allurerc.mjs
```
import {defineConfig} from "allure";
export default defineConfig({
name: "Missing tests history",
historyPath: "./history.jsonl"
})
```
When I run `allure generate` first time the history.jsonl file is generated in the root directory. After the second run, of the same tests, there is no history information available.
**To Reproduce**
Steps to reproduce the behavior:
1. Unpack attached archive [allure-missing-tests-history.zip](https://github.com/user-attachments/files/28641194/allure-missing-tests-history.zip)
```unzip allure-missing-tests-history.zip```
2. Initialize python and allure environment
```./init.sh```
4. Execute the first tests run
```./run1.sh```
6. Execute the second tests run
```./run2.sh```
7. Start web server
```npx serve allure-report```
8. Browse to allure UI http://localhost:3000
**Screenshots**
**Desktop (please complete the following information):**
- OS: Ubuntu Linux 24.04
- Browser: Chrome 148.0.7778.167 (Official Build) (64-bit)
Contributor guide
Research direction
Start by unpacking the attached archive and running init.sh, run1.sh, and run2.sh with the allurerc.mjs configuration. Inspect history.jsonl and the generated allure-report after the second run; done means the report UI displays test history for the repeated tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100