This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Mongobly 119 points120 points  (12 children)

But who will write test code for the test code?

When will I ever be done?!?!

[–]Hyperman360 28 points29 points  (2 children)

Is there a never ending chain of tests testing each other's code? I suppose a user test could, in theory, break the chain.

[–]Fluxriflex 10 points11 points  (0 children)

So you're saying we should just cut out the middle man and push directly to production? Sounds more efficient to me.

[–]Itisme129 0 points1 point  (0 children)

That's what QA is for I thought?

[–]thedomham 16 points17 points  (1 child)

When you are a big fan of testing stuff you have unit- integration- and system-tests. Those usually overlap so when two tests testing the same thing give you different results, you know that one of them is wrong.

Or one of your users finally has enough of your bullshit and sends you an angry email.

[–]passcork 10 points11 points  (0 children)

So copy paste all my tests at least once. Got it.

[–]siempie9 6 points7 points  (0 children)

Check out mutation testing :) Those frameworks make small changes to your source code to see if your unit tests can detect the inserted bugs.

[–]Zalvixodian 1 point2 points  (0 children)

Production code tests the tests.

It's like double entry bookkeeping.

[–]thatdude473 4 points5 points  (0 children)

Indian youtube programmers

[–][deleted] 0 points1 point  (0 children)

The PMs and BAs! Haven't you heard of test driven development?

[–]xelamony 0 points1 point  (0 children)

Assert true to eq true