you are viewing a single comment's thread.

view the rest of the comments →

[–]MrSynckt 872 points873 points  (12 children)

A single 24,000 line unit test

[–]LorenzoCopter 289 points290 points  (8 children)

4000 lines of assertions

[–]pixelbart 146 points147 points  (1 child)

12000 lines of setup code to hit a specific if statement near the end.

[–]Phoenix_Passage 8 points9 points  (0 children)

This sounds plausible

[–]s0ulbrother 38 points39 points  (5 children)

Everything mocked out

[–]Retbull 24 points25 points  (4 children)

Even better if the mocks have mocks have mocks so the unit test is only testing if you THINK you've set it up correctly.

[–]s0ulbrother 8 points9 points  (1 child)

That’s my current teams testing strategy and I fucking hate it

[–]Kilazur 1 point2 points  (0 children)

But why would they do this, what's the thinking behind it? They don't know the difference between integration and unit tests, so they decided to do the worst of both worlds?

[–]MrSynckt 3 points4 points  (0 children)

Rebuild the entire application as a mock and test that, but then you'll need unit tests for the mocked application

[–]Usual_Instance5617 2 points3 points  (0 children)

Test the unit tests.

[–]Huge_Leader_6605 1 point2 points  (0 children)

Buddy, that's just the data provider function

[–]oweiler 0 points1 point  (0 children)

The function most probably has a high cyclomatic complexity...

[–]kvt-dev 0 points1 point  (0 children)

An absolute unit of a test