c
 is a document which provides complete details about the resources which are used in a

project. Also describe the scope, approach and other activities which we perform during testing.
It is the responsibility of test lead to develop this document. It contains what things we are going
to test, how we test it, when we test it and who will test it. I would like to mention key elements
of a test plan which we mention when we create a test plan, which are given below.

(1) Test scope and its objectives: Here we mention the objectives of testing a particular module.
(2) Testing Strategy: Here we describe the strategy we used for testing the software.
(3) Deliverables of the test case: What we will get after executing testing.
(4) Test cases: We mention test cases for different modules.
(5) Test Requirements: Here we mention the necessary requirements for tests.
(6) Expected Result: it means that what result we expect after performing testing.
(7) Testing Environment: It means that what will be the software and hardware requirements for
testing the software.

c
 
 It is the job of project manager to develop this document. This document contains
which type of testing technique we will use for testing the software. As there are many types of
software testing which are used in different circumstances for different purposes and it depends
on the situation to choose a particular strategy.

  

is the process of determining the speed or effectiveness of a computer,
network, software program or device. This process can involve quantitative tests done in a lab,
such as measuring the response time or the number of MIPS (millions of instructions per second)
at which a system functions. Qualitative attributes such as reliability, scalability and
interoperability may also be evaluated. Performance testing is often done in conjunction with
stress testing.
Performance testing can verify that a system meets the specifications claimed by its
manufacturer or vendor. The process can compare two or more devices or programs in terms of
parameters such as speed, data transfer rate, bandwidth, throughput, efficiency or reliability.
Performance testing can also be used as a diagnostic aid in locating communications bottlenecks.
Often a system will work much better if a problem is resolved at a single point or in a single
component. For example, even the fastest computer will function poorly on today's Web if the
connection occurs at only 40 to 50 Kbps (kilobits per second).
Slow data transfer rate may be inherent in hardware but can also result from software-related
problems, such as:

 Too many applications running at the same time

 A corrupted file in a Web browser

 A security exploit

 Heavy-handed antivirus software

 The existence of active malware on the hard disk.

Effective performance testing can quickly identify the nature or location of a software-related
performance problem.