T-CRFPFiorenzo PelosoSystem Test PlanSystem Test Plancobas IT 5000Maintenance Release2.02.0110082298 
Document	ID - Nummer		Version: 	0	
	Filename		
	
	Project Role	Name	Department	Signature	Date	
Creation	Test Manager					

Review & Approval	QA					

Changes	Version	Name	Reason for Change	Date	
	00		First Version		

		

1 Purpose	3
2 Scope	3
3 System Description	3
4 Acceptance Criteria	3
5 Test Procedure	3
5.1 Test Strategy	3
5.2 Test Intensity	3
6 Resources	4
7 Test Environment	4
7.1 Computer Systems	4
7.2 Interfaces	5
7.3 Measuring equipment	5
8 Test Case List	5
9 References	6

1	
Purpose
This document describes the implementation of the system verification and validation according the strategy outlined and defined in the validation section of the Product Change Order (PCO) document. It includes all the information necessary to plan and control the test effort for the given system. 

2	Scope
This test plan relates to the following System (i.e. object under test):

System Name	… product…	
System Version	xx.xx.xx	
Test Run	3	

The tested version is labeled xxxx.

3	System Description
Please refer to corresponding PCO (Ref. [1]).

4	Acceptance Criteria
In general, a test case is "PASSED" when the real outcome corresponds to the expected outcome, otherwise the test case is marked as “FAILED”. Expected outcomes are defined separately in each test case.
•	a 100% test coverage is required (i.e. all implemented changes need to be tested at least once)
•	no critical defects are tolerated 

5	Test Procedure
5.1	Test Strategy 
According to the impact analysis of development of made fixes a specific test set is defined for this test run.
At least 100% of failed test cases will be retested.

In addition to the system validation, localized GUI masks are validated in an individual process.

5.2	Test Intensity
The criticality of any test case is rated, documented and printed with each test case document.
A 100% requirement coverage is needed, that means that there is in minimum one test case per specification.

Test Intensity	Test Case Types applied	
Extended	-	Valid Input Tests (generate at least 1 possible output or event using valid inputs)
Plus one or more of the following approaches:
-	Verifying boundary values for each parameter;
o	Entering an invalid value for each parameter;
o	Special input values: 0, negative numbers, wrong format, accented characters, empty fields, extremely high or low values;
-	Try as much as possible not allowed user actions or events
-	Interfering/Interrupting events or user actions outside the specified behavior, e.g. removing cables, closing browser window, pushing buttons several times, removing instrument during data transfer, time-outs, parallel browser sessions, etc.
-	Error Guessing	
Standard	-	Valid Input Tests (generate at least 1 possible output or event using valid inputs)	

6	Resources
Role	Responsibility	Persons	
Test Manager	-	coordination of design verification & validation
-	management of resources for validation		
Test Designer	-	definition of test cases
-	supervision of the testing and validation activities		
Group of Testers	-	execution of test cases
-	reporting of test results		

7	Test Environment
In order to successfully and reproducibly conduct the technical validation the following provisions and preconditions have to be established:
7.1	Computer Systems
Test computer systems	Product Server	Product Client	
		Windows Client	WebCard Client	
Operation System	Windows XP MUI	Windows XP MUI	Windows OS, MS Internet Explorer 6.x	
Test Engine	“test-server” (T-CR developer network), Pentium 4, 3.00 GHz, 1 GB RAM, 2 x HD á 75 GB	Test Clients, VMWare Workstation on each test work place; 500 MB RAM	MS Internet Explorer 6.x	
Standard System Test Computer Equipment

Server Name	IP-Address	Version/Configuration*)	

Test computer systems	Citrix Presentation Server on
Product Client	Product Client using 
Citrix Access Platform	
		Windows Client	WebCard Client	
Operation System	Windows 2003 MUI	According Citrix specification	
Test Engine	“test-server; Pentium 4, 2.80 GHz, 1 GB RAM, 2 x HD á 75 GB	Test Clients, VMWare Workstation on each test work place; Windows XP, 500 MB RAM	
Citrix Solutions System Test Computer Equipment 

Server Name	IP-Address	Version/Configuration*)	

			
			
With dump: realistic test data is imported into the DBMS.

Client  Name	IP-Address	Version/Configuration*)	

The different configurations of the test servers are necessary to match the requirements for individual test cases. Test cases that require realistic test data should be applied on the product-Test1 server.
All servers use the the identical installation EXE.

7.2	Interfaces
•	Nport-Server
7.3	Measuring equipment
•	Configured barcode scanner.

8	Test Case List
Test Cases are printed as PDF documents (System Test Case Definitions). A print of each approved System Test Case Definitions document is provided to the test person assigned to carry out the tests. This document is then used to carry out the results and record the specific system test.

The table below lists the entire System Test Case Definitions documents approved and used for system testing ([2]).

Test Def. ID	Test Case Document 	Remark 	
Product version…			

9	References
Ref.	Title	ID-Number	Version	
1	Product Change Order (PCO)		0	
2	System Test Cases	10082299 RER	0