Quick VS ToBeAutomated

Take this example mentioned in the blog post. It was merged into Quick:main from younata:fix_parallel_tests - until the PR was merged, the code resided in the user younata's profile. That's the point of PRs, right? It can't be merged into Quick unless it passes review and is merged. Therefore, when the (allegedly) Russian user's profile was removed it removed all of the commits on their profile - including anything un-merged. Anything already merged, and thus merged to the Quick project repository, has not been changed.

These tests are responsible for validating that a single unit is working properly. You can think of a unit as a class or function. These tests are written in an isolated fashion. I mean, if the rest of the system is full of bugs and nothing else work, if this unit work, the test will pass. They are also repeatable. They don't depend on anything else, really. Anytime you run the test, if the code hasn't changed, the test will report the same result. These tests are intimately related to the code quality of your project. If your code is clean, these tests should be relatively easy to write. When writing unit tests in iOS, you usually use XCTest or Quick

Well, enough theory for now. I've prepared a quick, small example so you can understand hands-on how all of this work. So, go and clone/download the code in this repo. This is the simplest app you could think of. It's a Counter app, that has a label in the center of the screen, a button to "add" and a button to "sub". As simple as that. A think that could draw your attention is this fragment: