something about code coverage planning

This milestone, my lead let me drive code coverage. So I need do a planning about this.

This is my planning email sent to team:

Code Coverage is a good tool to help us get the test coverage status and add test cases according to the code coverage data. We will run two round test passes in Beta. So we`d better collect code coverage data in Test Pass 1 and add new test cases accordingly. This can help us run test cases effectively in Test Pass 2.

Our goal for Test Pass 1 code coverage is to collect all test cases code coverage data of at least one version.

P and E test pass 1 will finish at 12/31,C test pass 1 will finish at 1/22. So the plan is:

· 1/4-1/8 P, E will send out the final code coverage data and analysis report;

· 1/4-1/8 C will send out the P0&P1 test case code coverage data or status report;

·  1/25-1/29 C will send out the final code coverage data and analysis report;

The first code coverage build has been copied to 

Code coverage build will be copied automatically daily and sent to test owner.

Thanks.

Jackie.

Goodness:

1. goal is clear. C has different schedule with P and E, you let C has two report and each for different purpose;

Badness:

1. only contains goal, no action

In fact, when I am executing this planning, I encountered several questions about this:

1. which branch will be used to collect code coverage? [Big Risk]

2. how tester will get the latest build binaries?

3. where is the binary static info stored?

4. when to Start officially , meaning you can talk about this on team meeting

5. when to push tester to do this

转载于:https://www.cnblogs.com/whyandinside/archive/2009/12/18/1627430.html