Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 3
    "In practice, keeping a clear distinction between unit tests and integration tests is not overly important." I agree from the perspective of the textbook testing responsibility of a developer; but there are other considerations here. Integration tests often take longer than unit tests (depending on how rigorous they are and how many cases they test), which for larger projects can be an issue for developers to run locally every so often. It's perfectly acceptable to split the tests so devs run the unit tests and the build pipeline runs unit+integration tests. Commented Mar 27, 2020 at 8:54
  • 1
    @Flater Absolutely! I've previously argued that point as well, but think that “Separating automated integration tests from unit tests is not in itself important, it is just a performance hack to improve your test feedback”. But in this answer, I'm trying to point OP towards doing things that work, without overthinking the official definitions of unit and integration tests. Commented Mar 27, 2020 at 9:33