When resolving a ACM problem, it's not a good idea to simply write a compilable algorithm and submit to the ACM System in the hope of getting AC (accept ). this way, we re relying on the system to provide some secret test cases to validate the correctiness of the algorithm. and we lose two things:
1. a good chance to train yourself thinking about things completely.
2. efficiency, since it will take you more submit to get pass all test cases.
So, it's important to design our own set of test cases. Here are some basic idea
Sample Test Case provided by the problem
Boundary test case
Random test case
Test case for Large Scale
Trick test case
Tip:
We can call the algorithm twice and compare their output to make sure we don't forget to initialize a variable on the stack. consider the example below, if we run the test case to call the algorithm twice, we can find out the annoying mistake. it's a good way to help use avoid some trivial mistakes.
1 # include "iostream"
2
3 using namespace STD;
4
5 Int Foo ()
6 {
7 int Z; // variable Z is declared without initialization.
8 int A = 13;
9 int r = a + z;
10 z = 35;
11 return R;
12}
13
14 int main ()
15 {
16 int R1 = Foo ();
17 int r2 = Foo ();
17 assert (r1 = R2 );
19}
How to Write test case
In practice, I'm using Google's gtest framework to perform my unit test.