Binita

• Oct 15th, 2006

 

Test coverage can be measured when Test cases are completed with certain percentage passed.

Common factors in deciding when to stop testing are:

Deadlines (release deadlines, testing deadlines, etc.)

Test cases completed with certain percentage passed

Test budget depleted

Coverage of code/functionality/requirements reaches a specified point

Bug rate falls below a certain level

Beta or alpha testing period ends

G.D.S.Prasad

 Profile Answers by G.D.S.Prasad Questions by G.D.S.Prasad

• Dec 18th, 2006

 

Hi,

Test coverage is mesured by using RTM(Requirement Treceability Matrix).

Common factors in deciding when to stop are:

• Deadlines (release deadlines, testing deadlines, etc.)
• Test cases completed with certain percentage passed
• Test budget depleted
• Coverage of code/functionality/requirements reaches a specified point
• Bug rate falls below a certain level
• Beta or alpha testing period ends.

Regards

Prasad 

vk1978

 Profile Answers by vk1978 Questions by vk1978

• Apr 17th, 2009

 

Through Traceability Matrix we can measure the test coverage.

In Test Plan, Exit Criteria specified when to stop testing

1) During the build release If Bug ratio comes down and there were zero critical and medium bugs

2) 100 % coverage is over as per the Test case document or Traceability Matrix

3) As per the Release Date mention in the agreement with client

4) Out of budget

5) When managers says stop testing

6) Alpha or beta testing is over

 

quality_guy

 Profile Answers by quality_guy 

• Oct 23rd, 2009

 

1) When the number of test cases are covered and how many passed and failed.
2) Bug flow rate is low or zero.
3) When more time is taken and its beyond the dead line.
4) More budget is consuming than what is planned.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 30th, 2009

 

Estimating the number of blackbox test cases:

# blackbox test cases =
[usecases x steps x rules]+[GUI‘s x objects x states]+[tables x tuples x instances]

Metrics for measuring test case coverage:

Requirements coverage =
tested requirements / specified requirements

Architectural coverage =
tested architectural features / architectural features

Code coverage =
tested statements, branches, paths, states  / statements, branches, paths, states

Test case coverage =
Executed test cases / specified test cases

When to stop testing:

Stop testing when you've thoroughly tested all requirements and are satisfied with your architectural and code coverage.