How keep track of Test cases and Testing done by the testers

Believe in doing the right thing the first time...

Start creating the test wares based on the flow charts (or activity diagram) of the module you wish to test...

This flowchart must be approved by the R&D counterparts.

It is also recommended that you create an integration map of the module with other related modules. This will help you to develop the integration cases. So once you receive the release notes with a bug fix,you know which all integration cases you need to execute.

Traceability matrix is a very useful tool in case you need to keep track that none of the requirements are missed out while writing cases. The flow chart will ensure that none of the paths/scenarios are skipped out.

Maintain the cases in excel so that you can use formulas to track the cases written/executed and even the pass/fail statistics easily... Some of the useful columns for tracking purposes are date of execution,defect id (for failed cases), Requirement number, Test case id

Relation between KLOC & Test cases

KLOC means Kilo Lines of Code means 1000 Lines of Code

so KLOC = 1000 LOC
10 LOC = 1 FP ( Functional Point)
we can design 3 test cases from each Functional Point

1 FP = 3 TC ( Test Case )

1000
------- = 100 FP
10

so 1 KLOC = 100 * 3 = 300 Test Cases ( we can write approximately ....this is according to my comp test metrics )