como não testar seu projeto de software
Post on 05-Jul-2015
1.429 Views
Preview:
DESCRIPTION
TRANSCRIPT
@dhhI find over-testing to be most common among those 1st adopting TDD. So excited about the idea that they go completely overboard.
Don’t use Cucumber unless you live in the magic kingdom of non-coders-writing-tests (and send me some fairy dust if you are!)
@mfeathers Ultimately, tests are a feedback mechanism, and we should make active decisions about what feedback we need and when.
@unclebobmartin 1 of Kent’s older wise sayings was: “Test everything that could possibly break.” I think that’s a pretty good recipe.
@joshuakerievskyTest first/after misses the point that TDD is more about emergent design than it is about testing. Do you practice emergent design?
@kentbeckIf I don’t typically make a mistake(...), I don’t test for it.
Wish there were more examples of “what not to test”.
@marickI test the high risk code thoroughly. I use up most of the remaining time testing the medium risk code. I don’t intentionally test the low risk code
@martinfowleryou’re doing enough testing if the following is true:■You rarely get bugs that escape
into production■You are rarely hesitant to change
some code for fear it will cause production bugs
Love MetricsDelivered customer benefit?Customers actively using it?
Customers tellings others about it?
top related