Create some automated builds and tests.

[Robert Massaioli]

We need to be able to tell that the code works as we expect. Create some test cases to meet the needs of our users. Some things that would work well as automated tests:

• Different Database test cases.
• Fundamental base code.

[Robert Massaioli]

I shall comment on the places that can use some good test cases over time:

• HTTP Messages Code. We should test our parsing abilities so that we know we are doing it right.
• Common.h We should test all of the common code. Every single file in there should be robust and reuseable.

[Robert Massaioli]

Fuppes already has some test cases inside it. Take a good look at them and work out how to keep everything from them.

[Robert Massaioli]

I have decided that I am going to get a test framwork setup as early as possible and just make it common practice to test my changes.

[Robert Massaioli]

Turns out that boost has a test module. I am setting up the code to use boost::test.