Reporting UI Test Results to TestRail

This is a stub for content that will appear in September. References TestRail – https://www.gurock.com/testrail TestsRail API - http://docs.gurock.com/testrail-api2/start XCTest documentation - https://developer.apple.com/documentation/xctest XCUITest User Interface Tests - https://developer.apple.com/documentation/xctest/user_interface_tests

Use the Debugger When Writing XCUITest Code

I prefer to use the debugger built into Xcode, lldb, when learning how to locate elements on the screen. I have the ability to display the elements tree for every screen in my app. From that I can see accessibility identifiers, labels, values for UI elements plus coordinates for each element. From this information, I …

Are Elements Ready for Use?

When writing any UI Test automation it is important to interact with elements on the screen only when they are ready to be interacted with. When navigating to a new screen, you are not guaranteed that all of the screen elements exist and are hittable the very second that test code is executed. This post …

Actionable UI Test Assertions

When writing your XCUITest UI test, it is important to provide enough data when an assertion fails so that someone looking at a test run report can most easily see what failed and begin to figure out the "why".