allure-framework / allure-framework/allure-python
JsonMappingException: Could not read test result file allure-results
- Dominant language
- Python
- Stars
- 814
- Forks
- 260
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the Bug
Getting a JsonMappingException using Allure single file generation when the parameter value exceeds the maximum allowed. The report is generated, but empty.
**I'm running on GitLab CI/CD.**
### Steps to Reproduce
- Try to get json file with params value more than maximum allowed (20000000)
- open cmd
- run `allure generate --single-file allure-results --clean`
### Expected Behaviour
The report is generated without errors.
### Screenshots or Additional Context
Could not read test result file allure-results/03142bda-850b-4896-a93b-ca53751bdbc9-result.json
com.fasterxml.jackson.databind.JsonMappingException: String value length (20054016) exceeds the maximum allowed (20000000, from `StreamReadConstraints.getMaxStringLength()`) (through reference chain: io.qameta.allure.model.TestResult["steps"]->java.util.ArrayList[7]->io.qameta.allure.model.StepResult["parameters"]->java.util.ArrayList[3]->io.qameta.allure.model.Parameter["value"])
### What Language are you using?
Python
### What Framework/Allure Integration you are using?
Allure Pytest-BDD
### What version of Allure Integration you are using?
2.13.5
### What version of Allure Report you are using?
2.34
### Code of Conduct
I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Start by reproducing the failure with the `allure generate --single-file allure-results --clean` command and inspect the reported `allure-results/03142bda-850b-4896-a93b-ca53751bdbc9-result.json` file. Trace how the oversized `steps` parameter value is handled, and consider the report complete when this result file no longer causes generation to fail and the report is populated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100