I would like to translate your post to portuguese and post it on our website, because I have a few coleagues that aren't comfortable reading in english and would benefit from your post. Can I do it?
I really like the managers attitude. I wish people would customize to help people with various skills and experience insead of assuming that one set of instructions will get us similar results. This note is really about master understanding his people.
I guess it is a nice way to let people understand about the code coverage. Or any other question.
I guess this is about the attibute of a person how we react in our day to day job.
Regarding the Code Coverage. I guess the first answer was quite important. Just try to concentrate on writing the good test, instead of worring about the coverage. It is important to dissuss those test with bussiness, through that a person should be able to figure out the coverage achieved in the test.
This story has earned me huge amount of repu points on StackOverflow: http://stackoverflow.com/questions/90002/what-is-a-reasonable-code-coverage-for-unit-tests-and-why/90021#90021
It remains to be one of the most excellent answers to the code coverage issue.
Interesting post! Testing is a huge subject hence is subjective per se! What I aim to do mostly in my development work is to test enough for the system to pass functional and non functional requirements as required in the SRS...and more details can follow.
I think our industry would benefit to have more of the first two people and a whole lot less of the third.
返信削除Is this about developers or testers? The story is nice though. But again it looks like the testing is only scripting in your place.
返信削除I would say to the experienced dev:
返信削除"Aim for an increasing trend in code coverage"
The Way of Testivus is the best thing I've seen in a long time. Well done.
返信削除The story is definitely not just about code coverage :)
返信削除We need great master...........
返信削除Just give the consultant answer, "It depends..." :)
返信削除Hope that I have a great master who can drink some tea with me. ;)
返信削除We need more great masters
返信削除Basharat
very cool. Thanks for sharing!
返信削除Interesting!
返信削除Dear Alberto,
返信削除I would like to translate your post to portuguese and post it on our website, because I have a few coleagues that aren't comfortable reading in english and would benefit from your post. Can I do it?
Respectfuly,
Júlio
I really like the managers attitude. I wish people would customize to help people with various skills and experience insead of assuming that one set of instructions will get us similar results. This note is really about master understanding his people.
返信削除Cool...Master
返信削除I guess it is a nice way to let people understand about the code coverage. Or any other question.
I guess this is about the attibute of a person how we react in our day to day job.
Regarding the Code Coverage. I guess the first answer was quite important. Just try to concentrate on writing the good test, instead of worring about the coverage. It is important to dissuss those test with bussiness, through that a person should be able to figure out the coverage achieved in the test.
But nice and cool approach. :)
Really nice story! Perfect introduction to code coverage for developers and project managers in particular!
返信削除>I would like to translate your post to portuguese and post it on our website ... Can I do it?<
返信削除Hi Julio, no problem. I'd love to see Testivus in Portuguese or any other language. Thanks, Alberto
このコメントは投稿者によって削除されました。
返信削除Look into T.D.D., XUnit, and other pre-cog code coverage methodologies that inherently strive for 100% coverage.
返信削除This story has earned me huge amount of repu points on StackOverflow: http://stackoverflow.com/questions/90002/what-is-a-reasonable-code-coverage-for-unit-tests-and-why/90021#90021
返信削除It remains to be one of the most excellent answers to the code coverage issue.
Great story! Love it!
返信削除Published a german translation here: http://itscertainlyuncertain.blogspot.de/2013/01/testivus-zum-thema-test-coverage.html
100% only! Otherwise people getting squeezed for time will cover getters and setters and leave the tasty stuff.
返信削除Interesting post!
返信削除Testing is a huge subject hence is subjective per se! What I aim to do mostly in my development work is to test enough for the system to pass functional and non functional requirements as required in the SRS...and more details can follow.