SpinGrid Testing Documents

Software Engineering Project (2IP40)
Project Group 1
Acceptance Test Plan

version 1.0.0 (Approved), 8 June 2006
Project Team:
Project Manager: Senior Manager: Advisor: Customer:
Sven Bego Roel Coset Robert Leeuwestein Maarten Leijten Ivo van der Linden Joery Mens Marcel Moreaux Tim Muller Tom Kleijkers L. Somers Y.Usenko C. Plevier H. de Wolf
0550191 0548132 0546746 0547649 0547632 0547515 0499480 0547961 0515015 TU/e HG 7.83 TU/e HG 5.71 Dutch Space Dutch Space
Technische Informatica, Eindhoven University of Technology, Eindhoven
Abstract
This document describes the Acceptance Test Plan (ATP) for the SPINGRID system and was made according to the software engineering standard provided by the European Space Agency described in [ESA]. The projects acceptance test for the product is described here. This project is one of seven assignments for the course 2IP40 at Eindhoven University of Technology.
SPINGRID
Acceptance Test Plan 1.0.0
Contents
1 Introduction 1.1 1.2 1.3 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of denitions and abbreviations . . . . . . . . . . . . . . . . . . . . . . . 1.3.1 1.3.2 1.4 Denitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6 6 7 7 8 8 8 8 8 9 9 9 9 10 10 11 12 13 15 16 21 22
Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1 1.4.2 Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Test plan 2.1 2.2 2.3 2.4 2.5 2.6 Test items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features to be tested . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test deliverables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environmental needs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Test case pass/fail criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Test case specications 3.1 3.2 3.3 3.4 3.5 General Requirements Acceptance Tests . . . . . . . . . . . . . . . . . . . . . Job Requirements Acceptance Tests . . . . . . . . . . . . . . . . . . . . . . . System Admin Requirements Acceptance Tests . . . . . . . . . . . . . . . . . Resource Provider Requirements Acceptance Tests . . . . . . . . . . . . . . . Project Admin Requirements Acceptance Tests . . . . . . . . . . . . . . . . .
SPINGRID
CONTENTS
3.6 3.7 3.8 3.9
Application Provider Requirements Acceptance Tests . . . . . . . . . . . . . . Data Provider Requirements Acceptance Tests . . . . . . . . . . . . . . . . . Job Provider Requirements Acceptance Tests . . . . . . . . . . . . . . . . . . Extrafunctional Requirements Acceptance Tests . . . . . . . . . . . . . . . . .
25 27 29 30 33 33 33 34 34 34 34 34 35
4 Test procedures 4.1 4.2 4.3 4.4 4.5 4.6 4.7 Test procedure for system admin . . . . . . . . . . . . . . . . . . . . . . . . . Test procedure for resource provider . . . . . . . . . . . . . . . . . . . . . . . Test procedure for project admin . . . . . . . . . . . . . . . . . . . . . . . . . Test procedure for application provider . . . . . . . . . . . . . . . . . . . . . . Test procedure for data provider . . . . . . . . . . . . . . . . . . . . . . . . . Test procedure for job provider . . . . . . . . . . . . . . . . . . . . . . . . . . Other test procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 Test report
SPINGRID
Document Status Sheet

Document Title Document Identication Author(s) Version Document Status Acceptance Test Plan SPINGRID/Documents/product/ATP/1.0.0 R. Leeuwestein, J. Mens 1.0.0 draft / internally accepted / conditionally approved / approved Summary Document creation Draft Added chapter 4 and 5 Version for rst internal review Version for second internal review Internally accepted Approved
Version 0.0.1 0.0.2 0.0.3 0.0.4 0.0.5 0.1.0 1.0.0
Date 24-01-2006 18-05-2006 21-05-2006 23-05-2006 31-05-2006 31-05-2006 15-06-2006
Author(s) J. Mens R. Leeuwestein R. Leeuwestein R. Leeuwestein R. Leeuwestein R. Leeuwestein J. Mens
SPINGRID
Document Change Report

Document Title Document Identication Date of Changes
10
Acceptance Test Plan SPINGRID/Documents/product/ATP/1.0.0 N/A
SPINGRID
Chapter 1
Introduction
1.1 Purpose
15
This document describes the plan for testing the developed SPINGRID software against the user requirements as dened in [URD]. The purpose of this acceptance test is to make sure that the system developed during the SPINGRID project complies with the requirements of URD. These tests should be executed in the Acceptance Test (AT) phase of the SPINGRID project.
1.2
20
Scope
The software implements a computational grid. This grid is able to execute jobs when it receives an application accompanied by a set of data les. By hiding the complexity of grid technology the system will be easy to use. Usability is also increased by oering a web-based front-end for users to access the system.
SPINGRID
CHAPTER 1. INTRODUCTION
1.3
25
List of denitions and abbreviations

Denitions
Application that is used by a resource provider to retrieve and execute jobs. A non-interactive data processing application consisting of executables, scripts and/or auxiliary data les that reads one or more input data les and writes one ore more output les. An application provider can oer a set of applications to the SPINGRID system. They can restrict access for projects and for resource providers to their applications. Application that is used by all the users except the resource provider who uses the agent application. A hardware and software infrastructure that enables coordinated resource sharing within dynamic organizations consisting of individuals, institutions and resources. Dutch Space B.V. A data provider can oer a set of datales to the SPINGRID system. They can restrict access for projects and for resource providers to their datales. A dispatcher acts like a server and manages the distribution of jobs over the computational grid. Specication of application, conguration data, input and/or output data les and scheduler specic data (priority, preferred resource, etc). Job providers are users that oer a job to a project. They have to be a member of that particular project. A collection of jobs with specied access rights to which users (project members) can be assigned. The project administrators administrate projects and can assign and remove job providers, congure a project and restrict access for resource providers. Resource providers are users that oer time on their computers to the SPINGRID system. They can restrict access to their computer for application providers and projects. The actions and activities assigned to a person. A computational grid using SPINGRID software. Software developed by Dutch Space and TU/e to build computational grids for distributed data processing. The full name of the entire system. The system administrator oversees the entire SPINGRID system and has the right to congure the system, to create and remove projects and assign and remove project administrators.
1.3.1
Agent
Application
Application Provider
Client Computational Grid
Customer Data Provider Dispatcher Job Job Provider Project Project Administrator
Resource Provider
Role SPINGRID SPINGRID Software SPINGRID System System Administrator
SPINGRID
CHAPTER 1. INTRODUCTION
1.3.2
ATP ESA JRE NAT URD
Abbreviations
Acceptance Test Plan European Space Agency Java Runtime Environment Network Address Translation User Requirements Document
1.4
30
Documents
Reference Documents
BSSC 2005 Java Coding Standard, Issue 1.0, March 2005 ESA Software Engineering Standards (ESA PSS-05-0 Issue 2), ESA Board for Software Standardization and Control (BSSC), 1991 Job Submission Description Language (JSDL) Specication, Version 1.0, November 2005 Software Transfer Document, SPINGRID team, TU/e, Version 0.0.1, May 2006 Software User Manual, SPINGRID team, TU/e, Version 0.0.1, May 2006 Software Verication and Validation Plan, SPINGRID team, TU/e, Version 0.1.2, March 2006
1.4.1
[BSSC] [ESA] [JSDL] [STD]
[SUM] [SVVP]
1.4.2
[URD] [SRD]
Applicable Documents
User Requirements Document, SPINGRID team, TU/e, version 1.0.0, February 2006 Software Requirements Document, SPINGRID team, TU/e, version 1.0.1, March 2006
1.5
Overview
35
In the second chapter the items to be tested are mentioned. A specication for each test case is given in the third chapter. The fourth chapter species the procedures for these test cases. In the fth chapter the reports for all test cases are presented.
SPINGRID
Chapter 2
Test plan
2.1 Test items
40
The software to be tested is the SPINGRID system. The user requirements can be found in [URD].
2.2
Features to be tested
The SPINGRID system will adhere to the requirements, which are documented in chapter 4 of the URD.
2.3
45
Test deliverables
The following items must be delivered before testing begins: The Software Verication and Validation Plan [SVVP]. The Software Requirements Document [SRD]. The User Requirements Document [URD]. The Software Transfer Document [STD].
50
Chapters 1, 2, 3 and 4 of this Acceptance Test Plan. Acceptance Test input data. Software to be tested. The following items must be delivered when the testing is nished: Acceptance test report. SPINGRID Acceptance Test Plan 1.0.0 9
CHAPTER 2. TEST PLAN
55
Acceptance test output data. Problem reports (if necessary).
2.4
Testing tasks
The following tasks are necessary for preparing and performing the acceptance tests: Designing the acceptance tests.
60
Ensuring that all environmental needs are satised for the acceptance tests. Performing the acceptance tests.
2.5
Environmental needs
65
The environmental requirements in [URD] only describe that the SPINGRID system runs on Windows XP, Mac OS or Linux. The environmental requirements are described in more detail in [SRD]. The requirements in [SRD] are taken instead of the requirements in [URD] because the URD does not describe the environment sucient. General Requirements: 1 dispatcher 40 agents
70
10 clients Dispatcher: Intel Pentium IV 2 GHz or equivalent 2 GB RAM 2 MBit/s network
75
dedicated server Linux 2.4 (or higher) Sun JRE 1.4.2 or 1.5 MySQL 5.0 MySQL Connector/J JDBC driver (libmysql-java)
80
IP-tables
SPINGRID
10
CHAPTER 2. TEST PLAN
Agent: Intel Pentium II 300 MHz or equivalent, G4 700 MHz or equivalent 128 MB RAM 256 MB Available Harddisk Space
85
Windows XP, Mac OS X or Linux 2.4 (or higher) Sun JRE 1.4.2 or 1.5 Client: Windows XP, Mac OS X or Linux 2.4 (or higher) Sun JRE 1.4.2 or 1.5
90
2.6
Test case pass/fail criteria
Every test should describe the criteria that should be met to pass that specic test.
SPINGRID
11
Chapter 3
Test case specications

In this chapter the test cases for all the user requirements are listed. If for specic tests any extra environmental needs are needed then they are mentioned in the test specication. There are a couple user requirements that dont have an acceptance test. The user requirements below dont have an acceptance test because it is not clear how to test these user requirements:
100
95
UR 0010 UR 0060 UR 0070 UR 2010 The user requirements below dont have an acceptance test because the requirements are not implemented in the SPINGRID system: UR 2140 UR 3010 UR 3020 UR 3030
105
110
UR 3040 UR 3060 UR 3062 UR 3072 UR 3074 SPINGRID Acceptance Test Plan 1.0.0 12
CHAPTER 3. TEST CASE SPECIFICATIONS
115
UR 4040 UR 4060 UR 5050 UR 5052 UR 5054
120
UR 6040 UR 6042 UR 7040 UR 7050 UR 7052
125
UR 7090 UR 7100 UR 7110 The user requirements below dont have an acceptance test because they are trivial. This is because there is only one dispatcher in the SPINGRID system:
130
UR 8010 UR 8020
3.1
General Requirements Acceptance Tests
TC 0020 acceptance test

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 0020 This test case veries whether the SPINGRID system provides an English interface This test case is veried by performing all acceptance tests in sections 3.2 to 3.8. Check if the interface of the SPINGRID system is English None
135
SPINGRID
13

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 0030 This test case veries whether all users can interact with a command-line interface in the SPINGRID system This test case is veried by performing all acceptance tests in sections 3.2 to 3.8 in the command-line interface Check if all acceptance tests can be done with the command-line interface None

Test Case Identier Test Item(s) Input Specication Output Specication
140
Environmental Needs
TC 0040 This test case veries whether all users can interact with a webbased interface in the SPINGRID system This test case is veried by performing all acceptance tests in sections 3.2 to 3.8 in the web-based interface Check if all acceptance tests can be done with the web-based interface None

Test Case Identier Test Item(s) Input Specication TC 0050 This test case veries whether the SPINGRID system can handle at least 40 executing jobs Perform TC 7020 Perform TC 7010 40 times in a short time Perform TC 7060 for those jobs when they are nished Check if the output of all 40 jobs is expected None
Output Specication Environmental Needs
145

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 0080 This test case veries whether the SPINGRID system provide a trust model as described in [URD, section 2.4.2] This test case is veried by applying for each user all actions described in [URD, appendix A] Check if all allowed actions for each user succeed and all other actions for that user fails None
SPINGRID
14
3.2
Job Requirements Acceptance Tests

Test Case Identier Test Item(s) TC 1010 This test case veries whether the SPINGRID system only accepts a job description written in a language who is a standardized one or one proposed for standardization This test case is veried by creating a job using the description language JSDL (described in [JSDL]) and oering it to the SPINGRID system (perform TC 7020 and then TC 7010) Check if the SPINGRID system accepts the job description None
Input Specication
150
TC 1020a acceptance test

Test Case Identier Test Item(s) Input Specication TC 1020a This test case veries whether jobs can only be oered to the SPINGRID system by using a job description This test case is veried by creating a job using the description language JSDL (described in [JSDL]) and oering it to the SPINGRID system (perform TC 7020 and then TC 7010) Check if the SPINGRID system accepts the job description None
155
TC 1020b acceptance test

Test Case Identier Test Item(s) Input Specication TC 1020b This test case veries whether jobs can only be oered to the SPINGRID system by using a job description This test case is veried by creating a job using a description language that is not standardized and is not proposed for standardization and oering it to the SPINGRID system (perform TC 7020 and then TC 7010 but with the le testjobfail.jsdl instead of testjob.jsdl.) Check if the SPINGRID system rejects the job description None
SPINGRID
15

Test Case Identier Test Item(s) TC 1030 This test case veries whether the job description contains all the necessary information for the SPINGRID system to handle the job Perform TC 7020 Perform TC 7010 Perform TC 7060 when the job is nished Check if the SPINGRID system accepts the job and if the job is executed correctly None
Input Specication
Output Specication
160
Environmental Needs
3.3
System Admin Requirements Acceptance Tests

Test Case Identier Test Item(s) Input Specication TC 2020 This test case veries whether the system admin can authorize a user to become an application provider Open the le options in the main directory of the client Type as password systemadmin Type as username systemadmin Type as dispatcher address the address of the dispatcher Save the le Type java -jar sgclient.jar as rol:sysadmin add user testuser testpassword Type java -jar sgclient.jar assign rol:appprov to usr:testuser Check if the user has application provider rights None
SPINGRID
16
165

Test Case Identier Test Item(s) Input Specication TC 2100 This test case veries whether the system admin can change system settings Open the le options in the directory of the dispatcher Type as database address the address of the database Type as http port the port that the dispatcher should listen to Type as max connections the maximal connections with the clients and agents Save the le Check if the system settings work correctly None

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 2030 This test case veries whether the system admin can authorize a user to become a data provider Type java -jar sgclient.jar assign rol:datprov to usr:testuser Check if the user has data provider rights None
170

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 2050 This test case veries whether the system admin can remove the role of application provider from a user Type java -jar sgclient.jar unassign rol:appprov from usr:testuser Check if the user has no longer application provider rights None

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 2060 This test case veries whether the system admin can remove the role of data provider from a user Type java -jar sgclient.jar unassign rol:datprov from usr:testuser Check if the user has no longer data provider rights None
175
SPINGRID
17

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 2080 This test case veries whether the system admin can add a project to the system Type java -jar sgclient.jar add project testproject with usr:testuser Check if the project is added to the SPINGRID system and if the user has project admin rights for the project None
180

Test Case Identier Test Item(s) Input Specication TC 2040 This test case veries whether the system admin can authorize a user to become a project admin of a project Type java -jar sgclient.jar as rol:sysadmin add user testuser2 testpassword Type java -jar sgclient.jar assign rol:projadmin to usr:testuser2 in pro:testproject Check if the user has project admin rights for the specied project None

185
Environmental Needs
TC 2114 This test case veries whether the system admin can view a list of all project admins of a project Type java -jar sgclient.jar list users having rol:projadmin Check if the output gives a list of project admins of the specied project None

Test Case Identier Test Item(s) TC 2070a This test case veries whether the system admin can remove the role of project admin from a user if that project does not violate UR 4010 Type java -jar sgclient.jar unassign rol:projadmin from usr:testuser2 in pro:testproject Check if the user has no longer project admin rights for the specied project None Acceptance Test Plan 1.0.0 18
Input Specication Output Specication Environmental Needs SPINGRID

Test Case Identier Test Item(s) TC 2070b This test case veries whether the system admin can remove the role of project admin from a user if that project does not violate UR 4010 Type java -jar sgclient.jar unassign rol:projadmin from usr:testuser in pro:testproject Check if an error message is returned because the project has only one project admin None
Input Specication Output Specication

190
Environmental Needs

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 2090 This test case veries whether the system admin can remove a project from the system Type java -jar sgclient.jar remove pro:testproject Check if the project does not exist in the SPINGRID system and if there are no users who still belong to the project None
195

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 2110 This test case veries whether the system admin can view a list of all jobs in the SPINGRID system Type java -jar sgclient.jar as rol:sysadmin list jobs Check if the output gives a list of all jobs in the SPINGRID system None
SPINGRID
19

Test Case Identier Test Item(s) Input Specication TC 2120 This test case veries whether the system admin can view a list of all trusted application providers in a project Type java -jar sgclient.jar as rol:sysadmin list users having rol:appprov Type java -jar sgclient.jar info usr:applicationprovider Check if the output gives a list of all trusted application providers in the specied project None
Output Specication
200
Environmental Needs

Test Case Identier Test Item(s) Input Specication TC 2130 This test case veries whether the system admin can view a list of all trusted data providers in a project Type java -jar sgclient.jar as rol:sysadmin list users having rol:datprov Type java -jar sgclient.jar info usr:dataprovider Check if the output gives a list of all trusted data providers in the specied project None

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 2150 This test case veries whether the system admin can work on a machine running Windows XP, Linux or Mac OS Perform all test cases of the system admin Check if no test cases fail The machine is running on Windows XP, Linux or Mac OS
205
SPINGRID
20
3.4
Resource Provider Requirements Acceptance Tests

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 3070a This test case veries whether the installation of the SPINGRID software should not require a computer expert Install the agent software as described in [SUM] by a person that is not a computer expert Check if the installation is successful The SPINGRID software is not installed
210

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 3050 This test case veries whether a resource provider can see on which projects his resource is working on Type list projects Check if the projects, which the resource is working on, is returned None

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 3070b This test case veries whether the de-installation of the SPINGRID software should not require a computer expert Uninstall the agent software as described in [SUM] by a person that is not a computer expert Check if the de-installation is successful The SPINGRID software is installed
215

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 3080 This test case veries whether the resource provider can work on a machine running Windows XP, Linux or Mac OS Perform all test cases of the resource provider Check if no test cases fail The machine is running on Windows XP, Linux or Mac OS
SPINGRID
21
220
3.5
Project Admin Requirements Acceptance Tests

Test Case Identier Test Item(s) Input Specication TC 4010 This test case veries whether the SPINGRID system has at least one project admin assigned to every project at all times Perform TC 2020 Perform TC 2080 Perform TC 2040 Perform TC 2070a Perform TC 2070b Check if all acceptance tests are successful None

Test Case Identier Test Item(s) Input Specication TC 4050a This test case veries whether a project admin can select which applications or application providers he trusts Open the le options in the main directory of the client Type as password projectadmin Type as username projectadmin Type as dispatcher address the address of the dispatcher Save the le Type java -jar sgclient.jar trust usr:applicationprovider as rol:appprov for pro:project Check if the application provider and all applications of the application provider are trusted for the project None
Output Specication
225
Environmental Needs

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 4050b This test case veries whether a project admin can select which applications or application providers he trusts Type java -jar sgclient.jar distrust usr:applicationprovider as rol:appprov for pro:project Check if the application provider and all applications of the application provider are distrusted for the project None
SPINGRID
22
230

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 4020 This test case veries whether the project admin can authorize a user to become a job provider (in the project admin project) Type java -jar sgclient.jar assign rol:jobprov to usr:testuser in pro:project Check if the user has job provider rights in the project None

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 4030 This test case veries whether the project admin can remove the role of job provider from a user (in the project admin project) Type java -jar sgclient.jar unassign rol:jobprov from usr:testuser in pro:project Check if the user no longer has job provider rights None
235

Test Case Identier Test Item(s) Input Specication TC 4042a This test case veries whether a project admin can select which data sources (either a data provider or a dataset) he trusts Open the le options in the main directory of the client Type as password systemadmin Type as username systemadmin Type java -jar sgclient.jar assign rol:datprov to usr:testuser Open the le options in the main directory of the client Type as password projectadmin Type as username projectadmin Type java -jar sgclient.jar trust usr:testuser as rol:datprov for pro:project Check if the user is trusted as data provider for the project None
SPINGRID
23

240
Environmental Needs
TC 4042b This test case veries whether a project admin can select which data sources (either a data provider or a dataset) he trusts Type java -jar sgclient.jar distrust usr:testuser as rol:datprov for pro:project Check if the user is not trusted anymore as data provider for the project None

Test Case Identier Test Item(s) Input Specication TC 4080 This test case veries whether the project admin can view a list of all jobs in the project admin project Perform TC 7020 Perform TC 7010 Open the le options in the main directory of the client Type as password projectadmin Type as username projectadmin Type as dispatcher address the address of the dispatcher Save the le Type java -jar sgclient.jar as rol:projadmin list jobs Check if the output gives a list of jobs in the project admin project None
245

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 4070 This test case veries whether a project admin can remove a job from his project Type java -jar sgclient.jar as rol:projadmin remove job:testjob Check if the job is removed from the project While the dispatcher is performing a job
SPINGRID
24

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 4090 This test case veries whether the project admin can work on a machine running Windows XP, Linux or Mac OS Perform all test cases of the project admin Check if no test cases fail The machine is running on Windows XP, Linux or Mac OS
250
3.6
Application Provider Requirements Acceptance Tests

Test Case Identier Test Item(s) Input Specication TC 5010 This test case veries whether an application provider can add applications to the SPINGRID system Open the le options in the main directory of the client Type as password applicationprovider Type as username applicationprovider Type as dispatcher address the address of the dispatcher Save the le Type java -jar sgclient.jar add app l:testapp.xml as testapp this is a test application Check if the application is added in the SPINGRID system None
255

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 5030a This test case veries whether an application provider can select for which projects his applications may be used Type java -jar sgclient.jar trust app:testapp for pro:project Check if the application is trusted for the project None

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs SPINGRID TC 5030b This test case veries whether an application provider can select for which projects his applications may be used Type java -jar sgclient.jar distrust app:testapp for pro:project Check if the application is distrusted for the project None Acceptance Test Plan 1.0.0 25
260

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 5040 This test case veries whether an application provider can see on which projects his applications are used Type java -jar sgclient.jar as rol:appprov list jobs Check if the output gives a list of projects who have used applications from the application provider None

265
Environmental Needs
TC 5042 This test case veries whether an application provider can see which applications he provides Type java -jar sgclient.jar as rol:appprov list apps Check if the output gives a list of applications provided by the application provider None

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 5012 This test case veries whether an application provider can remove applications from the SPINGRID system Type java -jar sgclient.jar remove app:testapp Check if the application is removed from the SPINGRID system None
270

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 5020 This test case veries whether an application provider can provide applications for Windows XP, Linux or Mac OS X Type java -jar sgclient.jar add app l:testapp.xml as testapp this is a test application for Windows XP, Linux and Mac OS X Check if the three applications are added to the SPINGRID system None
SPINGRID
26

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 5060 This test case veries whether an application provider can work on a machine running Windows XP, Linux or Mac OS Perform all test cases of the application provider Check if no test cases fail The machine is running on Windows XP, Linux or Mac OS
275
3.7
Data Provider Requirements Acceptance Tests

Test Case Identier Test Item(s) Input Specication TC 6010 This test case veries whether a data provider can add data les to the SPINGRID system Open the le options in the main directory of the client Type as password dataprovider Type as username dataprovider Type as dispatcher address the address of the dispatcher Save the le Type java -jar sgclient.jar add data l:testdata.txt testdata This is a tets dataset Check if the data is added in the SPINGRID system None
280

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 6020a This test case veries whether a data provider can select for which projects his data may be used Type java -jar sgclient.jar trust dat:testdata for pro:project Check if the dataset is trusted for the project None

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs SPINGRID TC 6020b This test case veries whether a data provider can select for which projects his data may be used Type java -jar sgclient.jar distrust dat:testdata for pro:project Check if the dataset is distrusted for the project None Acceptance Test Plan 1.0.0 27
285

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 6030 This test case veries whether a data provider can see on which projects his data is used Type java -jar sgclient.jar as rol:datprov list projects Check if the output gives a list of projects who have used data from the data provider None

290
Environmental Needs
TC 6032 This test case veries whether a data provider can see which data he provides Type java -jar sgclient.jar as rol:datprov list data Check if the output gives a list of data provided by the data provider None

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 6012 This test case veries whether a data provider can remove data les from the SPINGRID system Type java -jar sgclient.jar remove dat:testdata Check if the provided data is removed from the SPINGRID system None
295

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 6050 This test case veries whether a data provider can work on a machine running Windows XP, Linux or Mac OS Perform all test cases of the data provider Check if no test cases fail The machine is running on Windows XP, Linux or Mac OS
SPINGRID
28
3.8
Job Provider Requirements Acceptance Tests

Test Case Identier Test Item(s) Input Specication TC 7020 This test case veries whether a job provider can request a list of all applications available to him Open the le options in the main directory of the client Type as password jobprovider Type as username jobprovider Type as dispatcher address the address of the dispatcher Save the le Type java -jar sgclient.jar as rol:jobprov list apps Check if the output gives a list of applications available to the job provider None
Output Specication
300
Environmental Needs

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 7010 This test case veries whether a job provider can oer testjob.jsdl to the SPINGRID system Type java -jar sgclient.jar add job l:testjob.jsdl to pro:project Check if the job is added in the SPINGRID system None
305

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 7080 This test case veries whether a job provider can see a list of his jobs Type java -jar sgclient.jar as rol:jobprov list jobs Check if the output gives a list of jobs provided by the job provider None

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 7070 This test case veries whether a job provider can remove his jobs Type java -jar sgclient.jar as rol:jobprov remove job:testjob Check if the job is removed from the SPINGRID system None
310
SPINGRID
29

Test Case Identier Test Item(s) Input Specication TC 7082 This test case veries whether a job provider can inform the SPINGRID system of the characteristics that their jobs require Create a JSDL le (test2job.jsdl) with the required characteristics of the job as described in [SUM] Type java -jar sgclient.jar add job l:test2job.jsdl to pro:project Check if the provided job is accepted by the SPINGRID system None

Test Case Identier Test Item(s) Input Specication Output Specication Environmental Needs TC 7120 This test case veries whether a job provider can work on a machine running Windows XP, Linux or Mac OS Perform all test cases of the job provider Check if no test cases fail The machine is running on Windows XP, Linux or Mac OS
315
3.9
Extrafunctional Requirements Acceptance Tests

Test Case Identier Test Item(s) TC 8030 This test case veries whether the SPINGRID system has the following property: if one of the resources disappears while it was performing a job, the SPINGRID system should requeue the job Disconnect a resource from the SPINGRID system when it is calculating a job Check if the job is requeued None
Input Specication Output Specication Environmental Needs
320
SPINGRID
30

Test Case Identier Test Item(s) TC 8040 This test case veries whether the SPINGRID system has the following property: a job will be declared failed after it has been requeued for a congurable number of times Perform TC 8030 for the congurable number times with the same job Check if the job is declared failed None

Test Case Identier Test Item(s) TC 8050 This test case veries whether the SPINGRID system has the following property: the functionality of the system should not be restricted when computers of users are behind a rewall (which does not restrict trac over port 80) and/or NAT Perform all test cases Check if all test cases are successful All or some computers in the SPINGRID system are behind a rewall and/or NAT

325

Test Case Identier Test Item(s) TC 8060 This test case veries whether the SPINGRID system has the following property: the SPINGRID software shall be implemented in Java according to (a tailored version of ) the BSSC Java Coding Standards [BSSC] The source code of the SPINGRID system Check if it is implemented in Java according to the BSSC Java Coding Standards None
SPINGRID
31
330

Test Case Identier Test Item(s) TC 8070 This test case veries whether the SPINGRID system has the following property: the SPINGRID system shall be able to run for at least a week on the test environment without interruption. Run the SPINGRID system on the test environment (as described in chapter 2) for a week Check if the system is still running None

Test Case Identier Test Item(s) TC 8080 This test case veries whether the SPINGRID system has the following property: all applications in the SPINGRID system should log what they are doing Perform all test cases Open the log and error le in the main directory of the agent Open the log and error le in the main directory of the client Open the log and error le in the main directory of the dispatcher Check if everything was logged None
Input Specication
335

Test Case Identier Test Item(s) TC 8090 This test case veries whether the SPINGRID system has the following property: the total time in which no dispatcher responses should not exceed one hour a day during the acceptance test on the test environment Perform all test cases in the test environment (as described in chapter 2) Check if the total time in which no dispatcher responds does not exceed one hour a day None
SPINGRID
32
Chapter 4
340
Test procedures
As general prerequisite, all required hardware and software is assumed to be present, installed and running error free. Therefore the customer is responsible to have an environment as described in chapter 2. The test procedure must be run in this environment. Also, the dispatcher should have the database as described in test.sql, the client should have testjob.jsdl, testjobfail.jsdl, testapp.xml and testdata.dat. After performing a test procedure the database of the dispatcher should be reset to test.sql.
345
4.1
Test procedure for system admin

TP1 To test if the system admin can perform all actions as described in [URD, section 4.3] Perform TC 2020, TC 2100, TC 2030, TC 2050, TC 2060, TC 2080, TC 2040, TC 2114, TC 2070a, TC 2070b, TC 2090, TC 2110, TC 2120, TC 2130 and TC 2150
Identier Purpose Steps
4.2
Test procedure for resource provider

TP2 To test if the resource provider can perform all actions as described in [URD, section 4.4] Perform TC 3070a, TC 3030a, TC 3050, TC 3030b, TC 3060a, TC 3060b, TC 3074a, 3074b, TC 3070b and TC 3080

350
SPINGRID
33
CHAPTER 4. TEST PROCEDURES
4.3
Test procedure for project admin

TP3 To test if the project admin can perform all actions as described in [URD, section 4.5] Perform TC 4010, TC 4050a, TC 4050b, TC 4020, TC 4060a, TC 4060b, TC 4030, TC 4042a, TC 4042b, TC 4080, TC 4070 and TC 4090
4.4
Test procedure for application provider

TP4 To test if the application provider can perform all actions as described in [URD, section 4.6] Perform TC 5010, TC 5030a, TC 5030b, TC 5040, TC 5042, TC 5012, TC 5020 and TC 5060
355
4.5
Test procedure for data provider

TP5 To test if the application provider can perform all actions as described in [URD, section 4.7] Perform TC 6010, TC 6020a, TC 6020b, TC 6030, TC 6032, TC 6012 and TC 6050
4.6
Test procedure for job provider

TP6 To test if the job provider can perform all actions as described in [URD, section 4.8] Perform TC 7020, TC 7010, TC 7060, TC 7080, TC 7070, TC 7082 and TC 7120
4.7
Other test procedures

TP7 To test if the SPINGRID system has the properties described in [URD, section 4.1, 4.2 and 4.9] Perform TC 0020, TC 0030, TC 0040, TC 0050, TC 0080, TC 1010, TC 1020, TC 1030, TC 8030, TC 8040, TC 8050, TC 8060, TC 8070, TC 8080 and TC 8090

360
SPINGRID
34
Chapter 5
Test report
The results of the acceptance tests can be found in [STD].
SPINGRID
35

SpinGrid Testing Documents

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SpinGrid Testing Documents

Загружено:

Авторское право:

Доступные форматы

Software Engineering Project (2IP40)

Acceptance Test Plan

Project Manager: Senior Manager: Advisor: Customer:

Technische Informatica, Eindhoven University of Technology, Eindhoven

Acceptance Test Plan 1.0.0

Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1 1.4.2 Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . .

Acceptance Test Plan 1.0.0

3.6 3.7 3.8 3.9

Acceptance Test Plan 1.0.0

Document Status Sheet

Version 0.0.1 0.0.2 0.0.3 0.0.4 0.0.5 0.1.0 1.0.0

Date 24-01-2006 18-05-2006 21-05-2006 23-05-2006 31-05-2006 31-05-2006 15-06-2006

Author(s) J. Mens R. Leeuwestein R. Leeuwestein R. Leeuwestein R. Leeuwestein R. Leeuwestein J. Mens

Acceptance Test Plan 1.0.0

Document Change Report

Acceptance Test Plan SPINGRID/Documents/product/ATP/1.0.0 N/A

Acceptance Test Plan 1.0.0

Acceptance Test Plan 1.0.0

List of denitions and abbreviations

Client Computational Grid

Role SPINGRID SPINGRID Software SPINGRID System System Administrator

Acceptance Test Plan 1.0.0

Acceptance Test Plan 1.0.0

CHAPTER 2. TEST PLAN

Acceptance test output data. Problem reports (if necessary).

10 clients Dispatcher: Intel Pentium IV 2 GHz or equivalent 2 GB RAM 2 MBit/s network

Acceptance Test Plan 1.0.0

CHAPTER 2. TEST PLAN

Test case pass/fail criteria

Acceptance Test Plan 1.0.0

Test case specications

CHAPTER 3. TEST CASE SPECIFICATIONS

UR 4040 UR 4060 UR 5050 UR 5052 UR 5054

UR 6040 UR 6042 UR 7040 UR 7050 UR 7052

General Requirements Acceptance Tests

TC 0020 acceptance test

Acceptance Test Plan 1.0.0

CHAPTER 3. TEST CASE SPECIFICATIONS

TC 0030 acceptance test

TC 0040 acceptance test

TC 0050 acceptance test

Output Specication Environmental Needs

TC 0080 acceptance test

Acceptance Test Plan 1.0.0

CHAPTER 3. TEST CASE SPECIFICATIONS

Job Requirements Acceptance Tests

TC 1010 acceptance test

Output Specication Environmental Needs

TC 1020a acceptance test

Output Specication Environmental Needs

TC 1020b acceptance test

Output Specication Environmental Needs

Acceptance Test Plan 1.0.0

CHAPTER 3. TEST CASE SPECIFICATIONS

TC 1030 acceptance test

System Admin Requirements Acceptance Tests

TC 2020 acceptance test

Output Specication Environmental Needs

Acceptance Test Plan 1.0.0

CHAPTER 3. TEST CASE SPECIFICATIONS

TC 2100 acceptance test

Output Specication Environmental Needs

TC 2030 acceptance test