So far, we have accomplished a lot with fastlane, automating our workflow from registering to building our apps to publishing them to the app store, along with screenshots and metadata. As you pasue to appreciate how much easier our workflow is, be assured that we aren’t done yet; there is still a lot more to offer, and we will continue to press on with our next action, scan (https://docs.fastlane.tools/actions/run_tests/).
scan fits into our fastlane workflow seamlessly, allowing us to conduct automated testing, either adhoc or as part of our Fastfile, making it easier to create specific configurations to output tests in either HTML, JSON, Unit reports, or through sending the outcome straight to Slack. This action is certainly an important one that should be a part of your lane right before you publish to the App Store, or for beta-testing...
