Open tejassharma96 opened 2 years ago
So, I'm just going to perform a brain dump so I'll let the text flow free form. If your fastlane script will be relying on multi_scan to build the project before hand, it will have to have run the magical discovery phase itself...unless that fails because you didn't provide the workspace or project. I don't remember if that will work. Let's say it would fail and you're just relying on the tests.......it is possible that I could pre-discover the project using's scan's magical way of discovery but I don't remember why I don't do that.. it would slow it down perhaps.
Is there anyway that your script could pass in the filepath to the scheme? That may be something I could accept optionally instead of looking for it. Then, the code could look for that (as either an input, or a special environment variable), and not need it for this code.
I need to be able to get the tests in order to properly batch, split, retry, etc...
thanks for the reply! I'm mostly trying to avoid adding another config item. for now I've just added
workspace = File.absolute_path(Dir["../*.xcworkspace"].first)
and that seems to have worked, but I was hoping you might be able to update the plugin to take advantage of scan's functionality that supports a few more use-cases and wouldn't require me to maintain it locally (ie my links in the original MR). If you just reuse scan's stuff, it isn't something you'd need to maintain. I think there's an even more straightforward way of doing this though by using detect_projects. I'm gonna make a quick PR to demonstrate what I mean.
I want to apologize that I have not responded to this issue. A family health issue is requiring me to narrow my focus on the essentials and I don't have the time I need to focus on the plugin more than a minute. If you can get some other contributors to this project to help with this, I would consider merging a resulting PR.
New Issue Checklist
fastlane-plugin-test_center
to the latest version