3 ms·

Unit Test is the common generic term anymore. So Unit test is most commonly used to refer to any type of test, integration, end to end, or isolation. Most peo

Unit Test is the common generic term anymore. So Unit test is most commonly used to refer to any type of test, integration, end to end, or isolation. Most people will view you as being pedantic and old school for insisting on using an older definition. Which is exactly the feedback I kept running into so I changed my stance on the subject to fit what people expected. At least I got them to make more tests.

hk1337 5y ago
Yeah, I wondered about that too. Lumping it under one term is imprecise. I don’t like that there’s 3 different types of non unit tests, personally I would say pick one and run with it so you’d say we have unit tests and behavior tests for example.
Supermancho 5y ago
> So Unit test is most commonly used to refer to any type of test, integration, end to end, or isolation. Most people will view you as being pedantic and old school for insisting on using an older definition. I understand that anything can be categorized as a unit, even a functional test. That's fine. Transactions for integration tests. I'll suffer the distain of people who rather produce problematic (eventually buggy) software in lieu of understanding categoric differences and purpose, leading to these kinds of "questions". If that's "most people", so be it.
monksy 5y ago
Calling a mix of tests into the category of unit tests is incredibly wrong and misguided. It is a formal term that has been around for a long time and talks about a test that is extremely limited in scope and is tested in isolation.
morpheuskafka 5y ago
The old definition is still how we learned it in undergrad software engineering (taught by the youngest professor in the department, no less) in 2021. Integrating into a database, much less one with simulated real-world data, would be integration or end-to-end testing, definitely not unit. The name unit implies testing a single unit of code, not how everything runs in real world conditions.

hk1337 5y ago

Yeah, I wondered about that too. Lumping it under one term is imprecise. I don’t like that there’s 3 different types of non unit tests, personally I would say pick one and run with it so you’d say we have unit tests and behavior tests for example.

Supermancho 5y ago

> So Unit test is most commonly used to refer to any type of test, integration, end to end, or isolation. Most people will view you as being pedantic and old school for insisting on using an older definition. I understand that anything can be categorized as a unit, even a functional test. That's fine. Transactions for integration tests. I'll suffer the distain of people who rather produce problematic (eventually buggy) software in lieu of understanding categoric differences and purpose, leading to these kinds of "questions". If that's "most people", so be it.

monksy 5y ago

Calling a mix of tests into the category of unit tests is incredibly wrong and misguided. It is a formal term that has been around for a long time and talks about a test that is extremely limited in scope and is tested in isolation.

morpheuskafka 5y ago

The old definition is still how we learned it in undergrad software engineering (taught by the youngest professor in the department, no less) in 2021. Integrating into a database, much less one with simulated real-world data, would be integration or end-to-end testing, definitely not unit. The name unit implies testing a single unit of code, not how everything runs in real world conditions.