You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to create some kind of tool that can verify that all the test files are added to the test target. It's not uncommon for a test file to get removed from a test target during a .xcodeproj merge conflict resolution. If that happens, entire test classes can ended up being abandoned and forgotten about for a long time.
We'll need to spend some time designing how we'd want this to work, but I'm thinking that no matter how we end up designing it, it's going to have to be some kind of command line tool that can be run as a run script build phase.
The text was updated successfully, but these errors were encountered:
As you mentioned, this probably needs to be a command line tool. I believe we should write that in Swift, and check the source files in to this repository in their own directory... but those source files should not be pulled in by the Podspec. Instead, we need to provide the compiled tool in the Podspec.
Then we need to figure out how to craft the Podspec so that when running pod install, a build phase is added to any targets that list MTK as a dependency to run the tool.
The tricky part is going to be figuring out exactly which files should count. I guess we can look for any files that... what... inherit from XCTestCase (or inherit from a subclass of it)? But we actually need to look at more than just whether or not it's included in the test target. We need to care about whether or not the tests are actually enabled. ... and we probably need to allow for a configuration file, right?
And at this point, I'm thinking this might work as an independent tool, rather than part of MetovaTestKit.
I'd like to create some kind of tool that can verify that all the test files are added to the test target. It's not uncommon for a test file to get removed from a test target during a .xcodeproj merge conflict resolution. If that happens, entire test classes can ended up being abandoned and forgotten about for a long time.
We'll need to spend some time designing how we'd want this to work, but I'm thinking that no matter how we end up designing it, it's going to have to be some kind of command line tool that can be run as a run script build phase.
The text was updated successfully, but these errors were encountered: