The big difference with `tests/` is that they *have* to be integration tests. Th... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		tyoverby on Nov 22, 2016 \| parent \| context \| favorite \| on: Sccache, Mozilla’s distributed compiler cache, now... The big difference with `tests/` is that they have to be integration tests. This means that you can't test private functions from there.

Manishearth on Nov 22, 2016 [–]

Not .. exactly. An integration test usually tests an entire application at once. `tests/` can still test things in the public API (indeed, we do this in Servo a lot) without being an integration test.

The point is that some unit tests cannot be written in tests/, whereas all integration tests can be.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact