kif-framework

How do I set the accessibility label for a particular segment of a UISegmentedControl?

左心房为你撑大大i 提交于 2019-12-28 16:36:45
问题 We use KIF for our functional testing, and it uses the accessibility label of elements to determine where to send events. I'm currently trying to test the behaviour of a UISegmentedControl, but in order to do so I need to set different accessibility labels for the different segments of the control. How do I set the accessibility label for a particular segment? 回答1: I'm just getting started with KIF myself, so I haven't tested this, but it may be worth a try. I'm sure I'll have the same issue

How do I set the accessibility label for a particular segment of a UISegmentedControl?

青春壹個敷衍的年華 提交于 2019-12-28 16:35:31
问题 We use KIF for our functional testing, and it uses the accessibility label of elements to determine where to send events. I'm currently trying to test the behaviour of a UISegmentedControl, but in order to do so I need to set different accessibility labels for the different segments of the control. How do I set the accessibility label for a particular segment? 回答1: I'm just getting started with KIF myself, so I haven't tested this, but it may be worth a try. I'm sure I'll have the same issue

Linker error comes while running as well as testing the Xcode workspace after updating KIF framework via cocoapods

别来无恙 提交于 2019-12-23 10:22:02
问题 I have an Xcode workspace in which I have updated to KIF 2.0(pod update via terminal & pod 'KIF' in the podfile) after that I have configured the workspace as per the instructions provided in https://github.com/kif-framework/KIF#configure-the-testing-target(installation with Cocoapods section).But when I tried to execute the project as well as Run my test target it throws an error, ld: building for iOS Simulator, but linking against dylib built for MacOSX file '/Applications/Xcode.app

How do I turn off the Accessibility Inspector in the iOS 9 simulator?

六眼飞鱼酱① 提交于 2019-12-22 09:58:08
问题 The accessibility inspector is turned on by my KIF tests (apparently it's necessary for KIF to work.) Problem is, its window occludes controls some subsequent UI tests need to tap on and those tests fail. How can I turn the Accessibility Inspector off when my KIF tests are done with it so my UI Tests can run? (Turning it off "manually" from the simulator's Settings app is not a solution—I'm looking for something I can call from code, set in the target or...?) 回答1: It is not on by default. You

All KIF test steps are throwing the same error, what am I doing wrong?

若如初见. 提交于 2019-12-20 05:57:50
问题 When running my KIF target regardless of how I write my KIFTestScenario or KIFTestStep they are returning the following error: 12:20:58.434 - Test that a user can successfully dismiss the welcome screens 12:24:53.208 - FAIL (209.11s): Tap screen at point "{10, 10}" 12:24:53.209 - FAILING ERROR: Error Domain=KIFTest Code=0 "Step threw exception: *** -[__NSArrayM insertObject:atIndex:]: object cannot be nil" UserInfo=0x842c1e0 {NSLocalizedDescription=Step threw exception: *** -[__NSArrayM

how to programmatically tap a point on the iOS keyboard

穿精又带淫゛_ 提交于 2019-12-13 02:07:57
问题 I'm using KIF to automate my app, and I'm trying to automate typing something into a UISearchBar and searching for it. Unfortunately I couldn't find a satisfactory way to do that by programmatically clicking on the search button after I've entered my search text. So instead, I considered simply using KIF's tapScreenAtPoint method. The problem with that method is that it does the following: CGPoint windowPoint = [window convertPoint:screenPoint fromView:nil]; view = [window hitTest:windowPoint

how to order kif testcase sequences?

ε祈祈猫儿з 提交于 2019-12-12 14:53:32
问题 I used the latest version of KIF framework and create several testing cases (subclass of KIFTestCase). May I know is there any way to change the order of the sequences of testing runs? for examples I have testA.m testB.m testC.m ... how to make the sequence such as testB.m testC.m testA.m when I hit a cmd+U for testing? 回答1: It's ordered alphabetically, example: - (void)testB {} will be the second test - (void)testA {} will be the first test - (void)testC {} will be the third test 回答2: This

How do I turn off the Accessibility Inspector in the iOS 9 simulator?

十年热恋 提交于 2019-12-05 21:52:51
The accessibility inspector is turned on by my KIF tests (apparently it's necessary for KIF to work.) Problem is, its window occludes controls some subsequent UI tests need to tap on and those tests fail. How can I turn the Accessibility Inspector off when my KIF tests are done with it so my UI Tests can run? (Turning it off "manually" from the simulator's Settings app is not a solution—I'm looking for something I can call from code, set in the target or...?) It is not on by default. You must turn it on manually. bby I saw the following on Stew Gleadow's blog . You just need to change the line

All KIF test steps are throwing the same error, what am I doing wrong?

依然范特西╮ 提交于 2019-12-02 09:53:54
When running my KIF target regardless of how I write my KIFTestScenario or KIFTestStep they are returning the following error: 12:20:58.434 - Test that a user can successfully dismiss the welcome screens 12:24:53.208 - FAIL (209.11s): Tap screen at point "{10, 10}" 12:24:53.209 - FAILING ERROR: Error Domain=KIFTest Code=0 "Step threw exception: *** -[__NSArrayM insertObject:atIndex:]: object cannot be nil" UserInfo=0x842c1e0 {NSLocalizedDescription=Step threw exception: *** -[__NSArrayM insertObject:atIndex:]: object cannot be nil} 12:24:53.210 - END OF SCENARIO (duration 223.62s) As suggested

How do I set the accessibility label for a particular segment of a UISegmentedControl?

旧巷老猫 提交于 2019-11-29 05:34:57
We use KIF for our functional testing, and it uses the accessibility label of elements to determine where to send events. I'm currently trying to test the behaviour of a UISegmentedControl, but in order to do so I need to set different accessibility labels for the different segments of the control. How do I set the accessibility label for a particular segment? I'm just getting started with KIF myself, so I haven't tested this, but it may be worth a try. I'm sure I'll have the same issue soon, so I'd be interested to hear if it works. First, UIAccessibility Protocol Reference has a note under