On one of the projects we have test method defined in next way:
@Parameters({"TUID", "userType", "startPage"})
@Test()
public void verifyItemSelection(String TUID, String userType, String startPage) {
TestRail.setTestCaseId(TUID);
......
Then on suite level we have multiple test items with different parameters, e.g.:
<test name="name1" enabled="true">
<parameter name="TUID" value="3709692,3705554"/>
<parameter name="userType" value="type1"/>
<parameter name="filterOption" value="filter1"/>
<parameter name="startPage" value="page1"/>
<classes>
<class name="classname1">
<methods>
<include name="verifyAppFilterResultsTest"/>
</methods>
</class>
</classes>
</test>
<test name="name2" enabled="true">
<parameter name="TUID" value="3709696,3705558"/>
<parameter name="userType" value="type2"/>
<parameter name="filterOption" value="filter2"/>
<parameter name="startPage" value="page2"/>
<classes>
<class name="classname2">
<methods>
<include name="verifyAppFilterResultsTest"/>
</methods>
</class>
</classes>
</test>
As a result in Zebrunner report for failed tests which are organised this way we have not realistic amount of tracked sessions. because test results page also includes sessions and logs related to other test items (see screenshot)

