xctest

Suppose we have some validation in our ViewController ( say vc1 ) for a UItextfield in shouldChangeCharactersInRange method, as user only can enter the numbers not the alphabets or other special character. I just want to know that in our XCTestCase class, is this possible in unit testing, to check for a particular uitextfield , is allowing some characters (in my case only numbers) or not? Make unit tests that call shouldChangeCharactersInRange and check the expectation that the result should be true, or false. This is an example of how to unit test delegate methods. Where UIKit invokes a

I've created a GPX file and added it to my project. If I have my project running, I can select the GPX file from the dropdown of possible locations to simulate and have it correctly apply the defined path. The project contains 2 schemes: the Main Scheme and the MainTest Scheme. I've set up both to use the GPX file as the "Default Location" on the "Options" tab. Further, Under the "Test" area of both schemes, I've specified the same file again. Main Scheme Run Options Main Scheme Test setup Test Scheme Run Options Test Scheme Test setup When I Run the app on a simulator, it correctly applies

I am looking for opinions from test engineers and iOS developers regarding a specific matter. I have been using Appium for over a year now, and I have come across various difficulties while running mobile web tests on real devices. Every time Apple makes changes in XCTest or Safari, Appium is directly impacted (even if they fix something, some other issue pops up in its place), and it has come to a point where I'm spending more time resolving Appium related issues as opposed to the ones from an AUT. Furthermore, you would need an Apple computer to develop and execute Appium iOS tests anyway.

I am trying to replicate a pull to refresh on a UITableView using the new Xcode UI testing framework in Xcode 7 (beta 3) My current approach is dragging from the table to whatever element below the table I can find. This works when there is a fixed item below the table like a UIToolbar or UITabBar I would rather not rely on having a UITabBar or UIToolbar but I can't figure out a way to do the pull to refresh/drag action without using the method in XCUIElement . func pressForDuration(duration: NSTimeInterval, thenDragToElement otherElement: XCUIElement) But it fails when I don't have a toolbar

I would like to write a UI test in Xcode covering a login with FBDSKLoginKit . However, Facebook iOS SDK uses SFSafariViewController presented to the user in order to authenticate her and unfortunately, there's no way how to interact with SFSafariViewController in UI tests in Xcode 7 . Any ideas how to test the facebook login without interacting with SFSafariViewController ? thexande Swift 3 Xcode 8 solution func testFacebookLogin() { let app = XCUIApplication() // set up an expectation predicate to test whether elements exist let exists = NSPredicate(format: "exists == true") // as soon as

可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 由 翻译 强力驱动 问题: I have a XCTest bundle which I can run through xcode on a simulator by using simctl . I am using the iPhone 6 iOS 9.1 simulator with the following environment variables: export SIMCTL_CHILD_TestBundleLocation = "/Users/User/ios_app/DerivedData/primus/Build/Products/Debug-iphonesimulator/Tests.xctest" export SIMCTL_CHILD_XCInjectBundle = "/Users/User/ios_app/DerivedData/primus/Build/Products/Debug-iphonesimulator/Tests.xctest" export SIMCTL_CHILD_XCInjectBundleInto = "/Users/User/ios_app/DerivedData/primus/Build/Products/Debug

I am trying to build and run test cases using command line for iOS test cases. I have given the following command: xcodebuild -target AppEngineTests -configuration Debug -sdk iphonesimulator TEST_AFTER_BUILD=YES clean build It builds the app but the testcases are not run. could someone please help? Thanks tooluser I've found the name property to require more specification. xcodebuild test -workspace #{WORKSPACE_FILE} -scheme #{TEST_SCHEME} -destination 'platform=iOS Simulator,name=iPhone Retina (4-inch),OS=7.0' Was what finally worked for me. iPhone was limited and/or unpredictable. As another