fastlane-plugin-test_center 3.8.0 → 3.8.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0c9e21b3d030a91eafe41d2d3f4d70ee1736e2c4ae36c13218374a5669e0f5b5
-  data.tar.gz: 176a4e44e5f695404e33e1be399133178bbe7cfb6cf907e6cfc0d16381de2722
+  metadata.gz: 71f2ac632a905eaab2a3e9c7495fb1a3f17553f85979802daed0ba7611aa5eed
+  data.tar.gz: '095c5cf65ad0b71a8bd34a1883547951320470321e789f264f8987af83c47d4b'
 SHA512:
-  metadata.gz: b23d9fc31f7418859a56f835220b95ed6d251423cf1cbbd34e52766f128400b65b76e4cf692f52e30c4c502fd84b2e4fd2bd29103aac492f815a4e5edc57a3a3
-  data.tar.gz: 713ca27af8ee375ef245183527d32338d28f15a85f6c91647ee8f52bda7adf3b759fb004a7d16eb5d4bb34a13161ca2a1f5d253ae0288639c8310b502aa79b49
+  metadata.gz: 975f4be5396c3a3f6d45099d612c3b0a684101d52197cbed9f204bde048d91a0a884b35b9b5575007f08f3b2e2d4ad75c7c52841e66eb1c060ad86f7ca88c81d
+  data.tar.gz: 045ddfbe7d933c411f5c376e41e8cff69188d894411c46cd8838a01b68f0728110771d4690143b65055e3bc776e5407e0739711718b430a9dc58a78916b0f0d4

data/README.md

@@ -102,6 +102,9 @@ Another issue that can cause tests to incorrectly fail comes from an issue with
 
 Make better use of your Mac resources by running batches of test runs in parallel iOS Simulators running simultaneously. Use the `:parallel_testrun_count` option to specify 2 to 6 simulators, each running a subset of your tests. It is not recommended to run more than 6 simulators in parallel as the service that backs the simulators can fail to connect to them.
 
+##### Note: while Xcode provides the option to run testsuites in parallel, this does not help if one testsuite has 100 testcases and another has 300 testcases. That's because each of those testsuites will run on their own iOS Simulator and you have to wait for the Simulator with the most testcases: 300 testcases in this example.
+##### `multi_scan`, on the other hand, can split those tests into 4 batches of 100 using a `:parallel_testrun_count` of 4. You only have to wait for the iOS Simulators to finish 100 testcases.
+
 #### Inspect Partial Results
 
 If you have a large number of tests, and you want to inspect the overall status of how test runs are progressing, you can use the `:testrun_completed_block` callback to bailout early or make adjustments on how your tests are exercised.

data/lib/fastlane/plugin/test_center/actions/multi_scan.rb

@@ -121,7 +121,8 @@ module Fastlane
 
         defaults = Hash[Fastlane::Actions::ScanAction.available_options.map { |i| [i.key, i.default_value] }]
         FastlaneCore::UI.verbose("MultiScanAction resetting Scan config to defaults")
-        
+        defaults.delete(:destination)
+
         Scan.config._values.each do |k,v|
           Scan.config.set(k, defaults[k]) if defaults.key?(k)
         end

data/lib/fastlane/plugin/test_center/helper/multi_scan_manager/retrying_scan_helper.rb

@@ -224,7 +224,7 @@ module TestCenter
               junit: File.absolute_path(report_filepath)
             }
           )
-          @options[:only_testing] = Fastlane::Actions::TestsFromJunitAction.run(config)[:failed]
+          @options[:only_testing] = Fastlane::Actions::TestsFromJunitAction.run(config)[:failed].map(&:shellsafe_testidentifier)
           if @options[:invocation_based_tests]
             @options[:only_testing] = @options[:only_testing].map(&:strip_testcase).uniq
           end

data/lib/fastlane/plugin/test_center/version.rb

@@ -1,5 +1,5 @@
 module Fastlane
   module TestCenter
-    VERSION = "3.8.0"
+    VERSION = "3.8.1"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: fastlane-plugin-test_center
 version: !ruby/object:Gem::Version
-  version: 3.8.0
+  version: 3.8.1
 platform: ruby
 authors:
 - Lyndsey Ferguson
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-08-07 00:00:00.000000000 Z
+date: 2019-08-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: json