RSS feed [root] /testing /weblog /software_engineering



title search:


Mon Aug 28 19:17:18 HKT 2017


The evil test:

1. Evil tests create a lock on how the code is implemented.
2. Cause duplication.
3. Builds uncertainty on the tests (red is meaningless).
4. Decrease productivity.
5. Discourage change.

use thread in junit -[..]blog/2007/11/05/false-positives-in-junit

Don't try to test everything -[..]ay?entry=unit_testing_avoiding_extremism

Why TDD fail? Because test is too complicate to write - ( I agree it a lot )

Hard to test something? Unreadable tests? Slow running tests? It takes too long to write a test? Some solution suggested -[..]/last-d-in-tdd-means-more-than-just.html

Comment out test so that the code compile -

A list of TDD antipattern -

And the long discussion using random in unittest -[..]rivendevelopment/message/20458?var=1&l=1
Here is an example of using random in unittest, it actually same for every new instance! -

Test abstraction smells -[..]com/2011/11/test-abstraction-smells.html

Basically, we should keep it simple, and driven the development rather than post test -[..]stteam/Posts/13-01-24/top-5-tdd-mistakes

A good list of anti-pattern -[..]2014/05/06/getting-unit-testing-to-fail/
Test rely on shell script return is difficult to maintain, say the script running at background can cause problem -[..]m/2014/01/10/another-shell-test-pitfall/

Six Things That Go Wrong With Discussions About Testing -

(google search) (amazon search)
download zip of files only