Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#1130 Initial swift package manager support #1193

Merged
merged 15 commits into from
Jan 6, 2021

Conversation

kenji21
Copy link
Contributor

@kenji21 kenji21 commented Nov 12, 2020

#1130

As some project refers to openium/master and I don't want to force push to this branch, I created another branch to update my initial PR #1147 to current KIF master

Basically the same changes (removing precompiled headers (.pch) and moving files to be "more" SPM compliant)

@kenji21 kenji21 changed the title #1130 Initial swift package manager support [WIP] #1130 Initial swift package manager support Nov 12, 2020
@kenji21
Copy link
Contributor Author

kenji21 commented Nov 12, 2020

Since previous PR, Github Actions have been added, waiting for it to run

I still need to cherry-pick my latest commit demoing integration using "path package" of KIF in a test project and ask review to @dostrander or @justinseanmartin

Edit:

first CI job is an epic fail:

	 Executed 234 tests, with 656 failures (628 unexpected) in 3529.200 (3579.777) seconds

run is at: https://github.com/kif-framework/KIF/pull/1193/checks?check_run_id=1392807500

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 13, 2020

Got Xcode 10.3 back... got issue on AutoCorrectTests::testSmartQuotesEnabled, and on AutoCorrectTests_ViewTestActor::testSmartQuotesEnabled (2 assertions per test => 4 failures), but not on the ones of Github Actions... 🙁

Test Suite 'KIF Tests - XCTest.xctest' failed at 2020-11-13 09:23:58.324.
	 Executed 266 tests, with 4 failures (4 unexpected) in 872.233 (880.675) seconds
Test Suite 'All tests' failed at 2020-11-13 09:23:58.325.
	 Executed 266 tests, with 4 failures (4 unexpected) in 872.233 (880.677) seconds

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 13, 2020

Same result with ci script :

export DEVELOPER_DIR=/Applications/Xcode_10.3.app/Contents/Developer
./scripts/ci.sh 
Executed 266 tests, with 4 failures (4 unexpected) in 882.941 (890.868) seconds

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 13, 2020

tried again by running ci script in a ssh session... same errors

	 Executed 266 tests, with 4 failures (4 unexpected) in 884.942 (893.389) seconds

2020-11-13 10:42:43.565 xcodebuild[25708:59884020] [MT] IDETestOperationsObserverDebug: 904.832 elapsed -- Testing started completed.
2020-11-13 10:42:43.565 xcodebuild[25708:59884020] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
2020-11-13 10:42:43.565 xcodebuild[25708:59884020] [MT] IDETestOperationsObserverDebug: 904.832 sec, +904.832 sec -- end

Failing tests:
	KIF Tests:
		-[AutocorrectTests testSmartQuotesEnabled]
		-[AutocorrectTests testSmartQuotesEnabled]
		-[AutocorrectTests_ViewTestActor testSmartQuotesEnabled]
		-[AutocorrectTests_ViewTestActor testSmartQuotesEnabled]

I suspect than user interaction is not enabled, so all tests are failing (maybe because of user not logged in on CI server)

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 13, 2020

OK, tried Actions on another project, it is not "user interaction disabled" issue

As Xcode run tests alphabetically, I move the [BackgroundTests testBackgroundApp] to the end by renaming its class to ZBackgroundTests:

ZBackgroundTests

    ✓ testBackgroundApp (3.880 seconds)

TableViewTests
  testTappingLastRowAndSectionWithoutAnimation, The step timed out after 10.00 seconds: Found an accessibility element with the label "Last Cell", but not with the traits "8"
  /Users/runner/work/KIF/KIF/KIF Tests/TableViewTests.m:57
    [tester tapRowAtIndexPath:[NSIndexPath indexPathForRow:-1 inSection:-1] inTableViewWithAccessibilityIdentifier:@"TableView Tests Table"];
    [tester waitForViewWithAccessibilityLabel:@"Last Cell" traits:UIAccessibilityTraitSelected];
}
  testTappingLastRowAndSectionWithoutAnimation, failed: caught "KIFFailureException", "The step timed out after 10.00 seconds: Found an accessibility element with the label "Last Cell", but not with the traits "8""
  <unknown>:0

	 Executed 266 tests, with 2 failures (2 unexpected) in 977.533 (986.589) seconds

EDIT: run is : https://github.com/kif-framework/KIF/pull/1193/checks?check_run_id=1396588868

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 14, 2020

Force pushed to trigger another build because first time iPad build was stopped because of fail in iPhone tests
So it works on iPad, but not on iPhone X, 🤔
let's try using an iPhone 8 instead of X

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 14, 2020

so there is an issue with testTappingLastRowAndSectionWithoutAnimation but only on iPhone X maybe due to safe areas

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 14, 2020

nice, CI works for building SPM package, here is the command added to scripts/ci.sh to build the package for the simulator:

swift build -Xcc "-isysroot" -Xcc "$(xcrun --sdk iphonesimulator --show-sdk-path)" -Xcc "-target" -Xcc "x86_64-apple-ios$(xcrun --sdk iphonesimulator --show-sdk-version)-simulator"

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 14, 2020

As there are 3 projects built by CI (Testable Swift.xcodeproj, Testable.xcodeproj and Calculator.xcodeproj), to not duplicate code, @justinseanmartin @dostrander what do you think of modifying one to integrate the framework using SPM (doing so will require Xcode 11 minimum for this project, thus adding Xcode 11 in the CI matrix)

@justinseanmartin
Copy link
Contributor

justinseanmartin commented Nov 14, 2020 via email

@dostrander
Copy link
Contributor

@kenji21 Sounds good to me

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 16, 2020

Ok, as Calculator.xcodeproj uses KIF.framework, Testable.xcodeprojuses KIF static library and Testable Swift.xcodeproj also uses KIF.framework, I have removed KIF.xcodeproj and drag & dropped KIF folder (Xcode find it is a Swift Package) in Testable Swift.xcodeproj :

Screenshot 2

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 17, 2020

Tested on my mac using export DEVELOPER_DIR="/Applications/Xcode_11.7.app/Contents/Developer" and then running

On Xcode 11.7 with an iPhone SE (2nd generation) many tests fails (https://github.com/kif-framework/KIF/pull/1193/checks?check_run_id=1408774849):

 Executed 266 tests, with 474 failures (474 unexpected) in 2923.099 (2933.903) seconds

Found one issue:

-(void) testPullToRefreshByAccessibilityIdentifierWithDuration
{
	UITableView *tableView;
	[tester waitForAccessibilityElement:NULL view:&tableView withIdentifier:@"Test Suite TableView" tappable:NO];

    [tester tapViewWithAccessibilityLabel:@"Reset Refresh Control"];
	[tester pullToRefreshViewWithAccessibilityIdentifier:@"Test Suite TableView" pullDownDuration:KIFPullToRefreshInAboutThreeSeconds];
	[tester waitForViewWithAccessibilityLabel:@"Bingo!"];
	[tester waitForAbsenceOfViewWithAccessibilityLabel:@"Bingo!"];
}

makes refresh control label to have text "Refreshing...", and then waitForViewWithAccessibilityLabel:"Bingo!" fails

- (IBAction)resetRefreshControl
{
	self.refreshControl.attributedTitle = [[NSAttributedString alloc] initWithString:NSLocalizedString(@"Refreshing...", @"") attributes:nil];
}

To fix this:

 -(void)pullToRefreshHandler
 {
-       self.refreshControl.attributedTitle = [[NSAttributedString alloc] initWithString:NSLocalizedString(@"Bingo!", @"") attributes:nil];
     dispatch_after(dispatch_time(DISPATCH_TIME_NOW, (int64_t)(4.0 * NSEC_PER_SEC)), dispatch_get_main_queue(), ^{
+        self.refreshControl.attributedTitle = [[NSAttributedString alloc] initWithString:NSLocalizedString(@"Bingo!", @"") attributes:nil];
         [self.refreshControl endRefreshing];
         [self.tableView setContentOffset:CGPointZero animated:YES];
     });

Found another one that could be the source of many issues: the photo selector is shown and not cancelled, so I moved SystemAlertTests to the end of execution

Next actions should give a result like: Executed 266 tests, with 34 failures (34 unexpected) in 993.439 (1001.637) seconds

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 17, 2020

Run 1410490218 gets better than expected:

	 Executed 266 tests, with 24 failures (24 unexpected) in 973.740 (982.695) seconds

Failing tests:
	KIF Tests:
		-[AutocorrectTests testSmartQuotesEnabled]
		-[AutocorrectTests testSmartQuotesEnabled]
		-[AutocorrectTests_ViewTestActor testSmartQuotesEnabled]
		-[AutocorrectTests_ViewTestActor testSmartQuotesEnabled]
		-[TypingTests testEnteringTextIntoFirstResponder]
		-[TypingTests testEnteringTextIntoFirstResponder]
		-[TypingTests testEnteringTextIntoViewWithAccessibilityLabel]
		-[TypingTests testEnteringTextIntoViewWithAccessibilityLabel]
		-[TypingTests_ViewTestActor testEnteringTextIntoFirstResponder]
		-[TypingTests_ViewTestActor testEnteringTextIntoFirstResponder]
		-[TypingTests_ViewTestActor testEnteringTextIntoViewWithAccessibilityLabel]
		-[TypingTests_ViewTestActor testEnteringTextIntoViewWithAccessibilityLabel]
		-[ZSystemAlertTests testAuthorizingPhotosAccess]
		-[ZSystemAlertTests testAuthorizingPhotosAccess]
		-[ZSystemAlertTests testAuthorizingPhotosAccess]
		-[ZSystemAlertTests testAuthorizingPhotosAccess]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]


** TEST FAILED **

As expected, System Alerts Tests are broken

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 17, 2020

After fixing typing tests:

Executed 266 tests, with 16 failures (16 unexpected) in 928.241 (936.347) seconds

@kenji21 kenji21 force-pushed the spm-support branch 2 times, most recently from 413d837 to e10bdad Compare November 17, 2020 09:03
@kenji21
Copy link
Contributor Author

kenji21 commented Nov 17, 2020

Smart dashes fixed:

	 Executed 266 tests, with 16 failures (16 unexpected) in 928.241 (936.347) seconds

Failing tests:
	KIF Tests:
		-[AutocorrectTests testSmartQuotesEnabled]
		-[AutocorrectTests testSmartQuotesEnabled]
		-[AutocorrectTests_ViewTestActor testSmartQuotesEnabled]
		-[AutocorrectTests_ViewTestActor testSmartQuotesEnabled]
		-[ZSystemAlertTests testAuthorizingPhotosAccess]
		-[ZSystemAlertTests testAuthorizingPhotosAccess]
		-[ZSystemAlertTests testAuthorizingPhotosAccess]
		-[ZSystemAlertTests testAuthorizingPhotosAccess]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]

let's continue by loading UIAutomation.framework correctly (note that UIAutomation.framework no longer exists within Xcode 12)

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 17, 2020

Nice,

Fixed AutocorrectTests, now 16 -> 12 fails, now time to fix System Alert Tests:

 Executed 266 tests, with 12 failures (12 unexpected) in 914.926 (923.222) seconds

Failing tests:
	KIF Tests:
		-[ZSystemAlertTests testAuthorizingPhotosAccess]
		-[ZSystemAlertTests testAuthorizingPhotosAccess]
		-[ZSystemAlertTests testAuthorizingPhotosAccess]
		-[ZSystemAlertTests testAuthorizingPhotosAccess]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]
		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 20, 2020

Ok, I was looking to xcrun simctl privacy help to deprecate the acknowledgeSystemAlert... it's ok for Location, but it doesn't provide support for Bluetooth / Push notifications ones...

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 20, 2020

As this PR was only intended to add SPM support, can we merge it, and treat the Xcode 11 acknowledgeSystemAlert issue support on another PR ?
I can squash all my commit into one if needed
Another issue is supporting devices having "safe areas" (e.g. iPhone X) as I saw that test were failing because of this
Another issue will be Xcode 12 as UIAutomation framework is not more present (test will fail see openium@ee59ab8#diff-e6c4dd745e29178b755895d5d06f10181fe788142825897ca4d6baed20e7f84dL216)

@dostrander
Copy link
Contributor

@kenji21 Can we add an early return if we detect that it is running xcode 11 for the system tests

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 24, 2020

@kenji21 Can we add an early return if we detect that it is running xcode 11 for the system tests

sure, i'll have to rebase my branch on master (pbxproj have many conflicts)

@kenji21
Copy link
Contributor Author

kenji21 commented Nov 24, 2020

As this PR was only intended to add SPM support, can we merge it, and treat the Xcode 11 acknowledgeSystemAlert issue support on another PR ?

=> #1156

I can squash all my commit into one if needed

Another issue is supporting devices having "safe areas" (e.g. iPhone X) as I saw that test were failing because of this

=> #1196

Another issue will be Xcode 12 as UIAutomation framework is not more present (test will fail see openium@ee59ab8#diff-e6c4dd745e29178b755895d5d06f10181fe788142825897ca4d6baed20e7f84dL216)

=> Fixed by early return

So Xcode 11 tests are OK, but carthage build using Xcode 12 is failing

@kenji21
Copy link
Contributor Author

kenji21 commented Dec 1, 2020

Sorry, I haven't see it (confused by Xcode/iOS versions), it seems that's always the System Alert Tests that are also failing for iOS 11. :/

Failing tests:
3178	KIF Tests:
3179		-[ZSystemAlertTests testAuthorizingLocationServicesAndNotificationsScheduling]
3180		-[ZSystemAlertTests testAuthorizingLocationServicesAndNotificationsScheduling]
3181		-[ZSystemAlertTests testAuthorizingLocationServicesAndNotificationsScheduling]
3182		-[ZSystemAlertTests testAuthorizingLocationServicesAndNotificationsScheduling]
3183		-[ZSystemAlertTests testAuthorizingPhotosAccess]
3184		-[ZSystemAlertTests testAuthorizingPhotosAccess]
3185		-[ZSystemAlertTests testAuthorizingPhotosAccess]
3186		-[ZSystemAlertTests testAuthorizingPhotosAccess]
3187		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
3188		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
3189		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
3190		-[ZSystemAlertTests_ViewTestActor testAuthorizingLocationServices]
3191		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]
3192		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]
3193		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]
3194		-[ZSystemAlertTests_ViewTestActor testAuthorizingPhotosAccess]

Just rebased on top of current master (this one was easier than the previous one, merging a pbxproj is hard)

@dostrander
Copy link
Contributor

@kenji21 they also use the UIAutomation framework

@kenji21
Copy link
Contributor Author

kenji21 commented Dec 8, 2020

I am missing something, executed them on our CI after installing Xcode 11.6 and downloading simulator 11.4 (as it is in .travis.yml from current master)

$ export DEVELOPER_DIR=/Applications/Xcode_11.6.app/Contents/Developer/
$ SIMULATOR="name=iPad Pro (12.9-inch) (2nd generation),OS=11.4"
$ ./scripts/ci.sh "${SIMULATOR}"
[...]
ZBackgroundTests
    ✓ testBackgroundApp (13.208 seconds)
ZSystemAlertTests
    ✓ testAuthorizingLocationServicesAndNotificationsScheduling (1.540 seconds)
    ✓ testAuthorizingPhotosAccess (1.538 seconds)
ZSystemAlertTests_ViewTestActor
    ✓ testAuthorizingLocationServices (1.539 seconds)
    ✓ testAuthorizingPhotosAccess (1.538 seconds)


	 Executed 275 tests, with 0 failures (0 unexpected) in 759.207 (768.921) seconds
[...]

what surprises me is that Xcode 11.6 ship with iOS 13.6 see xcodereleases.com

@kenji21
Copy link
Contributor Author

kenji21 commented Dec 8, 2020

ok, it breaks in the beforeEach() method

ZSystemAlertTests
  testAuthorizingLocationServicesAndNotificationsScheduling, The step timed out after 10.00 seconds: Failed to find accessibility element with the label "System Alerts"
  /Users/travis/build/kif-framework/KIF/KIF Tests/SystemAlertTests.m:30
{
    [tester tapViewWithAccessibilityLabel:@"System Alerts"];
}

@kenji21
Copy link
Contributor Author

kenji21 commented Dec 8, 2020

It seems that one test is flaky...

Failing tests:
	KIF Tests:
		-[WebViewTests_ViewTestActor testTappingLinks]

** TEST FAILED **

while my previous push was fine:

Screenshot 11

@@ -12,7 +12,11 @@ jobs:
matrix:
run-config:
- { xcode_version: '10.3', simulator: 'name=iPad (5th generation),OS=12.4' }
- { xcode_version: '10.3', simulator: 'name=iPhone X,OS=12.4' }
- { xcode_version: '10.3', simulator: 'name=iPhone 8,OS=12.4' }
#- { xcode_version: '11.7', simulator: 'name=iPad (7th generation),OS=13.7' }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: remove comments

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done in openium@4f286cf

@@ -8,11 +8,11 @@

#import <KIF/KIF.h>

@interface BackgroundTests : KIFTestCase
@interface ZBackgroundTests : KIFTestCase
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rename back to BackgroundTests

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done in openium@4f286cf

@@ -35,6 +35,9 @@ - (void)afterEach {
}

- (void)testBackgroundApp {
#if defined(__IPHONE_14_0) // Xcode 12, UIAutomation framework not available
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could we just do if (@available(iOS 14.0, *)) ??

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done in openium@4f286cf

@@ -8,11 +8,11 @@

#import <KIF/KIF.h>

@interface SystemAlertTests : KIFTestCase
@interface ZSystemAlertTests : KIFTestCase
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rename back to SystemAlertTests

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done in openium@4f286cf

@@ -21,6 +21,9 @@ + (XCTestSuite *)defaultTestSuite
if ([UIDevice.currentDevice.systemVersion compare:@"8.0" options:NSNumericSearch] < 0) {
return nil;
}
#if defined(__IPHONE_13_0) // Xcode 11
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use @available instead of #ifs ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done in openium@4f286cf


@interface SystemAlertTests_ViewTestActor : KIFTestCase
@interface ZSystemAlertTests_ViewTestActor : KIFTestCase
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change back to SystemAlertTests_ViewTestACtor

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done in openium@4f286cf

@@ -20,7 +20,7 @@ - (NSNumber *)AXInspectorEnabled:(id)specifier;
@end


static void * loadDylibForSimulator(NSString *path)
void * loadDylibForSimulator(NSString *path)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why did this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to use it from UIAutomationHelper.m, reverted in openium@4f286cf

@@ -213,7 +214,12 @@ - (BOOL)_alertIsValidAndVisible:(UIAAlert *)alert;
}

- (void)linkAutomationFramework {
dlopen([@"/Developer/Library/PrivateFrameworks/UIAutomation.framework/UIAutomation" fileSystemRepresentation], RTLD_LOCAL);
NSString *path = @"/Developer/Library/PrivateFrameworks/UIAutomation.framework/UIAutomation";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this help anything for uiautomation?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tried to find why UIAutomation fails to load, see that loadDylibForSimulator prepends IPHONE_SIMULATOR_ROOT to framework path, but it didn't helped, reverted in openium@4f286cf

Copy link
Contributor

@dostrander dostrander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for doing this, i know a bunch of folks have been really excited for this

@kikeenrique
Copy link
Contributor

Can I ask for the plans to merge this?
I'm one of those folks excited for having SPM integration.

@kikeenrique
Copy link
Contributor

FYI, I've tested https://github.com/openium/KIF/tree/spm-support and found no problems so far in my projects.
Looks quite promising! Nice work! (hope it gets merged soon 🤞)

@kenji21
Copy link
Contributor Author

kenji21 commented Dec 22, 2020

FYI, I've tested https://github.com/openium/KIF/tree/spm-support and found no problems so far in my projects.
Looks quite promising! Nice work! (hope it gets merged soon 🤞)

please use https://github.com/openium/KIF/tree/spm-support-freez as I may rewrite history (if squash needed for example) and force push on spm-support branch

@kikeenrique
Copy link
Contributor

FYI, I've tested https://github.com/openium/KIF/tree/spm-support and found no problems so far in my projects.

Looks quite promising! Nice work! (hope it gets merged soon 🤞)

please use https://github.com/openium/KIF/tree/spm-support-freez as I may rewrite history (if squash needed for example) and force push on spm-support branch

Thanks for the info 😀.
Nevertheless, probably, after having tested it, I will patiently wait for an official release.

@dostrander
Copy link
Contributor

@kenji21 This looks good to me once you are ready to merge let me know. Only reason i'm not currently is it still has the WIP title :)

@kenji21 kenji21 changed the title [WIP] #1130 Initial swift package manager support #1130 Initial swift package manager support Dec 28, 2020
@dostrander dostrander merged commit b5a49ac into kif-framework:master Jan 6, 2021
@dostrander
Copy link
Contributor

@kenji21 This has duplicate files, moved the files around without fixing the podspec, and not including anything in the IdentifierTests subspec. I need to revert this for now. If you could fix these issues that would be helpful. I am going to add a check to make sure that the podspec should validate which would have picked up these issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants