Download Acceptance Test Plan

ProCom@MDH
Acceptance Test Plan
Version 0.1
Doc. No.:
Project Name: ProCom@MDH
Acceptance Test Plan
Version:
0.1.0
Date: 2009-11-25
Revision History
Date
Version
Description
Author
2009-11-25
0.01
Initial Draft
MA, IA
2009-12-11
0.5
Updated with changes in some sections of
paper
PG
Page 3
Project Name: ProCom@MDH
Acceptance Test Plan
Version:
0.1.0
Date: 2009-11-25
Table of Contents
1.
Introduction
6
1.1
1.2
1.3
1.4
Purpose of this document
Intended Audience
Customer Scope
Definitions and acronyms
1.4.1 Definitions
1.4.2 Acronyms and abbreviations
1.5 References
6
6
6
6
6
6
6
2.
Test-plan introduction
6
3.
Test items
7
4.
Features to be tested
7
5.
Features not to be tested
7
6.
Approach
8
6.1
8
7.
Approach to configuration and installation
Item pass/fail criteria
8
7.1
7.2
8
8
Installation and Configuration
Documentation problems
8.
Suspension criteria and resumption requirements
8
9.
Environmental needs
8
9.1
9.2
8
9
Hardware
Software
Eclipse 3.4 with Progress IDE and code generator plug-in must be installed on the machine with JDK
1.6 or higher in order to run the project.
9.3
10.
Other
Test procedure
10.1
Test case specifications
10.1.1 Generate Code –ProCom001
10.1.2 View Code – ProCom-002
10.1.3 Compile Code – ProCom-003
10.1.4 ProSys Composite Subsystem Code generation – ProCom-004
10.1.5 ProSys Subsystem Code generation – ProCom-005
10.1.6 Primitive ProSave Component Code generation – ProCom-006
10.1.7 ProSave CompositeComponent Code generation – ProCom-007
10.1.8 Input Message Port Code generation – ProCom-009
10.1.9 Output Message Port Code generation – ProCom-010
10.1.10
Message Channel Code generation – ProCom-011
10.1.11
Connector(s) Code generation – ProCom-012
10.1.12
Connection(s) Code generation – ProCom-012
10.1.13
ProSys Clock Code generation – ProCom-012
10.2
Test plan
9
9
9
9
9
9
10
10
12
12
13
13
14
15
15
17
17
19
Page 4
Project Name: ProCom@MDH
Acceptance Test Plan
11.
Responsibilities
11.1
11.2
Version:
0.1.0
Date: 2009-11-25
19
Developers
User representative
19
19
12.
Risks and contingencies
19
13.
Approvals
19
Page 5
Project Name: ProCom@MDH
Acceptance Test Plan
1.
Version:
0.1.0
Date: 2009-11-25
Introduction
1.1
Purpose of this document
The overall purpose of this document is to ensure the ProCom@MDH application performs at an acceptable
level for the customer. This document outlines the detailed plan for user acceptance testing of this application
according to the requirement specification describe in requirement document.
1.2
Intended Audience
The intended audience is:

PROCOM@MDH team members
 Steering group
 Customer
1.3
Customer Scope
This document’s scope is the testing of implementation and fulfillment of the requirements for ProCom@MDH.
The document doesn’t handle the testing for XML validation , it assume that input XML file is correct.
1.4
Definitions and acronyms
1.4.1
Definitions
Keyword
ProgressIDE
PROGRESS
Executable Code
ProCom plug-in
ProCom@MDH
1.4.2
Definitions
The IDE which enables user to model the embedded system using the
ProCom Component model.
Research project at MDH
A Java (preferred) or C code for ProCom model
ProCom model-driven code generation
ProCom model-driven code generation
Acronyms and abbreviations
Acronym or
abbreviation
ProCom model
MDH
XML
ProCom model
Definitions
the Progress Component Model
Mälardalen University
Extensible Markup Language, language for storing information
the Progress Component Model
1.5
References
1. Requirement document.
2.
Test-plan introduction
The PROCOM@MDH code generator has been based on RCP so it relies heavily on XML file provided by the
Progress IDE. So, first part of testing is code generation testing, and second is classic code view and code
compilation scenario testing.
.
Page 6
Project Name: ProCom@MDH
Acceptance Test Plan
3.
Version:
0.1.0
Date: 2009-11-25
Test items
PROCOM@MDH is an Eclipse plug-in based on GMF, so there are two main parts that need to be tested:
 PROCOM model which served as a starting point for generating base code
 User-related functionality and application behavior which is result of changes made in base code.
4.
Features to be tested
The Acceptance test assumes that all other tests are satisfactory. This test will cover the following.
o The Functional Requirements as defined in the Requirements Document
o Usability of the system
o The non-functional requirements defined in the Requirements Document
o XML file Selection for code generation
o Code generation for selected XML file and storage of code to selected folder.
o Plug-in feature of system by plug-in testing with PROGRESSIDE
o View code generated by system.
o Code compilation of the code generated by PROCOM code generator.
The functionality that will be tested are the requirements listed below:
Identity
Status
Priority
PCT1
PCT2
PCT3
PCT4
PCT5
PCT6
PCT7
PCT8
PCT9
PCT10
PCT16
PCT17
I
I
I
I
I
I
I
I
I
I
I
I
1
1
1
1
1
1
1
1
1
1
1
2
ProCom Model transformation
Code Generation for the Primitive Subsystem
Code generation for the Composite Subsystem
Code Generation for the Primitive ProSave Component
Code Generation for the ProSave CompositeComponent
Code Generation for the Connection Subsystem
Code Generation for the Input Message port
Code Generation for the Output Message port
Code Generation for the Message Channel
Code Generation for the Connection(s)
Code Generations for the Connector(s)
Code Generation for ProSave Clock
Compilation of the generated code
GCG1
GCG2
GCG6
I
I
I
1
1
2
Glue Code Generation
Glue Code Generation for the Primitive Subsystem
Glue Code generation for the Composite Subsystem
Compilation of the generated glue code
PID1
PID2
PID3
I
I
I
1
1
2
Plug-In Development
Interaction with ProgressIDE
Development of User Interface
Code Viewing
5.
Description
Features not to be tested
The acceptance test will not cover the following because they are not in the scope of system.
o The testing for validation of the XML file will not be tested. It is assumed that ProgressIDE generates
an error-free XML file which is to be transformed to the executable code.
o The features that will not be tested are non-functional requirements such as behavior with different
versions of Eclipse.
Page 7
Project Name: ProCom@MDH
Acceptance Test Plan
6.
Version:
0.1.0
Date: 2009-11-25
Approach
This section describes the approach to be followed for system testing to ensure that it meets all requirements.
The Acceptance test will define how system is tested to ensure that it meets the requirements defined in the
Requirements document by testing the application as per the defined test cases.
The tests are structured in a way so that each test caters each requirement to meet. This way we can ensure that
all the requirements are met as listed in the Requirements Document. It is important that all tests are passed and
results of testing are recorded. The developer who is responsible for each part of the implementation should
perform testing as per the document.
6.1
Approach to configuration and installation
The developer who will do the testing will be responsible to install the software according to the installation
document. Person conducting the tests is also responsible for setting up needed environment.
For manual part of the testing, it is necessary to have application correctly installed and configured according to
Installation manual and hardware/software requirements stated in part 9. of this document.
7.
Item pass/fail criteria
As for the use-case scenario testing, if observed results after the tests don’t match the expected ones, the test will
be marked as failed. Also, if in any step during the use-case scenario it is impossible for any reason to continue
with following steps, the test will be marked as failed. In case, we successfully finish an use-case scenario, and
the actual results of the test match the expected ones ,the test would be marked as passed.
7.1
Installation and Configuration
Installation and configuration don’t have any impact on testing, since the developed software is Eclipse plug-in
code generator, that doesn’t have any aspect which depends on external configuration. Only requirement that
differs from the requirements for running the plug-in is need for ProgressIDE plug-in to be installed in Eclipse.
7.2
Documentation problems
It is importance that all documentation that specifies the expected behavior of PROCOM code generator plug-in,
especially requirements definition document is kept up-to-date. The documentation is the reference for testers,
and if it is not complete and updated, the following main problems can occur:
8.

The time spent on test case implementation is wasted if the test cases are incorrect because of invalid
reference documentation.

False errors are reported by testers - this takes the time of both testers and developers.
Suspension criteria and resumption requirements
For manual part of the testing ProCom code generator, it is important to restart a test case scenario every time a
system failure occurs, because the nature of the error could also affect test cases that follow, and then we would
have false errors reported in use-cases that would usually pass. Some of the manual tests will require restarting
even if the past test case finished successfully.
9.
Environmental needs
As it is already stated before, the environment for conducting needed tests is almost the same as the one that is
required for running plug-in on PROGRESS IDE.
9.1
Hardware
Since the ProgressIDE is developed as Eclipse plug-in, hardware requirements don’t depend on it, but on the
Eclipse version that you are running. So, minimal hardware requirements for PROCOM@MDH code generator
plug-in testing are the same as minimal hardware requirements for the PROGRESS IDE with which you will be
working.
Page 8
Project Name: ProCom@MDH
Acceptance Test Plan
9.2
Version:
0.1.0
Date: 2009-11-25
Software
Eclipse 3.4 with Progress IDE and code generator plug-in must be installed on the machine with JDK 1.6 or
higher in order to run the project.
9.3
N/A
Other
10.
Test procedure
Each test case has a name, a state ProCom should be in to initiate the case, what action(s) need to occur to
perform the test, and what should happen after the actions are completed.
10.1
Test case specifications
10.1.1
Generate Code –ProCom001
Description:
Testing the system to generate java code for PROCOM model. Selecting the XML file of ProCom model from
source directory and store the generated code in a destination directory, it is assumed that ProgressIDE generates
an error-free XML file of ProCom model which is to be transformed to the executable code.
Steps
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Click on “Project Explorer” and expand the tree.
Click on “ProCom” model tree item – “Generate Code” menu bar item should be enabled
Click on “Generate Code” tool bar item – window should open for selection of Source directory.
Click on “Browse” button to Select Source Directory
Source directory is set to the selected project directory by default.
Destination directory is set to the default “JavaSource” folder.
Click “Continue” button for code generation of selected XML file of ProCom Model.
The new window opens display the property of the files selected in the table.
Click on Generate Code Button.
New Message is shown for successful code generation.
A “JavaSource” folder “Project Explorer” that should contain java files generated from XML file of
ProCom Model
Test type:
Positive
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE
 A valid XML file exists for ProCom model.
Input definition:
Select XML File of a ProCom model from source directory.
Output definition:
At initial level, “JavaSource” folder will be created and appear in “Project Explorer” that should contains
executable Java code files generated by system.
Remarks:
This test case lets user to store generated code in the default directory.
10.1.2
View Code – ProCom-002
Description:
Testing the system to view java code generated by system or existing java code.
Steps
Page 9
Project Name: ProCom@MDH
Acceptance Test Plan
1.
2.
3.
Version:
0.1.0
Date: 2009-11-25
Click on “Project Explorer” and expand the tree.
Click on “JavaSource” folder and expand the tree.
Double Click on specific java for view, java file should open in editor.
Test type:
Positive
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE
 Generated java code is already generated and exists in source directory.
Input definition:
Generated java code file
Output definition:
Window will be open for view code/ Failed – error message will display
Remarks:
10.1.3
Compile Code – ProCom-003
Description:
Testing the system to compile code that is generated by code generation functionality of system for XML file of
ProCom model generated by ProgressIDE.
Steps
1.
2.
3.
4.
Click on “Project Explorer” and expand the tree.
Click on “JavaSource” folder and expand the tree.
Right Click on specific java for compilation, a menu should be display
Click on “Compile Code” option in menu to compile the java code.
Test type:
Positive
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE
 Generated Java code exists in destination directory.
Input definition:
Generated java code file
Output definition:
Successfully compiled/Failed
Remarks:
10.1.4
ProSys Composite Subsystem Code generation – ProCom-004
Description:
Testing the system to generate java code for ProCom model with Composite Subsystem. Selecting the XML file
of ProCom Composite Subsystem model from source directory and store the generated code in a destination
directory, it is assumed that ProgressIDE generates an error-free XML file of ProCom ProSys Composite
Subsystem model which is to be transformed to the executable code.
Steps
1.
2.
3.
4.
5.
Click on “Project Explorer” and expand the tree.
Click on “ProCom” model tree item – “Generate Code” menu bar item should be enabled
Click on “Generate Code” tool bar item – window should open for selection of Source directory.
Click on “Browse” button to Select Source Directory
Source directory is set to the selected project directory by default.
Page 10
Project Name: ProCom@MDH
Acceptance Test Plan
6.
7.
8.
9.
10.
11.
Version:
0.1.0
Date: 2009-11-25
Destination directory is set to the default “JavaSource” folder.
Click “Continue” button for code generation of selected XML file of ProCom Model.
The new window opens display the property of the files selected in the table.
Click on Generate Code Button.
New Message is shown for successful code generation.
A “JavaSource” folder “Project Explorer” that should contain java files generated from XML file of
ProCom Model
Test type:
Positive
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE
 A valid XML file exists for ProCom ProSys Composite Subsystem model.
Input definition:
Select XML File of a ProCom Composite Subsystem model from source directory.
Output definition:
Java files will be created in “JavaSource” folder that should contain executable java code generated from XML
files of ProCom ProSys Composite Subsystem Model
Remarks:
Page 11
Project Name: ProCom@MDH
Acceptance Test Plan
10.1.5
Version:
0.1.0
Date: 2009-11-25
ProSys Subsystem Code generation – ProCom-005
Description:
Testing the system to generate java code for ProCom Primitive Subsystem model. Selecting the XML file of
ProCom Primitive Subsystem model from source directory and store the generated code in a destination
directory, it is assumed that ProgressIDE generates an error-free XML file of ProCom ProSys Subsystem model
which is to be transformed to the executable code.
Steps
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Click on “Project Explorer” and expand the tree.
Click on “ProCom” model tree item – “Generate Code” menu bar item should be enabled
Click on “Generate Code” tool bar item – window should open for selection of Source directory.
Click on “Browse” button to Select Source Directory
Source directory is set to the selected project directory by default.
Destination directory is set to the default “JavaSource” folder.
Click “Continue” button for code generation of selected XML file of ProCom Model.
The new window opens display the property of the files selected in the table.
Click on Generate Code Button.
New Message is shown for successful code generation.
A “JavaSource” folder “Project Explorer” that should contain java files generated from XML file of
ProCom Model
.
Test type:
Positive
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE
 A valid XML file exists for ProCom ProSys Subsystem model.
Input definition:
Select XML File of a ProCom ProSys Subsystem model from source directory.
Output definition:
Java files will create in “JavaSource” folder that should contain executable java code generated from XML files
of ProCom ProSys Subsystem Model
Remarks:
10.1.6
Primitive ProSave Component Code generation – ProCom-006
Description:
Testing the system to generate java code for ProCom model with Primitive ProSave Component. Selecting the
XML file of ProCom ProSave Primitive Component model from source directory and store the generated code
in a destination directory, it is assumed that ProgressIDE generates an error-free XML file of ProCom ProSave
Primitive Component model which is to be transformed to the executable code.
Steps
1.
2.
3.
4.
5.
6.
7.
8.
9.
Click on “Project Explorer” and expand the tree.
Click on “ProCom” model tree item – “Generate Code” menu bar item should be enabled
Click on “Generate Code” tool bar item – window should open for selection of Source directory.
Click on “Browse” button to Select Source Directory
Source directory is set to the selected project directory by default.
Destination directory is set to the default “JavaSource” folder.
Click “Continue” button for code generation of selected XML file of ProCom Model.
The new window opens display the property of the files selected in the table.
Click on Generate Code Button.
Page 12
Project Name: ProCom@MDH
Acceptance Test Plan
Version:
0.1.0
Date: 2009-11-25
10. New Message is shown for successful code generation.
11. A “JavaSource” folder “Project Explorer” that should contain java files generated from XML file of
ProCom Model
Test type:
Positive
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE.
 A valid XML file exists for ProCom ProSave Primitive Component model.
Input definition:
Select XML File of a ProCom ProSave Primitive Component model from source directory.
Output definition:
Java files will create in “JavaSource” folder that should contain executable java code generated from XML files
of ProCom ProSave Primitive Component Model
Remarks:
10.1.7
ProSave CompositeComponent Code generation – ProCom-007
Description:
Testing the system to generate java code for ProCom model with ProSave Composite Component. Selecting the
XML file of ProCom ProSave Composite Component model from source directory and store the generated code
in a destination directory, it is assumed that ProgressIDE generates an error-free XML file of ProCom ProSave
Composite Component model which is to be transformed to the executable code.
Steps
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Click on “Project Explorer” and expand the tree.
Click on “ProCom” model tree item – “Generate Code” menu bar item should be enabled
Click on “Generate Code” tool bar item – window should open for selection of Source directory.
Click on “Browse” button to Select Source Directory
Source directory is set to the selected project directory by default.
Destination directory is set to the default “JavaSource” folder.
Click “Continue” button for code generation of selected XML file of ProCom Model.
The new window opens display the property of the files selected in the table.
Click on Generate Code Button.
New Message is shown for successful code generation.
A “JavaSource” folder “Project Explorer” that should contain java files generated from XML file of
ProCom Model
Test type:
Positive
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE.
 A valid XML file exists for ProCom ProSave Composite Component model.
Input definition:
Select XML File of a ProCom ProSave Composite Component model from source directory.
Output definition:
Java files will create in “JavaSource” folder that should contain executable java code generated from XML files
of ProCom ProSave Composite Component Model
Remarks:
10.1.8
Input Message Port Code generation – ProCom-009
Description:
Page 13
Project Name: ProCom@MDH
Acceptance Test Plan
Version:
0.1.0
Date: 2009-11-25
Testing the system to generate java code for ProCom model with Input Message Port. Selecting the XML file of
ProCom Input Message Port model from source directory and store the generated code in a destination directory,
it is assumed that ProgressIDE generates an error-free XML file of ProCom Input Message Port model which is
to be transformed to the executable code.
Steps
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Click on “Project Explorer” and expand the tree.
Click on “ProCom” model tree item – “Generate Code” menu bar item should be enabled
Click on “Generate Code” tool bar item – window should open for selection of Source directory.
Click on “Browse” button to Select Source Directory
Source directory is set to the selected project directory by default.
Destination directory is set to the default “JavaSource” folder.
Click “Continue” button for code generation of selected XML file of ProCom Model.
The new window opens display the property of the files selected in the table.
Click on Generate Code Button.
New Message is shown for successful code generation.
A “JavaSource” folder “Project Explorer” that should contain java files generated from XML file of
ProCom Model
Test type:
Positive
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE.
 A valid XML file exists for ProCom Input Message Port model.
Input definition:
Select XML File of a ProCom Input Message Port model from source directory.
Output definition:
Java files will create in “JavaSource” folder that should contain executable java code generated from XML files
of ProCom Input Message Port Model
Remarks:
10.1.9
Output Message Port Code generation – ProCom-010
Description:
Testing the system to generate java code for ProCom model with Output Message Port. Selecting the XML file
of ProCom Output Message Port model from source directory and store the generated code in a destination
directory, it is assumed that ProgressIDE generates an error-free XML file of ProCom Output Message Port
model which is to be transformed to the executable code.
Steps
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Click on “Project Explorer” and expand the tree.
Click on “ProCom” model tree item – “Generate Code” menu bar item should be enabled
Click on “Generate Code” tool bar item – window should open for selection of Source directory.
Click on “Browse” button to Select Source Directory
Source directory is set to the selected project directory by default.
Destination directory is set to the default “JavaSource” folder.
Click “Continue” button for code generation of selected XML file of ProCom Model.
The new window opens display the property of the files selected in the table.
Click on Generate Code Button.
New Message is shown for successful code generation.
A “JavaSource” folder “Project Explorer” that should contain java files generated from XML file of
ProCom Model
Test type:
Positive
Page 14
Project Name: ProCom@MDH
Acceptance Test Plan
Version:
0.1.0
Date: 2009-11-25
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE.
 A valid XML file exists for ProCom Output Message Port model.
Input definition:
Select XML File of a ProCom Output Message Port model from source directory.
Output definition:
Java files will create in “JavaSource” folder that should contain executable java code generated from XML files
of ProCom Output Message Port Model
Remarks:
10.1.10 Message Channel Code generation – ProCom-011
Description:
Testing the system to generate java code for ProCom model with Message Channel. Selecting the XML file of
ProCom Message Channel model from source directory and store the generated code in a destination directory,
it is assumed that ProgressIDE generates an error-free XML file of ProCom Message Channel model which is to
be transformed to the executable code.
Steps
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Click on “Project Explorer” and expand the tree.
Click on “ProCom” model tree item – “Generate Code” menu bar item should be enabled
Click on “Generate Code” tool bar item – window should open for selection of Source directory.
Click on “Browse” button to Select Source Directory
Source directory is set to the selected project directory by default.
Destination directory is set to the default “JavaSource” folder.
Click “Continue” button for code generation of selected XML file of ProCom Model.
The new window opens display the property of the files selected in the table.
Click on Generate Code Button.
New Message is shown for successful code generation.
A “JavaSource” folder “Project Explorer” that should contain java files generated from XML file of
ProCom Model
Test type:
Positive
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE.
 A valid XML file exists for ProCom Message Channel model.
Input definition:
Select XML File of a ProCom Message Channel model from source directory.
Output definition:
Java files will create in “JavaSource” folder that should contain executable java code generated from XML files
of ProCom Message Channel Model
Remarks:
10.1.11 Connector(s) Code generation – ProCom-012
Description:
Testing the system to generate java code for ProCom model with Connector(s). Selecting the XML file of
ProCom Connector(s) model from source directory and store the generated code in a destination directory, it is
assumed that ProgressIDE generates an error-free XML file of ProCom Connector(s) model which is to be
transformed to the executable code.
Steps
Page 15
Project Name: ProCom@MDH
Acceptance Test Plan
Version:
0.1.0
Date: 2009-11-25
Click on “Project Explorer” and expand the tree.
Click on “ProCom” model tree item – “Generate Code” menu bar item should be enabled
Click on “Generate Code” tool bar item – window should open for selection of Source directory.
Click on “Browse” button to Select Source Directory
Source directory is set to the selected project directory by default.
Destination directory is set to the default “JavaSource” folder.
Click “Continue” button for code generation of selected XML file of ProCom Model.
The new window opens display the property of the files selected in the table.
Click on Generate Code Button.
New Message is shown for successful code generation.
A “JavaSource” folder “Project Explorer” that should contain java files generated from XML file of
ProCom Model
Test type:
Positive
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE.
 A valid XML file exists for ProCom Connector(s) model.
Input definition:
Select XML File of a ProCom Connector(s) model from source directory.
Output definition:
Java files will create in “JavaSource” folder that should contain executable java code generated from XML files
of ProCom Connector(s) Model
Remarks:
Page 16
Project Name: ProCom@MDH
Acceptance Test Plan
Version:
0.1.0
Date: 2009-11-25
10.1.12 Connection(s) Code generation – ProCom-012
Description:
Testing the system to generate java code for ProCom model with Connection(s). Selecting the XML file of
ProCom Connection(s) model from source directory and store the generated code in a destination directory, it
is assumed that ProgressIDE generates an error-free XML file of ProCom Connection(s) model which is to be
transformed to the executable code.
Steps
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Click on “Project Explorer” and expand the tree.
Click on “ProCom” model tree item – “Generate Code” menu bar item should be enabled
Click on “Generate Code” tool bar item – window should open for selection of Source directory.
Click on “Browse” button to Select Source Directory
Source directory is set to the selected project directory by default.
Destination directory is set to the default “JavaSource” folder.
Click “Continue” button for code generation of selected XML file of ProCom Model.
The new window opens display the property of the files selected in the table.
Click on Generate Code Button.
New Message is shown for successful code generation.
A “JavaSource” folder “Project Explorer” that should contain java files generated from XML file of
ProCom Model
Test type:
Positive
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE.
 A valid XML file exists for ProCom Connection(s) model.
Input definition:
Select XML File of a ProCom Connection(s) model from source directory.
Output definition:
Java files will create in “JavaSource” folder that should contain executable java code generated from XML files
of ProCom Connection(s) Model
Remarks:
10.1.13 ProSys Clock Code generation – ProCom-012
Description:
Testing the system to generate java code for ProCom ProSys model with Clock. Selecting the XML file of
ProCom Connection(s) model from source directory and store the generated code in a destination directory, it
is assumed that ProgressIDE generates an error-free XML file of ProCom ProSave Clock model which is to be
transformed to the executable code.
Steps
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Click on “Project Explorer” and expand the tree.
Click on “ProCom” model tree item – “Generate Code” menu bar item should be enabled
Click on “Generate Code” tool bar item – window should open for selection of Source directory.
Click on “Browse” button to Select Source Directory
Source directory is set to the selected project directory by default.
Destination directory is set to the default “JavaSource” folder.
Click “Continue” button for code generation of selected XML file of ProCom Model.
The new window opens display the property of the files selected in the table.
Click on Generate Code Button.
New Message is shown for successful code generation.
A “JavaSource” folder “Project Explorer” that should contain java files generated from XML file of
ProCom Model
Page 17
Project Name: ProCom@MDH
Acceptance Test Plan
Version:
0.1.0
Date: 2009-11-25
Test type:
Positive
Preconditions:
 Progress IDE should be up and running.
 Plug-in is applied in progress IDE.
 A valid XML file exists for ProCom ProSave Clock model.
Input definition:
Select XML File of a ProCom ProSave Clock model from source directory.
Output definition:
Java files will create in “JavaSource” folder that should contain executable java code generated from XML files
of ProCom ProSave Clock Model
Remarks:
Page 18
Project Name: ProCom@MDH
Acceptance Test Plan
Version:
0.1.0
Date: 2009-11-25
10.2
Test plan
Use-case scenario tests do not require any specific order, so they can be done in which ever order user chooses,
or even done separately. However, some of the test cases require that there are already existing
PROCOM@MDH projects available to user conducting tests, so user should create at least two different test
models before running the tests that are connected to opening and merging of existing projects.
11.
Responsibilities
11.1
Developers
Developers’ responsibilities are to test their part of the code and provided functionality during the development
process. They also need to be completely familiar and understand the requirements and design related
documentation, so the implementation is compatible with test specification.
In the testing phase, developers have to be available at least once a day on skype, or if that is impossible, check
the google groups MDH_PROCOM group messages at least twice a day, for communication with the testers.
Also, they need to inform tester whenever one of the errors are resolved.
11.2
User representative
Customers have no special responsibilities during the testing. They should be available for discussing testing
results and how to deal with failed/misunderstood requirements.
12.
Risks and contingencies
Additional errors could be introduced with future versions of Eclipse, but since we can not affect othe
development of the aforementioned products, that doesn’t come under our responsibility. However, that kind of
risk is almost negligible, and if necessary can be avoided by using the exact versions of software that were listed
fewer than 9.2.
13.
Approvals
Name
Title
Date
yyyy-mm-dd
Signature
Page 19