In the last post on DRY XCUITest with Base classes, we have abstracted our code in the base classes in order to avoid the duplication of the code. We have achieved this using the object-oriented inheritance approach. However, Swift is a protocol-oriented language, and we will see how we can use Swift protocols and extension to make our XCUITests more human readable. We will apply Behaviour-Driven Development a.k.a BDD in the methodology for our XCUITest.
In our previous post on setting up XCUITest framework, we got up and running with a sample XCUITest with Xcode 10. Apple’s XCUITest framework gives us an ability to record the basic user journeys to get started with XCUITest, but the recorded tests are not scalable and reusable. We have to take efforts to make the XCUITest more readable, scalable, maintainable and reusable.
Apple announced the Xcode UI Testing framework in WWDC 2015 that allows us to write user interface tests for iOS apps using Swift or Objective-C. The only option remained to automate iOS apps is the XCUITest framework. Since iOS 10, there is a growing trend of iOS teams adopting XCUITest and deprecating old toolbox. In this short post, we will explore steps to get started with XCUITest to automate iOS app testing with the latest Xcode 10.
Apple released iOS 12 just in time after announcing three new iPhones. The new iOS version has a rich set of features in terms of performance and user experience and comes with huge enhancements in performance, security and privacy. Whilst considering these new features for users, we also need to consider what this release means to every iOS developer and QA engineer. In this post, we will explore some major development and testing considerations for Apple’s new operating system.
2017 was another exciting year for Bitbar. We introduced powerful new features and teamed up with new partners to strengthen our mobile DevOps platform. ‘Speed’ is the single word to be used to wrap up the achievements for the year. We want to take this opportunity to have an annual review.
At Bitbar, we always push the boundaries of agility and quality by providing organizations with the most stable and scalable testing solution for mobile apps. In order to bring you the best iOS development and testing experience, we will perform an iOS environment upgrade and add iOS 11 devices to our Cloud on September 13th.
Happy Summer! Sadly there are about 6 weeks left till autumn 🙁
Last month we heard about iOS 11 and boy there were some good announcements! By now most of you know that when WWDC rolls around it’s a scramble to make sure your team is prepared for the changes in iOS app development and testing. Today I wanted to highlight some of the big changes that are coming and how they will probably influence your iOS app development and testing.
It’s quite common in mobile app testing that application and test script with a test session needs an access to various locations. For example, some test scripts need to access URLs, databases, back-end servers or even App Stores (e.g. Google Play or Apple App Store). With the access, test session can get, download or update certain applications from app stores before the actual test session will begin.
In this blog, we’ll take a look of how Appium test script can access Apple App Store and how to use certain XCUIElement components to assist your script with that.
Thank you all for attending our latest webinar – Getting Started with XCTest/XCUITest for iOS App Testing. Although XCTest/XCUITest is not new to iOS developers, it is one of the hottest open source test automation framework for iOS app testing.
There are very few test automation frameworks that are tightly coupled with the development tool itself. XCTest framework is one of those frameworks that enable its users to write basic unit, performance and some level of UI tests for iOS apps.