Could you add field about failed screenshot information to reports/xml-report/result.xml

[slymanAktas]

Is your feature request related to a problem? Please describe.

• Unfortunately I don't like gauge's own html report, because I have more then 5000+ test and it couldn't be big picture about test result.
• So I generate allure result from xml-report/result.xml.
• But there is no information about screenshot path of failed test case on result.xl.
• So screenshot could't be included on allure result report which generated from xml-report/result.xml.

Describe the solution you'd like

• Failed screenshot information should be added to reports/xml-report/result.xml

Describe alternatives you've considered

• It would be better if you add failed test result as categorized.
  Before going through all the specs detail on html report, I want to see how many tests got 500 error and how many test failed in case of assertion issue

Additional context

• Could you inform me if there is any other way to create allure-result other then result.xml

[omutwar]

Hello @slymanAktas , thank you for providing this info!
I'll try to implement this, it's taking a while for me to figure this one out.

I may post some following questions also.

[Hungleminh]

Hi @omutwar , @slymanAktas

I just want to follow up this issue because i'm facing the same problem. Do you have anythings news for this issue?

Note: My issue https://github.com/orgs/allure-framework/discussions/2737

Regards,

[sriv]

gauge's xml-report was designed to follow the junit xml spec (see an example here. -https://github.com/testmoapp/junitxml?tab=readme-ov-file#example)

If you have any suggestions on where this information can be placed in the xml report - it should be fairly easy to bring that in since the plugin gets this information from gauge itself.

[Hungleminh]

@sriv do you mean the format of xml can be modified to get the result we wanted? If yes, can I modify by myself or i need to submit the support ticket to the support team?

[sriv]

in a manner of speaking, yes. It would require a change in the xml-report plugin. Unfortunately there isn't a way for a user to modify/override it (yet).

I am transferring this issue to the right repo. Feel free to post the xml-schema that would work for your usecase. If you like you can submit a pull request with the desired changes and I can review it.

On a side note - there is no "support team" for gauge - just a bunch of volunteers spending their personal time help maintain the project.

[Hungleminh]

Thanks @sriv for your response. I dont have any specific xml-schema (sorry for my limited of this knowledge). In my case, I just need a basic information such as: total pass/failed/error, duration, suite/spec/scenarios name, details steps and failed screenshot attached by failed step.

And I tend to think that would be great if we can have a config file that helping much in modify the report by owner and shows the result with information we wanted.

Regarding to the note, thanks for your correction. I truly appreciate your work as well as volunteers's effort. Great job you guys!

[sriv]

And I tend to think that would be great if we can have a config file that helping much in modify the report by owner and shows the result with information we wanted.

this particular case is more than a config unfortunately. It will require using a code change since the way this is generated is to use xml serialization rather than templating. This is where the layout is - https://github.com/getgauge/xml-report/blob/master/builder/xmlReportBuilder.go#L39-L55

There is another option to explore if you need to take control on the output - the "raw" output of a test run is exposed to a reporting plugin, and you can write your own plugin to take that output and transform it to any format you need.

This seed project can help you get started - https://github.com/getgauge-contrib/report-seed

Alternatively, if you can think of what additional fields will help enhance the xml-report - please paste here and that can help decide the amount of changes.