[v5]When running test in multiply files test result are show inside the first file

[ohank]

Test result reports inside other tests result in a hierarchy.

And I sorting on fail show no result:

I am using pytest to run tests and send the result to reportportal. Not sure if this is an agent bug or the web site that is doing anything wrong.

Expected behavior
I expected the each file with tests to be group together not all files in the first file.

Desktop (please complete the following information):

• Ubuntu/Windows
• chrome
• The version of what? web browser or os?

[evjlobanova]

@ohank send us please any details? so that we will be able to reproduce this issue?
@iivanou what info would be useful for debugging this problem?

[iivanou]

@ohank Can you try changes from #183? Let us know the results.

[ohank]

@iivanou changes from #183 from did fix the problem with nested hierarchy. Still problem show list of pass, skipped. failed and total. But to investigation works. Here are som screenshot:

[iivanou]

@ohank Sorry, I do not understand what's wrong on your screenshot...

[ohank]

I click the number under PASSED and get that no result is found on the page that opens. 6 test shall be shown in the second screenshot.

[iivanou]

Take a look at the URL generated when you click on the PASSED number. It will be similar to `

item2Params=filter.eq.hasStats%3Dtrue%26filter.eq.hasChildren%3Dfalse%26filter.in.type%3DSTEP%26filter.in.status%3DPASSED

If you change STEP to TEST in that URL, you will get what you want. If you think it is an issue, please open it in the reportportal project. It has nothing to do on the agent side. @DzmitryHumianiuk From my point of view, it'd be better to fill up the default filter with the TEST item type instead of the STEP one.

[DzmitryHumianiuk]

@iivanou that's architectual desicion fail, made 7 years ago.
We named objects corresponding to Test Case as steps, assuming the option to involve BDD.

Now we have nested steps.

And change of STEP type to TEST will affect all variety of our agents, clients and UI as well.
We plan this big step for RP 6.

[ohank]

@iivanou I agree with "It has nothing to do on the agent side". It was more that I did report on the reportprotal project, to begin with. Thanks for your help!

@DzmitryHumianiuk It is good you know the problem and has a plan to fix it =)
The thing that is nuclear for me is that in reportportal 4.3 this was working. Have something change in reportportal 5 so this behavior happens based on the architectural decision?

[DzmitryHumianiuk]

@ohank where was no big changes for the structure from v4.3 to v5.

Maybe just minor cleans ups from UI side, in order to minimize the move in RPv6.

My suggestion to get it work: change it in client.
Send your tests as type STEP.

[ohank]

Fix is committed.