Question: Why Scanfile overrides multi_scan options

[lyndsey-ferguson]

From @AyaAkl25

When having options inside multi_scan like scheme or workspace but there is already these options as default in scanfile, I can see
that multi_scan overrides its option with options of scanfile. Although I checked this is not happening with normal run_tests action of
fastlane.

I also checked the code and logs displayed and I find a line of log that shows that this overrides is intended to happen, but was
wondering why? because in some cases I don't want multi_scan to take the options from scanfile
So my question like I mentioned in issue above, why is this intended and how could I change that if possible?

Thank you for such great tool, We use it now to work with parallel execution and retry logic which is helping us a lot.

[lyndsey-ferguson]

Hello @AyaAkl25. multi_scan depends on scan, so it will end up using the Scanfile that you have configured for scan (also known as run_tests). There are only a few places that multi_scan overrides the options, but be assured that it only does this where it needs to. The options that you pass to multi_scan need to take precedence, otherwise, you would receive the results that you expect.

[lyndsey-ferguson]

There are two ways to prevent multi_scan from using the Scanfile that occur to me.

1. Delete your Scanfile.
2. Monkeypatch the Scanfile.scanfile_name method before you call multi_scan. I haven't tested the code, but I think it would look like this:

scan_module_monkeypatch.rb

module Scan
  class << self 
  
  def scanfile_name
    "NoScanfile"
  end
end

Fastfile

require_relative 'scan_module_monkeypatch'

lane :yourlanename do
  multi_scan(...)
end