Resolving 'fullName' Field Issue in Allure-Pytest: A Local Solution and Call for Official Adjustment

Hello, currently I am using Allure TestOps to manage my automated tests, and after much searching, I finally found a small issue that was not noticeable before in allure-pytest. The problem is that when I run tests with examples using (@pytest.mark.parametrize) with more than one test, at the end of the execution, the result.json file is filled with the "fullName" field containing only the test name without the examples appended. In other words, when I add the execution results to TestOps, it considers it as a single test instead of the multiple tests I have in the parametrize. Here's an example below:


After cloning the allure-python repository, I was able to identify that in the utils.py file of allure-pytest, on line 122, the method "allure_full_name" is located. What I did to test it locally was to modify the line that previously read:

test = item.originalname if isinstance(item, pytest.Function) else item.name.split("[")[0]

to:
test = item.name

After reinstalling the library locally, the issue was resolved as evidenced below:


I didn't encounter any functionality issues with allure-pytest after making this local modification. Can you make this adjustment officially in the library?

Beginnen Sie in allure-pytest/utils.py bei der Methode allure_full_name um Zeile 122 und reproduzieren Sie das Problem mit einem pytest.mark.parametrize-Test mit mehreren Beispielen. Untersuchen Sie die generierte result.json und verifizieren Sie, dass jedes parametrisierte Ergebnis einen eindeutigen fullName hat, damit TestOps die Tests separat erkennt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.