Comments on: Properties of Good Tests: A-TRIP http://www.cavdar.net/2008/10/25/properties-of-good-tests-a-trip/ Tech, Internet, Engineering and Life Blog Mon, 06 Sep 2010 07:32:10 +0000 http://wordpress.org/?v=2.6.2 By: A blind spot of Continuous Integration « Schneide Blog http://www.cavdar.net/2008/10/25/properties-of-good-tests-a-trip/#comment-215 A blind spot of Continuous Integration « Schneide Blog Mon, 28 Dec 2009 21:34:11 +0000 http://www.cavdar.net/?p=340#comment-215 [...] are rules for good unit tests. A basic set are the A-TRIP rules formulated in the excellent beginner’s book “Pragmatic Unit Testing” by Andy Hunt [...] [...] are rules for good unit tests. A basic set are the A-TRIP rules formulated in the excellent beginner’s book “Pragmatic Unit Testing” by Andy Hunt [...]

]]> By: Azauskas http://www.cavdar.net/2008/10/25/properties-of-good-tests-a-trip/#comment-121 Azauskas Fri, 31 Oct 2008 13:14:46 +0000 http://www.cavdar.net/?p=340#comment-121 Thank you..Viva TDD :) Thank you..Viva TDD :)

]]> By: mstf http://www.cavdar.net/2008/10/25/properties-of-good-tests-a-trip/#comment-116 mstf Sun, 26 Oct 2008 08:18:52 +0000 http://www.cavdar.net/?p=340#comment-116 nice,thanks. from my experiences,i also have some practical advise addition to cetin(especially for C programmers) **unit tests should be written just for public methods, if you need to write test for a private method,check your classes again. **do not forget to test copy constructors TestC1_Method { C1* pInst_c1 = new C1(); //C1 is a class C1* pInst_c2 = new C1(); pInst_c1->DoSomeStateChange; pInst_c2 = pInst_c1; -->everything is fine? delete pInst_c1; pInst_c2->RunYourMethods -->is it ok? } But these are for the cases you have time,if you don't have and your supervisor waits for release,fuck it.just write your code :) cause money is important :) nice,thanks.
from my experiences,i also have some practical advise addition to cetin(especially for C programmers)

**unit tests should be written just for public methods, if you need to write test for a private method,check your classes again.

**do not forget to test copy constructors

TestC1_Method
{
C1* pInst_c1 = new C1(); //C1 is a class
C1* pInst_c2 = new C1();

pInst_c1->DoSomeStateChange;

pInst_c2 = pInst_c1; –>everything is fine?

delete pInst_c1;

pInst_c2->RunYourMethods –>is it ok?
}

But these are for the cases you have time,if you don’t have and your supervisor waits for release,fuck it.just write your code :) cause money is important :)

]]>