Discussion - When and What to Test

GeekInterview.com > Interview Questions > Testing > Discussion

Go To First | Previous Question | Next Question

Discussion | Question 67 of 72

When and What to Test

How do you determine when and what to test?

Total Answers and Comments: 6

Last Update: August 31, 2009 Asked by: rehman.scorpio

Sponsored Links

Best Rated Answer

—

Submitted by: StevenPace

Test Plan outlines when and what to test, so how to you make the test plan?

Some suggestions and principles:

Test coverage should be risk based, the higher the risk, the more the area should be tested.

Early in the project, bugs have to be removed to enable the testing to procede. Usually certain interface problems make testing impossible.

Give an area testing based on how much work has been done on it lately, then the bugs will be discovered sooner, and hopefully as the work in the area continues, this makes fixing them easier and quicker for the developers. So if you had a list of the source code that has been checked out since the previous build, that would help you decide what to test.

Bugs should be identified before the area is "frozen". If the area is subject to a freeze, the odds are high that the bug won't be fixed. Clearly this is not as useful as finding bugs that will be fixed. The Test Plan would definately take the development schedule into account.

Above answer was rated as good by the following members:
G.D.S.Prasad

July 13, 2008 07:14:03

StevenPace

Member Since: July 2008 Contribution: 32

RE: When and What to Test

Test Plan outlines when and what to test so how to you make the test plan?

Some suggestions and principles:

Test coverage should be risk based the higher the risk the more the area should be tested.

Early in the project bugs have to be removed to enable the testing to procede. Usually certain interface problems make testing impossible.

Give an area testing based on how much work has been done on it lately then the bugs will be discovered sooner and hopefully as the work in the area continues this makes fixing them easier and quicker for the developers. So if you had a list of the source code that has been checked out since the previous build that would help you decide what to test.

Bugs should be identified before the area is "frozen". If the area is subject to a freeze the odds are high that the bug won't be fixed. Clearly this is not as useful as finding bugs that will be fixed. The Test Plan would definately take the development schedule into account.

Is this answer useful? Yes | No

1 0

Overall Rating: +1

September 02, 2008 04:59:55

varsha.bora

Member Since: August 2008 Contribution: 3

RE: When and What to Test

Testing should start early the software devlopment life cycle to reduce the cost. Testing is risk based activity. We can adopt different approached for testing depend upon the aims and goals of project. Experience in testing will definately help to decide what to test.

Is this answer useful? Yes | No

November 20, 2008 08:52:04

laalu

Member Since: November 2008 Contribution: 2

RE: When and What to Test

This a very interesting question. You should detarmine it based on your SDLC and TLC your company is following. This document will make it clear for you.

Is this answer useful? Yes | No

March 21, 2009 03:23:45

mathan_vel

Member Since: December 2007 Contribution: 422

RE: When and What to Test

This should be clearly focused in the Test Plan.
Testing Starts once the "Sanity" is passed and split to the Testers that they are well enough practiced in the requirements.
What to Test also clearly mentioned in the Test pla: Testing Scope Testing Strategy(Testing Type Defined) Testing Schedule.

Is this answer useful? Yes | No

July 23, 2009 08:27:48

srinivasulub1981

Member Since: December 2005 Contribution: 387

RE: When and What to Test

HI

When and what to test will definitely mentioned in the test plan it self...

so one can easily follow the test plan...

Srinivas

Is this answer useful? Yes | No

August 31, 2009 09:19:47

ashishks

Member Since: December 2008 Contribution: 73

RE: When and What to Test

When and what to test is only depends on the following factors:
1. Budget of project.
2. Type of project.
3. Resources available to test.
4. Time available for testing.

So considering above mentioned factors test plan is prepared initially wherein:

under "Schedule and milestones" section "when to test" is mentioned and
under "Test Strategies" section "What to test" is mentioned.

Is this answer useful? Yes | No

Go To Top

User Name		Remember Me?
Password

Question Bank