hi 
this is jp.pls any one can help to me

2.
PERFOMANCE TESTING:response times, transaction rates, and 
other time sensitive requirements are measured and 
evaluated. implemented and executed to profile and tune a 
target-of-test's performance behaviors as a function of 
conditions such as workload or hardware configurations.

Load Testing:Load testing is a performance test which 
subjects the target-of-test to varying workloads to measure 
and evaluate the performance behaviors and ability of the 
target-of-test to continue to function properly under these 
different workloads.   The goal of load testing is to 
determine and ensure that the system functions properly 
beyond the expected maximum workload.  Additionally, load 
testing evaluates the performance characteristics  
(response times, transaction rates, and other time 
sensitive issues).

Stress Testing: Stress testing is a type of performance 
test implemented and executed to find errors due to low 
resources or competition for resources. Low memory or disk 
space may reveal defects in the target-of-test that aren't 
apparent under normal conditions. Other defects might 
results from competition for shared resource like database 
locks or network bandwidth. Stress testing can also be used 
to identify the peak workload the target-of-test can handle

Volume Testing: It subjects the target-of-test to large 
amounts of data to determine if limits are reached that 
cause the software to fail.  Volume testing also identifies 
the continuous maximum load or volume the target-of-test 
can handle for a given period.  For example, if the target-
of-test is processing a set of database records to generate 
a report, a Volume Test would use a large test database and 
check that the software behaved normally and produced the 
correct report

4.
defect: deviation from the requirements
bug : conceptually same as defect. technical people use 
this word
error:mistake associated with the program that cause defect

1) System Testing- it's end to end testing. Testing based 
on the SRS and FS documents. Validation process
 both functional and non-functionality testing carried out.
 UAT- it's Acceptance testing. TEsting based on BRS 
document. Verification process. Alpha and BETA testing 
carried out.

2)Performance testing- we check the response time of the 
application
load- on different work load, how the system will perform
stress-beyand the limit of load how the system will 
response.

3)Integaration Testing-integarate all the module by top-
down or bottom-up approach. 
 System testing-complete end -to - end testing not only in 
the integarated module including database,network 
connectivity etc.
after integaration testing we perform system testing

4)Defect- founded by tester, mismatch between expected and 
actual result.
Bug- Once tester place defect in the defect tracking system 
it's called bug.

5)use case- it's a document, details about how the user 
interact with application 
fields are- Usecase ID, DEscription, trigeer, extected 
result.
TEst CAse- From Usecase and TRM we prepare the test case.
test case it's for particular condition.
fields are - testcase id,procedure,expected result, actual 
result.

6)Test Plan- it's a document it have scope, approach and 
entry and exit criteria,requirements details etc.
how to test.
test strategy-what to test, what r the approach neef to 
result.

7_test scenario- it's a complete details about one 
transaction. here we specify the test condtion
test case- it's complete details about partic;ar confiyion.

9) client and server
  client- work as a dump terminals.
  by useing client we do input and output
  Server: all the data's stored on and rhe processing   
  take place.

10)  Test case template is a step by step description of 
the action we do to test the application. Test case 
template consists of step#, description of the step, 
expected results and actual results.

11)   Test plan template is consists of the objective,scope 
and the schedule of the testing and what is assigned to who.

12)Testing process - Analyzing the requirements
                     Creating the test scenario,
                     Creating the test plan,
                     Prepraing the test cases,
                     executing the test cases,
                     Login the defects,
                     Tracking until defects are resolved.

13) Bug report template consist of 
    bug ID, test case ID, test scenario Id, description of 
the bug, name of the tester, name of the assigned 
developer, Priority level, expected results, actual 
results, status of the bug i.e new, open, closed.

14)Scenario is set of test cases.

15)Criteria is how well the application is working with out 
any defects. This is decided by both client and the testing 
manager.
Entry criteria- Means is the application testable, is the 
environment ready to the testing. How long the testing is 
going to take.
Exit criteria- This is defined by the client like 
application should be delivered to the client with 0 high 
level bugs, 0 severity bugs, 0 medium bugs, and 1 or 2 
small bugs.
20) Stress testing- Testing the application under heavy load
    sanity testing - Testing whether the build is ready of 
the approaching the test.

23) Boundry value- Min and max lenght of the fields

24) Equivalence value- is to check the valid and invalid 
data of the field.