GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — Changing an id of a pytest parameter set breaks test's history · Issue #744 · allure-framework/allure-python Closed Labels DescriptionI'm submitting a ...
What is the current behavior?Assigning or changing an id of a parameter set in pytest's If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problemGiven we have the following test file: import pytest @pytest.mark.parametrize("v", [1]) def test_issue744_reproduction(v): pass When we run pytest (without the import pytest @pytest.mark.parametrize("v", [1], ids=["a"]) def test_issue744_reproduction(v): pass When we run pytest again we end up with two test results with different If we generate the report it will look like this: What is the expected behavior?Both results should be considered retries (i.e., should have the same 'historyId' values). Assigning an id to a parameter set should only affects the default title of the test (where a portion of the What is the motivation / use case for changing the behavior?More flexibility to refactor tests without losing the history of runs/reruns. Please tell us about your environment:
Other informationMost probably will be fixed together with #743. Activity
MetadataMetadataAssigneesLabelsTypeProjectsMilestoneRelationshipsDevelopmentIssue actions |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |