What is it?
Fastlane plugin for XCHTMLReport
- Install XCHTMLReport
fastlane add_plugin xchtmlreport
- Add the following to your Scanfile
- Add a call to
xchtmlreportafter running your tests. For example
lane :tests do scan ( fail_build: false # Otherwise following steps won't be executed ) xchtmlreport end
Specify the path to the result bundle
By default the plugin will use the default location of the result bundle which is under fastlane/test_output/ but your also have the ability to pass the path yourself
xchtmlreport( result_bundle_path: path_to_result_bundle )
You can also pass multiple paths
xchtmlreport( result_bundle_paths: [ path_to_ui_result_bundle, path_to_unit_result_bundle ] )
Specify path to xchtmlreport
XCHTMLReport is by default install at /usr/local/bin/xchtmlreport. Should it be somewhere else you can pass the path to the binary to the plugin
xchtmlreport( binary_path: path_to_xchtmlreport )
Enable JUnit reporting
You can enable the JUnit reporting as well
xchtmlreport( enable_junit: true )
Please create an issue whenever you find an issue or think a feature could be a good addition to XCTestHTMLReport's fastlane plugin. Always make sure to follow the Contributing Guidelines. Feel free to take a shot at these issues.
XCTestHTMLReport's fastlane plugin is available under the MIT license.
If you have trouble using plugins, check out the Plugins Troubleshooting guide.
Using fastlane Plugins
For more information about how the
fastlane plugin system works, check out the Plugins documentation.
fastlane is the easiest way to automate beta deployments and releases for your iOS and Android apps. To learn more, check out fastlane.tools.