How to write good test

---

Correctness

1. Doesn’t write depend on known bugs

// DO NOT DO THIS!!!
int square(int x){
	// TODO
	return 0;
}
TEST(SqureTest, MathTest){
	EXPECT_EQ(0, square(2));
}

2. Write Test base on real scenarios

Readability

1. Should be obvious to the future reader

TEST(BigSystemTest, CallIsUnImplemented){
	BigSyste system = Initialize();   // make initialize short by function
	EXCEPT_EQ(42, system.PrivateKey());
}

2. Don’t advanced test framework when it isn’t necessary.
   A test should be like a novel: setup, action, conclusion.

Completeness

1. Test for common inputs, corner cases, outlandish cases:

EXCPECT_EQ(1, Factorial(1));
EXCPECT_EQ(std::numeric_limints::max<int>(), Factorial(13));
EXCPECT_EQ(std::numeric_limints::max<int>(), Factorial(13));

2. Only test the thing your responsible.

Demonstrability

1. Test the API works, do not test private member. (Test the use of consumer. )
2. Test shows how the usage of API

Resilience

1. Don’t write flaky test. (re-run get different result.)
2. Don’t write brittle test. (tests those may fail with unrelated code change.)[hermeticity, order, Deep Dependence]

sleep(1);  // may failure if test timeout is 0.5
---------------------
fopen();  //may fail if multi test read/write a same file. (should be hermeticity)
---------------------
static int i = 0;    // may fail 
TEST(Foo, First){
.....
++i;
}
TEST(Foo, Second){
.....
++i;
}
----------------------