That's a useful distinction for creating a shared language within Google, and it might be a useful distinction for your team too. But it's definitely not the o

That's a useful distinction for creating a shared language within Google, and it might be a useful distinction for your team too. But it's definitely not the only way to divide things up. The important thing is that the terminology your term uses is useful for your team. One project I'm working on has two kinds of tests: unit tests run within the code and test classes, state transitions, etc. by calling the code directly, while integration tests are run in Selenium in a headless browser from the perspective of the user. Some of the unit tests on models do hit the DB (i.e. they do I/O).