Is it possible to disable xcpretty in scan?

[benjaminsnorris]

New Issue Checklist

• Updated fastlane to the latest version
• I have read the Contribution Guidelines

Issue Description

I am having a problem with my iOS project that code coverage data from UI tests is not reported. I have tried using Slather and directly with Codecov, as well as just looking locally, and no data is reported for UI tests. There is an issue reported in xcov, as well as an issue reported in Codecov that discuss this further. I'm wanting to keep using Fastlane, and want to try disabling xcpretty to see if I can get proper results. I can disable it fine with gym, but cannot figure it out with scan. Thanks!

[TKBurner]

Hi @benjaminsnorris right now that's not possible in scan but it'd be an interesting PR. Would you be interested in contributing to our repo? We'd love that 👍

[ghost]

@benjaminsnorris Could you use the output_style option with raw? Looking at the code, this should eliminate the use of xcpretty.

fastlane/scan/lib/scan/test_command_generator.rb

Lines 62 to 92 in 0e54a6d

	def pipe
	# During building we just show the output in the terminal
	# Check out the ReportCollector class for more xcpretty things
	pipe = ["| tee '#{xcodebuild_log_path}'"]
	if Scan.config[:output_style] == 'raw'
	return pipe
	end
	formatter = []
	if Scan.config[:formatter]
	formatter << "-f `#{Scan.config[:formatter]}`"
	elsif FastlaneCore::Env.truthy?("TRAVIS")
	formatter << "-f `xcpretty-travis-formatter`"
	UI.success("Automatically switched to Travis formatter")
	end
	if Helper.colors_disabled?
	formatter << "--no-color"
	end
	if Scan.config[:output_style] == 'basic'
	formatter << "--no-utf"
	end
	if Scan.config[:output_style] == 'rspec'
	formatter << "--test"
	end
	return pipe << ["| xcpretty #{formatter.join(' ')}"]
	end

[benjaminsnorris]

Sorry, I should have come back to this. I did some manual tests and found that the underlying issue of UI test code coverage is not solved by disabling scan, so this fell completely off my radar.

[ohayon]

Thanks for following up! Going to close this issue as it seems to have been a red herring resolved. Feel free to continue conversation if necessary! 🐙