i think as per my knowledge Incident reports are not 
included in Test Plan. actually Test plan conatins:-
1)Test Plan Identifier
2)Introduction
3)Test Items
4)features to be tested
5)Features not to be tested
6)test Approach
7)items pass/Fail Criteria
  i)Entry criteria
  ii)Exit Criteria
8)Suspension Criteria
9)test Deliverables
10)Environment
   i)technologies
   ii)Languages
   iii)Software
11)roles & responsibilities
12)Staffing & Training Needs
13)Schedule
14)Risks,Contingencies and Assumptions
15)Approvals

Please Inform me If Any Thing Wrong.
uday
uday_testing@yahoo.co.in

2) Incident reports

The option is 2)Incident reports is not included in test 
plan

hai uday .this is sunithayagnamurthy.she is asking what is 
difference between wht is compayability and system 
testing.........
compatability testing means
it is verify look and feel
the color is good or not etc
system testing: means it is like blockbox testing 
to verify the functionality is working according to the 
customer requirment this is system testing......
if any mistajes is thr please excuse

Incident reports

To include:
Features to be tested since some of them can be test at 
rela time for some of them we can test using simulator.if 
we give them what we r testing then at other end they can 
arrange for other cases.and also some internal features 
also we cant test just like internal memory or addresses.
so its mandatory to include it.

Risks: here we might be saying some risks like environmenmt 
supports or operating systems we using,language dependent 
issues.
assumptions and constraints also we can include in test 
plan.
schedule: conveying them about our flow of testing which 
means first we perform GUI testing,fucntionality 
testing,integration and system.
But incident reports is not necessary.Because we would be 
updating our test plan usually.
So if we are facing incident then we need to analyse it and 
add it to the test plan by adding either in risky 
section,constraint section..incase if it can be overcome by 
any other testing methodology then we can add those in our 
testing technoque

Compatibility testing is not look and feel, it is
applications compatibility with the computing environment
(hardware, network, OS, Database, borwsers, etc)

Look and feel means usability testing.

Incident reports