The change we needed to stop fighting unit tests and make them fun.
Use Cases and Deployment Scope
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.
Pros
- Is easy to learn and implement.
- Is faster than others competitors.
- Cool integration with UI Tests.
- Swift Native language.
Cons
- Its only for iOS apps.
- Only Swift and Objective-C language.
- Some stability issues on real devices.
Likelihood to Recommend
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.
