You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
using pytest.mark.parametrize will miss some testcase in report #778
support request => Please do not submit support request here, see note at the top of this template.
What is the current behavior?
when i use pytest.mark.parametrize ,in specific data situations, i got same historyId for two diffent testcase, when report cameout, only one of two testcase show in report.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Allure version: 2.19.0
Test framework: pytest@7.2.2
Allure adaptor: allure-pytest@2.13.2
Other information
Becourse in allure_pytest.util.get_history_id, only use values in original_values to generate historyId
Maybe use both name and value will solve the problem
Thank you for your report, @Pegasus-Yang !
There is a bug in how we hash arguments to create historyId. Due to this bug, empty strings don't affect the result, so the actual sequence of arguments that get into historyId is ["admin", 12345] in both cases. The same bug, I believe, causes some other collisions, like 1 and "1".
I'll fix it soon.
Activity
delatrie commentedon Dec 5, 2023
Thank you for your report, @Pegasus-Yang !
There is a bug in how we hash arguments to create historyId. Due to this bug, empty strings don't affect the result, so the actual sequence of arguments that get into historyId is
["admin", 12345]in both cases. The same bug, I believe, causes some other collisions, like1and"1".I'll fix it soon.
saaj commentedon Jun 24, 2024
Here is a workaround when you don't need the history feature, but just one-off report: