Skip to content
This repository has been archived by the owner on Nov 19, 2018. It is now read-only.

Add support for output_name parameter #27

Closed
sguillope opened this issue Oct 31, 2015 · 9 comments
Closed

Add support for output_name parameter #27

sguillope opened this issue Oct 31, 2015 · 9 comments

Comments

@sguillope
Copy link

It would be nice if it was possible to specify the name of the output file (similar to gym's output_name parameter).
We are running our tests on Bamboo but the Junit Parser plugin only seems to parse files with an .xml extension. We currently have to manually rename the output file report.junit to have the .xml extension.

@KrauseFx
Copy link
Collaborator

@sguillope It's probably best to add a mv command after running scan, as even if you'd specify an output name, it might not include the extension.

@xfreebird
Copy link

@KrauseFx is there a reason why you used the .junit file extension ? since most the tools I know creates the JUnit report with the .xml extension.

@KrauseFx
Copy link
Collaborator

KrauseFx commented Nov 1, 2015

@xfreebird I think it was default of xcpretty

@xfreebird
Copy link

from xcpretty I see that the default report name is build/reports/junit.xml

The file name is coming from scan/report_collector.rb in generate_commands:

        file_name = "report.#{type}"
        output_path = output_file_name || File.join(File.expand_path(Scan.config[:output_directory]), file_name)

I think it would be better to use a different name for report.junit, something like junit/TEST-report.xml. This is a wide used name format for junit tests reports.

@KrauseFx
Copy link
Collaborator

KrauseFx commented Nov 1, 2015

Sounds good to me 👍

@Tokuriku
Copy link

Tokuriku commented Dec 2, 2015

Any advances made on this issue?

@jacobvanorder
Copy link

👍

@jeeftor
Copy link

jeeftor commented Dec 12, 2015

I fully agree with this! .xml would make things more compatible with bamboo

@fastlane-bot-helper
Copy link

This issue was migrated to fastlane/fastlane#1942. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀

@fastlane-old fastlane-old locked and limited conversation to collaborators Mar 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants