Answer / satish kumar.k

To do any task we need a plan and without planning we cant
workout the things in a order.

To test a entire project we need a some planning here test
plan comes into the picture n you can have some better plan
to test the application like what kind of testing should be
good to test this project, how many resources are required,
time allocation and what kind of tools are required and
what the deadlines for this project. And what is the scope
and what approaches should we follow n what kind of
hardware and software required for this project so
everthing will be planned here.

sorry i dont have time now so i just in few sentense, so if
you have doubts contact me at my mail

Answer / sairam

Test Plan Gives an idea about what you are testing and what
is the objective of testing a scenario/feature/build
Test plan gives a complete details to the test engineer who
is executing the test cases. It gives why we need to test
(i.e. the Objective of testing) the tools/ or the setup
needed to execute the test case, it also tells the test
engineer like by when the test case need to be get
completed giving the start date and end date for testing.It
also gives the results like if a test case works fine what
should be the test engineer should do like
Pass/Fail/Block/Not executable.

Answer / vital

Once the requirements of the project are examined, a test plan is created and documented. In this stage the software test plan (STP) document is written. The STP provides the scope of testing , testing approach, required resources,schedule, etc.

Answer / sagar more

A better question is why plan anything? You plan those
things that you know are more complicated than what you can
do by the seat of your pants. You plan things for which
order and completeness are important. Even the simplest
software system is so complex and is so prone to failure,
that planning to test is just as essential as planning your
design.
The second major reason is that, as an industry, we are
doing a lousy job at releasing quality products. Current
industry standards are that tested and released software
averages more than ten significant bugs per 1000 lines of
code. How many hundreds of thousand of lines was that last
project? Thinking ahead and planning your testing is one
way to cut that down.
All of these are good starting reasons for having a
software test plan.

when giving demo to the client. if u found a showstoper defect what you will do.

1 Answers  

---

2. What resources do you use to learn about Web accessibility?

0 Answers  

---

is there any difference between test case design and test case development

3 Answers  

---

is there any openings in testing mba guys

1 Answers  

---

Difference between manual and automation? Explain me test cases?How to write test cases??Give some examples of test cases? is anybody here who has 2 years manual testing experience.. difference between black box and white box testing

2 Answers  

---

1.. what is mean by data base testing and what are the important things you want to check while in database testing ?

1 Answers   IBM,

---

diff b/w waterfall model & spiral model?

14 Answers   APIIT, BBD, QQ, Rift Valley Institute of Science and Technology RVIST, Wipro,

---

what is metrics?...What metrics do u follow in ur company?

6 Answers  

---

Wht is the Difference between Test Harness and Test Driver Anybody can explain it..Thanks in advance...

5 Answers   Siemens,

---

During alpha testing why customer people are invited?

0 Answers  

---

How to test an Scheduled event? For ex: in an investment banking application, the scheduler will create an equity anbd user has nothing to do but tester has to test if the instrument is created properly or not?

0 Answers  

---

we are writing bug report in excel-sheet how you are sending the report to your concern person. (give me the detail work from bug found, where you are storing and how you are sending related to your company)

2 Answers  

---