2007-Sep-4 - Risk of building test automation framework

is that it is not fully tested.

We spend most of the time thinking how to automate more cases. We spend the last minute coding on our automation tool to cover one more case. There's no time for us to test our program, and we have to use this quality-unknown thing to test our real product. Isn't it a BIG risk added on the product and schedule?

If we do this test automation framework again, I think we must have a clear plan. And one phase must be included in the plan is the CODE FREEZE and start TESTING phase. During this phase, no more features added to the framework, no more test cases covered, no matter how easy it seems. During this phase, the most important thing is to test whether it will give a PASS when ALL the inputs are correct, and a FAIL when ONE of the input is wrong.