- Last edited February 18, 2003 |
At least that's what seems to happen. Some integration tests...
1) Two classes being tested together.
2) Three classes being tested together.
3) Testing with real test data.
4) Testing the whole application actually starts (fingers crossed).
5) Testing performance.
6) Testing multithreaded bits.
7) Anything with I/O.
8) Does it look nice?
9) Testing use cases actually work.
10) Check-in didn't break anything (fingers crossed on both hands).
11) Other stuff.
12) Something done on the integration machine.
Techniques to test all of these things vary from unit test harnesses to full dress rehearsals with dummy data. I am not yet sure how to split them up. - MarcuS
- Last edited February 18, 2003 |