Unit vs Integration testing — what's the difference? | Code Walks 005

Unit testing is to test in isolation, and integration testing is to test in integration. But just how isolated must something be for it to be considered a unit test? Here's my opinion on how far you need to go.

Original upload date:
May 14, 2016

[DiegoOliveiraProf]

liked the walking over the developers cemetery, very relaxing to know the suffering one day will end :')

[juanjosegranda]

The Dependency injection at the end was the most important part for me in the video. Congrats, nice video

[stdiosus]

Good topic to discuss. BTW, there is an ERP from Microsoft, which uses this term "Unit of Work" - it let's us commit multiple changes to DB in one request. :)

[sunnysrivastava]

I liked the concept of walking and talking haha it seems like you are discussing some topic with your friends on the way to the university XD please make outdoor videos more its fun :P

[arvindnaidu]

In your "you wrote" and "they wrote" who is you and they? You = developer/team/company ?

[sebonaccid.]

If you would have one class that you are unit testing and them you extract some logic for readability and using new class logic inside the first one - would you name it integration test? For me it's not. Unit could be a set of classes imo.

[andrejpetrovic]

Look at the home boy, talking about the testing and just casually walking by the graveyard. Is there some subliminal messaging in that or

[zerosandones]

So, when I test my repository, I'll consider this as an integration test:

// C# with Entity Framework
public context)
{
_context = context;
}

[braydonbudde]

I could not focus with the sound of the footsteps and the abundance of short redundant scene breaks.

[jeffpeng]

integrate, this reminds me of calculus

[trailblazer_nomad]

Unit Testing and Integration Testing From a

[bartholomewtott]

Wrong!! A unit test does not require complete isolation. Think about that. No tests can be completely isolated.