BASIL - Master Test Plan

7/31/2019 BASIL - Master Test Plan

1/21

NYSS SOFTWARE SOLUTIONS

Barcoded Assessment System For Independent Learning (BASIL)

Master Test Plan

Version 1.3


2/21

Barcoded Assessment System For Independent Learning (BASIL) Version: 1.3

Master Test Plan Date: 20/11/2010

basil_rup_mtp.docx

Author: Ndumayak Onomo NYSS SOFTWARE

SOLUTIONS, 2012

Page 56

Revision History

Date Version Description Author

05/11/2010 1.1 First draft Ndumayak Onomo

17/11/2010 1.2 Second draft Ndumayak Onomo

20/11/2010 1.3 Third draft Ndumayak Onomo


3/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 57

Table of Contents

1. Introduction 59

1.1 Purpose 591.2 Scope 59

1.3 Intended Audience 591.4 Document Terminology and Acronyms 59

1.5 References 59

2. Evaluation Mission and Test Motivation 59

2.1 Background 60

2.2 Evaluation Mission 602.3 Test Motivators 60

3. Target Test Items 60

4. Outline of Planned Tests 60

4.1 Outline of Test Inclusions 604.2 Outline of Other Candidates for Potential Inclusion 60

4.3 Outline of Test Exclusions 60

5. Test Approach 61

5.1 Initial Test-Idea Catalogs and Other Reference Sources 61

5.2 Testing Techniques and Types 61

5.2.1 Data and Database Integrity Testing 61

5.2.2 Function Testing 615.2.3 Business Cycle Testing Error! Bookmark not defined.

5.2.4 User Interface Testing Error! Bookmark not defined.5.2.5 Performance Profiling Testing 63

5.2.6 Load Testing Error! Bookmark not defined.

5.2.7 Stress Testing5.2.8 Volume Testing

5.2.9 Security And Access Control Testing

5.2.10 Failure And Recovery Testing5.2.11 Configuration Testing

5.2.12 Installation Testing 64

6. Entry and Exit Criteria 65

6.1 Test Plan 67

6.1.1 Test Plan Entry Criteria 68

6.1.2 Test Plan Exit Criteria 686.1.3 Suspension and Resumption Criteria 68


4/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 58

6.2 Test Cycles 68

6.2.1 Test Cycle Entry Criteria 68

6.2.2 Test Cycle Exit Criteria 68

7. Deliverables 68

7.1 Test Evaluation Summaries 687.2 Incident Logs and Change Requests 68

8. Testing Workflow 68

9. Environmental Needs 68

9.1 Base System Hardware 689.2 Base Software Elements in the Test Environment 69

9.3 Productivity and Support Tools 69

10. Responsibilities, Staffing, and Training Needs 70

10.1 People and Roles 70

10.2 Staffing and Training Needs 72

11. Iteration Milestones 73

12. Risks, Dependencies, Assumptions, and Constraints 74

13. Management Process and Procedures 74

13.1 Measuring And Accessing The Extent Of Testing 74

13.2 Assessing the deliverables of this test plan 7413.3 Problem reporting, Escalation, and Issue Resolution

13.4 Managing Test Cycles

13.5 Traceability Strategies13.6 Approval and Signoff 75


5/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 59

Master Test Plan

1. Introduction

The master test plan of the BASIL system involves the test phases, its features and its

performance to the system.

1.1 Purpose

The main objective of this system is to ensure that the workflows satisfies all the project

requirements, and also enable all the components of the system to function according to the

design.

1.2 Scope

The BASIL system will contain the details of individual tests to be run during the testing cycle ofthe system which includes: Unit testing, System testing, Beta testing and Usability testing. This

is to indicate what has been tested, where its not functional, what is to be tested and the ability

to rectify problems. Unit Testing

This is a process whereby individual units of the source codes are tested to determine the

systems efficiency and reliability. This finds problem early in the development of the testing

cycle.

System TestingSystem testing is a method of testing been carried out on a complete system, to ensure that it

corresponds with the system requirements. This involves both the software and the hardware of

the system.

Beta TestingBeta testing in a testing life cycle, is the last stage of testing that is carried out before the

products is been released for commercial purposes. Usability Testing

Usability testing is a technique / method whereby the products are been tested by users. This

gives us a clue of how users use the system ERGONOMICS or interact with the system. Thisis to ensure that the users/ students/ staff will not have any difficulty in using the system.

1.3 Intended Audience

In this section the documents are for the program managers of the system, the stakeholders, thestaff/ students in order to give a detailed guideline as regards the testing phase of the system and

what will be expected in the later iterations.

1.4 Document Terminology and Acronyms

1.5 References

The master test plan for the BASIL system is referenced in the BASIL Use Case Model + Surveydocument authored by Saqib Abbas.

2. Evaluation Mission and Test Motivation


6/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 60

Testing will be carried out primarily to ensure that the BASIL system satisfies all the system

requirements as referenced by the Use Case Model+ Survey document both the functional and

non-functional requirements.

2.1 Background

2.2 Evaluation Mission

The main objective of the testing life cycle phase, is to ensure that the system compatibility,

functionality, accessibility, availability, meets the required standard of the system requirements

in the BASIL system.

2.3 Test Motivators

The testing will be motivated by the desire to ensure that the functional and non-functionalrequirements are met as required by the system requirements and also all the codings are

documented and carried out efficiently to reduce the level of risks outlined in the Risk

Management / Risk List document.3. Target Test Items

The target test items that are to be carried out in the BASIL system includes: software, hardware,

the software to be implemented, and other supporting products that will be identified in the

project as targets for testing. The outline of the list below will be determine what will also betested.

4. Outline of Planned Tests

4.1 Outline of Test Inclusions

The following testing will be carried out in the BASIL system

Functional Testing User Interface Testing Data Integrity Testing Load Testing Performance Profiling Testing Stress Testing Security and Access Control Testing

4.2 Outline of Other Candidates for Potential Inclusion

The following test that is still necessary in the development of the BASIL system which willbe needed in the next iteration is:

Unit Testing4.3 Outline of Test Exclusions

The test that was not deemed fit for the BASIL system was the hardware unit testing. If a


7/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 61

hardware component fails its the responsibility of the supplier to test run the products andchange it were necessary.

5. Test Approach

The tests will be carried out using the Microsofts. Net Platform, this is because it supportsmultiple programming languages in a way that allows language to be able to communicate

and use information which the unit testing will be carried out upon to perform software unit

tests.

5.1 Initial Test-Idea Catalogs and Other Reference Sources

5.2 Testing Techniques and Types

5.2.1Data and Database Integrity TestingTechnique

Objective:

This tests verifies that data are stored in the right location or file to

avoid data corruption and that the data are not invalid.

Technique: Valid and invalid data are inputed into the database using the SQL

server management studio.

Oracles: The output of the data are displayed in the SQL servermanagement studio.

Required Tools: The tools required are:

SQL server management studio Data generation tool

Success Criteria: The database provides the expected output of data without any data

corruption.

Special

Considerations:

Will be considered for each iteration phase.

5.2.2 Function Testing


8/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 62

Technique

Objective:

Test verifies that the system works correctly according to its

expected requirements.

Technique: This is done by implementing the use case models and functions todetermine the expected result of the system:

If data is invalid then there is an error that needs to becorrected.

If data is valid then the system proceeds to its nextiteration phase.

Oracles: Tests the data to verify that system functions properly.

Required Tools: Data Generation Tools

Success Criteria: System is functioning well and all errors has been detected and

corrected.

SpecialConsiderations:

None

5.2.3Business Cycle TestingTechnique

Objective:

Verifies how the products can be marketed

To convince users about the products reliability.

Technique: Online Advertisements. Handbills and Posters. Television Adverts. Marketing group that will move around to display the

products.

Oracles:

Required Tools:

Success Criteria: Enables the product to be marketed successfully.

Special

Considerations:

Must consider the psychology, physiology and the awareness of

the people in a specific geographical area.

5.2.4 User Interface Testing


9/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 63

Technique

Objective:

Tests the system to observe how human interacts with the user

interface of the system to ensure that the system is useful andusable.

Technique: Gathering a group of users and observing how they interact with

the system by giving them specific tasks to perform.

Oracles:

Required Tools: Computer System.

Success Criteria: System is understandable and easy to use by the users.

Special

Considerations:

Those that are disabled, with color blindness, wheel chair,

clutches will be considered in designing the system.

5.2.5 Performance Profiling TestingTechniqueObjective:

Verifies the run-time performance of the software in the BASILsystem to ensure that the software provides the required function.

Technique: Imputing values into each of the Use case models specified in theuse case document to determine the time it takes the system to a

specific task or action.

Oracles:

Required Tools: Stop watch. Test Script Tool Microsoft SQL Profiler

Success Criteria: The runtime to perform a particular task.

Special

Considerations:

Review the results of the test in each iteration.

5.2.6Load Testing


10/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 64

Technique

Objective:

This measures the response of the system and tests the system

work under loading.

Technique: Function tests occurs mostly in this phase implementing testprocedures and scripts in other to determine how the system will

function when more users are on it at the same time, testing the

systems CPU load and database load.

Oracles:

Required Tools: Test Script Tools

Data Generation Tools

Success Criteria: Tests to ensure that the system can function under much workloadgiven to it to perform at a particular.

SpecialConsiderations:

To determine the systems reliability tests must be carriedout on the main system server to deliver the expectedoutput.

5.2.7 Stress TestingTechnique

Objective:

Verifies the parts of the system that is malfunctioning such as: maximum

number of data to be imputed, systems maximum memory capacity, and

which of the operating system that is used.

Technique: Stress tests can be performed by doing simple multi tasking tests.

Each tests will be conducted repeatedly to correct stress defects inthe system.

Inputting heavy amount of data within a specific short period oftime.

Oracles: Multiple tasking jobs carried out by the users on the internet at the sametime.

RequiredTools:

Data Generation Tool

Test Script Automation Tool

SuccessCriteria:

Displays how the system can manage a volume of data at a given time toperform a task.

SpecialConsideration

Stress testing should be carried out early enough in the developmentprocess to spot out defects and correct them in the system.


11/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 65

5.2.8 Volume Testing

Technique

Objective:

This test ensures that the system is able to accumulate high amount

/volume of data in the BASIL system at a specific time whenperforming a particular task.

Technique: Multiple users may be allowed to access the system at the same

time to test the system maximum/ minimum character size andvolume in the system for an extended period.

Oracles:

Required Tools: Data Generation Tool

Test Script Automation Tool

Installation-monitoring tools such as: hard disk, CPU, memory,

etc.

Success Criteria: High amount of data are inputted into the BASIL system to see if

the system can handle the volume of data inputted into it.

Special

Considerations:

5.2.9 Security And Access Control Testing

Technique

Objective:

This is mainly implemented to enhance file integrity and

confidentiality with the use of usernames and passwords.

Technique: A platform that specifies what users are supposed to do and what

they are not to do on a system that is signing in as an authenticateduser.

Oracles: Unauthorized users are not denied access to the system.

Required Tools: Test Automation Tool

Success Criteria: Ensures data prevention and integrity from unauthorized users.

Special

Considerations:


12/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 66

5.2.10 Failover And Recovery Testing

Technique

Objective:

This ensures the system ability to recover from a software /

hardware failure.

Technique: Back up of data due to systems failures. Retrieval of data when system is outdated. Verifying that all the data in the system where completely

restored during maintenance or error recovery.

Oracles:

Required Tools: Installation monitoring tools such as hard disk, removable disks,

CD Rom,etc.

Success Criteria: Ensures data protection and recovery.

Special

Considerations:

Data must be backed up after each iteration phase as documented

in the use case document.

5.2.11 Configuration Testing

Technique

Objective:

Verifies that the system works correctly using different system

configurations like software, hardware and network.

Technique: Testing the systems compatibility using differentsystem softwares.

Test the system to ensure it matches with the hardwarecomponents of the system.

Oracles: Determines the effect of adding or upgrading hardware

components; for example memory, disk and tape resources.

Required Tools:

Success Criteria: Ensures the effect of configuration changes and its performance inthe system.


13/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 67

Special

Considerations:

Configure the system to enhance its compatibility to avoid defect

in the system.

5.2.12 Installation Testing

Technique

Objective:

Verifies the ability of the users to install and set up new software

successfully.

Technique: Upgrading the system software. Re-installation guidelines are also needed to be able to

make the previous system software valid from itsenvironmental conditions.

Oracles:

Required Tools: Installation monitoring tools like hard disk, CPU, memory, etc.

Success Criteria: Ensures that the installation is done successfully and the system is

working well.

Special

Considerations:

The installation process must be done following the mainsteps and guidelines.

Know the environment each installation is supposed towork on.

6. Entry and Exit Criteria

6.1 Test Plan


14/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 68

6.1.1 Test Plan Entry CriteriaAll the requirements testing needed for the development of the software had been outlined, so

therefore the test plan can begin. The required platform/ environment for the test plan to be

conducted has been installed.

6.1.2 Test Plan Exit CriteriaAfter the test plan might have met all the software requirements for the development of the

system and the system is working properly, test plan can be exited. The management staff / team

will confirm the systems effectiveness and then sign to agree that the system has successfullyundergone the testing.

6.1.3 Suspension and Resumption CriteriaTest cycle can only be suspended if errors or defects are found / encountered during the test

life phases and after that when errors are corrected and the system is working properly testingiterations goes to the next phase.

6.2 Test Cycles

6.2.1 Test Cycle Entry CriteriaThe use case document and its requirements as regards the system development is successfuland had been declared complete by the management team for processing.

6.2.2 Test Cycle Exit CriteriaAll the test life cycle phases is completed and the test manager has signed them off forrelease.

7. Deliverables

The outcome of each of the testing phases will give a brief summary and list of how each

testing phases where conducted.

7.1 Test Evaluation Summaries

This section will be completed in each of the iteration phase of the test life cycle.

7.2 Incident Logs and Change Requests

This section deals with the occurrences of damages or problems that might occur in software

development and how they are been verified and corrected like: spoting illegal activitiesgoing on a system, discovering how attacks where been made, and device a change or means

of solving the problem using a different means of how the system is been modified.

8. Testing Workflow

9. Environmental Needs

This section is also referenced in the supplementary specification document authored by Saud

Aljaloud.

9.1 Base System Hardware


15/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 69

The following table sets forth the system resources for the test effort presented in this Test

Plan.

System Resources

Resource Quantity Name and Type

Database Server 1 TBD

Network or Subnet 1 TBD

Server Name NYSS 01 TBD

Database Name BASIL TBD

Client Test PCs 2

Include special configurationrequirements

TBD

Test Repository 1

Network or Subnet TBD

Server Name TBD

Test Development PCs 2 TBD

9.2 Base Software Elements in the Test Environment

The following base software elements are required in the test environment for this Test Plan.

Software Element Name Version Type and Other Notes

Internet Explorer 8.0 Internet Browser

Windows XP SP 2 Operating System

.Net Framework 3.5 Framework

SQL Server 2008 DBMS

Card Reader This electronic device reads

card to retrieve data.

Student ID Card The system receives studentsdata through the card.

9.3 Productivity and Support Tools

The following tools will be employed to support the test process for this Test Plan.


16/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 70

Tool Category or Type Tool Brand Name Vendor or In-house Version

DBMS tools Microsoft SQLmanagement studio

Vendor 2005

Project Management Microsoft project Vendor 2007

10. Responsibilities, Staffing, and Training Needs

10.1 People and Roles

This table shows the staffing assumptions for the test effort.

Human Resources

Role Minimum Resources

Recommended(number of full-time

roles allocated)

Specific Responsibilities or Comments

Test Manager 1 Provides management oversight.

Responsibilities include:

planning and logistics agree mission identify motivators acquire appropriate resources present management reporting advocate the interests of test evaluate effectiveness of test effort

Test Analyst 1 Identifies and defines the specific teststo be conducted.


identify test ideas define test details determine test results document change requests evaluate product quality


17/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 71

Human Resources


Recommended

(number of full-time

roles allocated)


Test Designer 1 Defines the technical approach to the

implementation of the test effort.


define test approach define test automation architecture verify test techniques define testability elements structure test implementation

Tester 2 Implements and executes the tests.


implement tests and test suites execute test suites log results analyze and recover from test

failures

document incidentsTest System

Administrator

1 Ensures test environment and assets are

managed and maintained.


administer test management system install and support access to, and

recovery of, test environmentconfigurations and test labs


18/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 72

Human Resources


Recommended

(number of full-time

roles allocated)


Database

Administrator,

Database Manager

1 Ensures test data (database)

environment and assets are managed

and maintained.


support the administration of testdata and test beds (database).

Designer 1 Identifies and defines the operations,attributes, and associations of the test

classes.


defines the test classes requiredto support testabilityrequirements as defined by the

test team

Implementer 1 Implements and unit tests the testclasses and test packages.


creates the test componentsrequired to support testability

requirements as defined by thedesigner

10.2 Staffing and Training Needs

Staffs that are to be involved in the inception phase of the project includes:

Test Analyst Test Designer Test Manager Test Administrator Test Implementer Database Manager Tester


19/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 73

11. Iteration Milestones

Milestone PlannedStart

Date

ActualStart

Date

PlannedEnd Date ActualEnd Date

Iteration Plan agreed TBD

Iteration starts TBD

Requirements baselined TBD

Architecture baselined TBD

User Interface baselined TBD

First Build delivered to test TBD

First Build accepted into

test

TBD

First Build test cycle

finishes

TBD

[Build Two will not be

tested]

TBD

Third Build delivered to

test

TBD

Third Build accepted intotest

TBD

Third Build test cyclefinishes

TBD

Fourth Build delivered totest

TBD

Fourth Build accepted intotest

TBD

Iteration Assessment

review

TBD

Iteration ends TBD


20/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 74

12. Risks, Dependencies, Assumptions, and Constraints

Risk Mitigation Strateg

Contingency (Risk is

realized)

Testers not

involved early

enough duringdevelopment.

Test not

working as

expected.

Notify the testers on time concerning

a specific project task.

Write out the test plan as required to

meet the system requirements and

start testing early enough.

Have different testers available

in case one of them

disappoints.

Errors are corrected early

enough in the project.

Test harnessdoesnt load thesystem to the

level required

Test the servers to see how muchinformation causes the CPU and

network to start to slow down.

Have more testers available inorder to meet up the standard

requirements of the project.

13. Management Process and Procedures

13.1 Measuring and Assessing The Extent Of Testing

The steps or guidelines that can be initiated in this section using the required tools, programming

languages, required operating system platform, required user interfaces to correct errors whichdetermines the result of the testing.

13.2 Assessing the Deliverables of this Test PlanThe test manager provides management oversight as regards the effectiveness of test effort.

13.3 Problem Reporting, Escalation, and Issue Resolution

If any problem is encountered in the Software development the test manager is to be contacted,then he will pass the information across to the testers of the project to correct any errors and fix

up the problem.

13.4 Managing Test Cycles

The product manager is responsible for every problem that affects compatibility or technical

support costs of the testing phase. What he does he contacts the technical support team, testmanagers, programmers, who supervises the testing staff, review problems and solve them.

13.5 Traceability StrategiesThis section is mainly used by the following departments to ensure projects reliability and theyare:

Test Manager: Accountable for the quality of the testing in the BASIL system. Project Manager: Oversees all the aspects of the project and direct errors to the

departments that are in charge.


21/21



basil_rup_mtp.docx


SOLUTIONS, 2012

Page 75

Programmers: Involves in the coding of the system( detects and corrects errors). Product Manager: gives details of how users interacts o reacts with the system when

working on them.

13.6 Approval and Signoff

This is the responsibility of the test manager/ project manager to approve the testing phase andsign when the test cycles are complete and effective for use

BASIL - Master Test Plan

Documents

Transcript of BASIL - Master Test Plan