
Anytime you run the test, if the code hasn't changed, the test will report the same result. They don't depend on anything else, really. I mean, if the rest of the system is full of bugs and nothing else work, if this unit work, the test will pass. These tests are written in an isolated fashion. You can think of a unit as a class or function.

These tests are responsible for validating that a single unit is working properly. Let's first distinguish briefly among the different types of automated tests. I've done Unit tests many many times, but I've never written so many UI tests.Īppium, WebdriverIO and Jasmine are the tools this team has chosen to write these tests, and for good reasons. I've never done that before, I have to confess. In the team I'm now taking part of, everyone is responsible for writing e2e tests for iOS/Android/Web. However, I started working in a new project something like a month ago.

I normally write posts explaining things I've been doing in a daily basis for many years.
