Guillermo Ignacio Enriquez Gutierrez

Hi, After a long time... It is already 2021 so 2 years later... To me, building a view for all the passed/failed/skipped tests (what XCTestHTMLReport does) and calculating the code...

After long time... I think there is no reliable way of doing this from xchtmlreport (or any library like this). Only developer knows about what screenshots are important to correctly...

After a long time ... Apparently Xcode now provides a way to reduce number of screens shots. Tyler said: > ... you may be able to workaround this issue in...

I wonder if it is the same as this issue: https://github.com/XCTestHTMLReport/XCTestHTMLReport/issues/203 Takeshi fixed this and PR was merged recently. Needs confirmation.

Yeah! I agree with your suggestion totally.I think updating the hardcoded version string to be always in sync with the tag is something we need. I imagine a manually triggered...

Do you think it is good we do this in `next` branch?

I wonder why this Pull-Request didn't land? Not it is old and conflicted but I think adding this is nice. Trainer automatically does this.

I recently was investigating about junit format and found the properties tag. I think this info should be inside the `property` tags, I believe they were put in the name...

Hi @ssharma0312 Thank you suggesting that. In the README.md at the bottom there is a section about Contribution (With a link to [CONTRIBUTING.md](https://github.com/XCTestHTMLReport/XCTestHTMLReport/blob/develop/CONTRIBUTING.md)). > Contribution > >Please create an issue...

@ssharma0312 Sorry for late response. ## If you want to check the changes manually: When you build with SPM (swift build ...) then the binary is somewhere inside .build folder....