Add support for output_name parameter about scan HOT 9 CLOSED

@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.

from scan.

@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.

from scan.

@xfreebird I think it was default of xcpretty

from scan.

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.

from scan.

Sounds good to me 👍

from scan.

Any advances made on this issue?

from scan.

👍

from scan.

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

from scan.

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 🚀

from scan.