The change we needed to stop fighting unit tests and make them fun.
December 20, 2022

The change we needed to stop fighting unit tests and make them fun.

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with XCTest

Im a Fullstack Mobile developer, I usually make Android apps, but I have experience with Swift, Objective-C, and iOS; XCTest has been really useful for Unit Testing for those platforms and languages. Before the use of XCTest, we had a lot of issues when we changed or made refactors on the code, and we needed to stop to fix all of those issues, but since we added XCTest, we don't need to worry about that, because XCTest will tell us what was broken.
  • Is easy to learn and implement.
  • Is faster than others competitors.
  • Cool integration with UI Tests.
  • Swift Native language.
  • Its only for iOS apps.
  • Only Swift and Objective-C language.
  • Some stability issues on real devices.
  • Native iOS languages.
  • Continuos integration support.
  • Easy to understand and install if you have iOS experience.
  • Faster way to know which issues appeared and fixed it.
  • Easy way to install and teach to the programmers.
  • More time invested on the project to implement.
We used Appium to do unit testing, but we felt that it was slow and had its own learning curve, so we decided to try XCTest; it seemed faster and more agile to use because we already had knowledge of iOS and the other advantages that I talk before, now all the team is using XCTest.

Do you think XCTest delivers good value for the price?


Are you happy with XCTest's feature set?


Did XCTest live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of XCTest go as expected?


Would you buy XCTest again?


It is very useful to add it mainly at the beginning of the app when each feature is finished and if the greatest importance of the app is its stability and a quick way to fix errors that are made during the changes. Do it when the app is finished; it's going to be quite time-consuming; however, applying it will go a long way in making sure the code hasn't been broken by changes and improvements.