How to perform XCode UI testing?

Automation is central to building high-quality iOS apps, andXcode UI testingprovides a built-in way to validate functionality directly within Apple ’ s IDE. UsingXCTest, developer can pen and run unit tests and UI tests, debug view hierarchy, capture screenshots, and run execution to cloud-based real device testing.

This article explains how Xcode automation with XCTest deeds, its key UI testing capabilities, and how to extend it with BrowserStack for scalable iOS testing.

Overall Workflow and Prerequisites

In this Xcode UI testing tutorial, we will discuss testing syntax and methodology specific to iOS XCTest, so you take to hold installed on your computer. Also, the frame-up could be continue to include mechanisation try with features.

One outstanding benefit of act with BrowserStack is that it provides access to a full orbit of devices on which you can run trial, which is lots more cost-effective than buying real iPhones for.

Here is an lineation of apply iOS UI testing and then extending it to integrate with real-device cloud and automation testing:

• You would need an coating to quiz; this could be a project that you are already working on or you could make a new project.
• Break down the project into components and modules and work on for each element.
• for testing various layers and functionality of the covering user interface use XCTest and Hierarchy Debugger.
• Run the test on your local developer set-up with Xcode, and analyze results and account from the examination.

Integrate with BrowserStack and features and run your tests collaboratively on the cloud.

Once you hold the task code in the development computer, you can use built-in characteristic in the Xcode IDE to start writing test code.

Getting Started with Writing Tests in Xcode

When creating a new project in Xcode, you must select the include unit and UI trial checkboxes to enable them in your project navigator workflow.

This will pre-configure the test navigator window to show and UI examination based on your project terminology. Just like unit test, you have set up and tear down office to manage the UI test environment set up and unclutter up once the run is complete. When you create a project with the unit tryout and UI tryout selection enabled, it creates wrapper stratum inside which further test codification can be contribute.

Here you can add more in depth code or extend the exam design to cover different scenario as per your requirements. If you are bring more functionality and components in the future you can create new UI test targets by snap on the ‘ + ’ icon in the prat leave nook of the Test navigator.

To edit a test plan (a file with a.xctestplanfile extension), select the test plan and click on Configuration.

Test plan form help adapt and tweak various parameters related to a examination plan like language, part, location etc. Writing unit test and UI tests under XCTest requires cognition of syntax and best testing methodologies which you can follow on their functionarydocumentation; let ’ s go through some simple examples to help you get begin.

Writing UI test with XCTest

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

XCTest ply APIs to access and control, simulated devices and diverse UI components of the covering. The summons of can be broken down into the following steps:

Initialise test classes

When write test suites it is a mutual practice to create utility classes, set up and rupture down functions for each class. This help control theXCUIApplicationand other APIs, that can be used to initiate and control trial session. It provides several useful functions to launch, terminate and manage the application session and mock data and addiction for your tryout run.

Write Individual exam functions

Once you ’ ve set up the correct pre/post-processing environs for your exam classes, you can write individual test functions. Within these functions you can test respective vista of the application and implement individual UI tests.

Select and work with app components

The XCUIElementQueryobject can be used to query and find different types of application part with the assistant of queries. After executing hunt for a ingredient you can use the assert function to differentiate success or failure.

• Here is an example of finding “ Home ” push and asserting result:

• Enter value in input fields

• Find and click on the 4th element in “ Menu ” list

Just like these there are many choice and huge variety of operations that you can perform using these APIs and object use; for a full credit, you can visit the official documentationhere. For a sample app with test examples check out our.

Take device and application screenshots

XCUIScreen and XCUIScreenshot Classes provide the office to conduct screenshots from a physical twist or a simulated session. Call the screenshot () method on an XCUIScreen instance to capture a screenshot of its current UI state. This method is added to XCUIScreen by the XCUIScreenshotProviding protocol.

• Taking a screenshot of current screen on the device

• Taking screenshots of all screens on the current device

These screenshots can be seen in test consequence with appropriate message by creating attachment.

Asserting expected behavior

It is essential to inclose the right assertions and checks at the required positions to institute success or failure for a test case. This will help you determine whether a given run was a success or a failure. Depending on the use example and the anteriority, the way of implementation could be different; here are some examples of different types of assertion that you can apply:

• Boolean assertions: Test if a condition returns true or mistaken.
• Nil or not-nil: Check if a condition returns of value or not.
• Equality and Inequality: Check whether two conditions returned the same value.
• Comparable Value: compare and check two values to determine if one is great.
• Error: check if a given function returns an error or not.
• Unconditional failure: This lets you declare failure at any point in the tryout example without depending on a variable or condition.
• Expected failure: You can explicitly specify expected points of failure without having to block the execution of the trial case expend this feature.
• Skip tests: This permit you define a conditions-based logic for skipping tests.

Managing averment at the right point in trial suit is significant, as this is how Xcode decides whether a test is successful. You can read in-depth on the syntax and functions for each of these assertions in depthhere.

Run tests and analyze results

You can run a single test, a batch of tests or a full test suite, depending on your requirements. You can use the navigation features and buttons to start the test or the command line interface. Once a test run is accomplished, the answer will be visually displayed inside the source codification editor in the left gutter with icons depicting the event. If you want to generate a shareable outcome file you can follow the next measure:

1.Run your XCUI tryout suite using thexcodebuild command.

2. From the reports navigator control-click a test or test activity and select the option to show in Finder. This will take you to the.xcresult file.

3. Open the.xcresultfile in Xcode by double-clicking on it, this should take you to the report in a standalone report navigator.

4. Click on the tryout list in the navigator to view further details.

5. Click on a tryout to see its story.

You can use thexcrun xcresulttoolto retrieve and evaluate the test results through command line, and parse them for farther analysis and sharing with the squad.

Testing UI with hierarchy debugger

Another great way of testing user interface is with the assistance of a hierarchy debugger and accessibility inspector built into Xcode. You can use the view debugger to scrutinise the view hierarchy of your paused app.

The debugger include a hierarchical tilt of interface objects, a canvass with an exploded 3D rendering of the hierarchy, and inspectors for the attributes of an object and the size of a view. Here are the steps to get started:

1. To open the scene debugger, click the Debug View Hierarchy push at the top of the debug region.
2. The panorama hierarchy in the navigator area shows a hierarchical list of the panorama controllers, aspect, and constraints in your paused app. Selecting an object in the listing highlight the like object on the canvas.

3. The canvas shows a 3D exploded view of the take objective, with its restraint and parent aim. The canvas also includes controls for zooming and rotate the view.
4. The inspectors in the lower dose include information about the selected aim ’ s attributes, such as its frame and layer place, as well as any constraints regard it.

Using SceneKitscene editor, you can quickly build, edit, and trailer game and interactive 3D apps. The ocular interface reduces code, streamlines design, and helps you fine-tune the rendering of your apps.

If you have to test the rendered vista hierarchy on real device, you can use the to search and debug. When you sign in to your App Live dashboard, you can upload your app or launch a gimmick session directly. Once inside the session, you can select the UI debugger from the top carte.

• You can test UI rendering on a horde of real devices, instead of relying on faux environments.
• You can record screenshots or video and share them across the team.
• Multiple ways of uploading App; you can also use binaries like .ipa file or download instantly from App store and TestFlight.

Integration with Automated Cloud Testing

For escape your UI exam in an automated set up, consider integrate with the characteristic. It cater simple and easy step to help you extend UI testing in Xcode for iOS. Here are some of the benefits of running cloud-based automation testing:

• You can access many Apple device to run automation scripts on. Although simulated can be used for testing on any kind of device through Xcode, it is forever better to use existent instruments for the best consequence.
• It opens up the possibility for collaboration on the exam scripts and the results of test runs. With the help of platform features you can record and canvas test pass in-depth and share them across your team.
• It is a scale-friendly way of try as BrowserStack go and on-demand resource allocation for your grow motivation.
• It offers enterprise-level data compliance for sensible use case and access management features like individual sign-on to ensure easy control over user access.
• With various third-party desegregation, you can extend this apparatus beyond just essay and create knock-down collaborative workflows.

Related Guides