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.

Suppose " You are given a build with 5 modules to test as per the Customer request after finalization of SRS, But the SRS contains only documentation about 4 modules. On what basis you will continue the testing of 5th module." ?

15 Answers   HCL, TCS,

---

what comments have u given in peer review? tell me at least 3 comments what u have given? july27 brahma412@yahoo.co.in

2 Answers   CTS,

---

which environment you like to work?

3 Answers  

---

i am keeping 2yrs fake experience in banking sector can someone please tel me what kind of questions and answers i have to face

3 Answers  

---

Differentiate verification and validation?

0 Answers  

---

---

Have you done exploratory or specification-driven testing?

1 Answers  

---

wt r the types of testings r belongs to black box testing, wt r the types of testings r belongs to white box testing and wt r the types of testing r belongs to both.

4 Answers  

---

what is the most critical bug u have to find in ur project.My application is ERP based,in this purchase module is there.plz tell me the answer?

0 Answers   Accenture, Value Labs,

---

how cookie and session testing is done ?????

2 Answers   CMC, TCS,

---

What is the difference between test case result and a bug?

5 Answers   Satyam,

---

what is the use of functional specification?

2 Answers  

---

Test Track Pro. Defect report formate? what r the attibutes?

1 Answers   CybAge,

---