BASIL - Master Test Plan

NYSS SOFTWARE SOLUTIONS
Barcoded Assessment System For Independent Learning (BASIL) Master Test Plan Version 1.3
Barcoded Assessment System For Independent Learning (BASIL) Master Test Plan basil_rup_mtp.docx
Version: 1.3 Date: 20/11/2010
Date 05/11/2010 17/11/2010 20/11/2010
Version 1.1 1.2 1.3
Revision History Description First draft Second draft Third draft
Author Ndumayak Onomo Ndumayak Onomo Ndumayak Onomo
Author: Ndumayak Onomo
NYSS SOFTWARE SOLUTIONS, 2012
Page 56
Version: 1.3 Date: 20/11/2010
Table of Contents 1. Introduction 1.1 Purpose 1.2 Scope 1.3 Intended Audience 1.4 Document Terminology and Acronyms 1.5 References Evaluation Mission and Test Motivation 2.1 Background 2.2 Evaluation Mission 2.3 Test Motivators Target Test Items Outline of Planned Tests 4.1 Outline of Test Inclusions 4.2 Outline of Other Candidates for Potential Inclusion 4.3 Outline of Test Exclusions 59 59 59 59 59 59 59 60 60 60 60 60 60 60 60
2.
3. 4.
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 61 5.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 Testing 5.2.8 Volume Testing 5.2.9 Security And Access Control Testing 5.2.10 Failure And Recovery Testing 5.2.11 Configuration Testing 5.2.12 Installation Testing 64 Entry and Exit Criteria 6.1 Test Plan 6.1.1 Test Plan Entry Criteria 6.1.2 Test Plan Exit Criteria 6.1.3 Suspension and Resumption Criteria
6.
65 67 68 68 68
Page 57
Version: 1.3 Date: 20/11/2010
6.2
Test Cycles 6.2.1 Test Cycle Entry Criteria 6.2.2 Test Cycle Exit Criteria
68 68 68 68 68 68 68 68 68 69 69 70 70 72 73 74 74 74 74
7.
Deliverables 7.1 Test Evaluation Summaries 7.2 Incident Logs and Change Requests Testing Workflow Environmental Needs 9.1 Base System Hardware 9.2 Base Software Elements in the Test Environment 9.3 Productivity and Support Tools Responsibilities, Staffing, and Training Needs 10.1 People and Roles 10.2 Staffing and Training Needs Iteration Milestones Risks, Dependencies, Assumptions, and Constraints Management Process and Procedures 13.1 Measuring And Accessing The Extent Of Testing 13.2 Assessing the deliverables of this test plan 13.3 Problem reporting, Escalation, and Issue Resolution 13.4 Managing Test Cycles 13.5 Traceability Strategies 13.6 Approval and Signoff
8. 9.
10.
11. 12. 13.
75
Page 58
Version: 1.3 Date: 20/11/2010
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 of the 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 Testing System 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 Testing Beta 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. This is 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, the staff/ 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 + Survey document authored by Saqib Abbas. 2. Evaluation Mission and Test Motivation
Author: Ndumayak Onomo NYSS SOFTWARE SOLUTIONS, 2012 Page 59
Version: 1.3 Date: 20/11/2010
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-functional requirements 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 be tested. 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 will be needed in the next iteration is: Unit Testing 4.3 Outline of Test Exclusions The test that was not deemed fit for the BASIL system was the hardware unit testing. If a
Version: 1.3 Date: 20/11/2010
hardware component fails its the responsibility of the supplier to test run the products and change it were necessary. 5. Test Approach The tests will be carried out using the Microsofts. Net Platform, this is because it supports multiple 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.1 Data and Database Integrity Testing Technique Objective: Technique: Oracles: Required Tools: This tests verifies that data are stored in the right location or file to avoid data corruption and that the data are not invalid. Valid and invalid data are inputed into the database using the SQL server management studio. The output of the data are displayed in the SQL server management studio. The tools required are: Success Criteria: Special Considerations: SQL server management studio Data generation tool
The database provides the expected output of data without any data corruption. Will be considered for each iteration phase.
5.2.2 Function Testing
Page 61
Version: 1.3 Date: 20/11/2010
Technique Objective: Technique:
Test verifies that the system works correctly according to its expected requirements. This is done by implementing the use case models and functions to determine the expected result of the system: If data is invalid then there is an error that needs to be corrected. If data is valid then the system proceeds to its next iteration phase.
Oracles: Required Tools: Success Criteria: Special Considerations:
Tests the data to verify that system functions properly. Data Generation Tools System is functioning well and all errors has been detected and corrected. None
5.2.3 Business Cycle Testing Technique Objective: Technique: Verifies how the products can be marketed To convince users about the products reliability. Oracles: Required Tools: Success Criteria: Special Considerations: Enables the product to be marketed successfully. Must consider the psychology, physiology and the awareness of the people in a specific geographical area. Online Advertisements. Handbills and Posters. Television Adverts. Marketing group that will move around to display the products.
5.2.4 User Interface Testing

Version: 1.3 Date: 20/11/2010
Technique Objective: Technique: Oracles: Required Tools: Success Criteria: Special Considerations:
Tests the system to observe how human interacts with the user interface of the system to ensure that the system is useful and usable. Gathering a group of users and observing how they interact with the system by giving them specific tasks to perform.
Computer System. System is understandable and easy to use by the users. Those that are disabled, with color blindness, wheel chair, clutches will be considered in designing the system.
5.2.5 Performance Profiling Testing Technique Objective: Technique: Verifies the run-time performance of the software in the BASIL system to ensure that the software provides the required function. Imputing values into each of the Use case models specified in the use case document to determine the time it takes the system to a specific task or action. Success Criteria: Special Considerations:
Oracles: Required Tools: Stop watch. Test Script Tool Microsoft SQL Profiler
The runtime to perform a particular task. Review the results of the test in each iteration.
5.2.6 Load Testing
Page 63
Version: 1.3 Date: 20/11/2010
This measures the response of the system and tests the system work under loading. Function tests occurs mostly in this phase implementing test procedures 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: Success Criteria: Special Considerations: Test Script Tools Data Generation Tools Tests to ensure that the system can function under much workload given to it to perform at a particular. To determine the systems reliability tests must be carried out on the main system server to deliver the expected output.
5.2.7 Stress Testing Technique Objective: Technique: 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. Stress tests can be performed by doing simple multi tasking tests. Oracles: Required Tools: Success Criteria: Special Consideration
Each tests will be conducted repeatedly to correct stress defects in the system. Inputting heavy amount of data within a specific short period of time.
Multiple tasking jobs carried out by the users on the internet at the same time. Data Generation Tool Test Script Automation Tool Displays how the system can manage a volume of data at a given time to perform a task. Stress testing should be carried out early enough in the development process to spot out defects and correct them in the system.
NYSS SOFTWARE SOLUTIONS, 2012 Page 64
Version: 1.3 Date: 20/11/2010
5.2.8 Volume Testing Technique Objective: Technique: This test ensures that the system is able to accumulate high amount /volume of data in the BASIL system at a specific time when performing a particular task. Multiple users may be allowed to access the system at the same time to test the system maximum/ minimum character size and volume 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: Special Considerations: High amount of data are inputted into the BASIL system to see if the system can handle the volume of data inputted into it.
5.2.9 Security And Access Control Testing Technique Objective: Technique: This is mainly implemented to enhance file integrity and confidentiality with the use of usernames and passwords. 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 authenticated user. Unauthorized users are not denied access to the system. Test Automation Tool Ensures data prevention and integrity from unauthorized users.
Oracles: Required Tools: Success Criteria: Special Considerations:
Page 65
Version: 1.3 Date: 20/11/2010
5.2.10
Failover And Recovery Testing This ensures the system ability to recover from a software / hardware failure. 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: Success Criteria: Special Considerations: Installation monitoring tools such as hard disk, removable disks, CD Rom,etc. Ensures data protection and recovery. Data must be backed up after each iteration phase as documented in the use case document.
5.2.11 Configuration Testing Technique Objective: Technique: Verifies that the system works correctly using different system configurations like software, hardware and network. Oracles: Required Tools: Success Criteria: Ensures the effect of configuration changes and its performance in the system. Testing the systems compatibility using different system softwares. Test the system to ensure it matches with the hardware components of the system.
Determines the effect of adding or upgrading hardware components; for example memory, disk and tape resources.
Page 66
Version: 1.3 Date: 20/11/2010
Special Considerations:
Configure the system to enhance its compatibility to avoid defect in the system.
5.2.12 Installation Testing Technique Objective: Technique: Verifies the ability of the users to install and set up new software successfully. Upgrading the system software. Re-installation guidelines are also needed to be able to make the previous system software valid from its environmental conditions.
Oracles: Required Tools: Success Criteria: Special Considerations: Installation monitoring tools like hard disk, CPU, memory, etc. Ensures that the installation is done successfully and the system is working well. The installation process must be done following the main steps and guidelines. Know the environment each installation is supposed to work on.
6. Entry and Exit Criteria 6.1 Test Plan

Version: 1.3 Date: 20/11/2010
6.1.1 Test Plan Entry Criteria All 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 Criteria After 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 successfully undergone the testing. 6.1.3 Suspension and Resumption Criteria Test 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 testing iterations goes to the next phase. 6.2 Test Cycles 6.2.1 Test Cycle Entry Criteria The use case document and its requirements as regards the system development is successful and had been declared complete by the management team for processing. 6.2.2 Test Cycle Exit Criteria All the test life cycle phases is completed and the test manager has signed them off for release. 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 activities going 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
Version: 1.3 Date: 20/11/2010
The following table sets forth the system resources for the test effort presented in this Test Plan. System Resources Resource Database Server Network or Subnet Server Name Database Name Client Test PCs Include special configuration requirements Test Repository Network or Subnet Server Name Test Development PCs 2 1 TBD TBD TBD 1 1 NYSS 01 BASIL 2 TBD Quantity TBD TBD TBD TBD Name and Type
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 Internet Explorer Windows XP .Net Framework SQL Server Card Reader Student ID Card Version 8.0 SP 2 3.5 2008 Type and Other Notes Internet Browser Operating System Framework DBMS This electronic device reads card to retrieve data. The system receives students data through the card.
9.3 Productivity and Support Tools The following tools will be employed to support the test process for this Test Plan.
Version: 1.3 Date: 20/11/2010
Tool Category or Type DBMS tools Project Management
Tool Brand Name Microsoft SQL management studio Microsoft project
Vendor or In-house Vendor Vendor
Version 2005 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) Test Manager 1 Provides management oversight. Responsibilities include: Test Analyst 1 planning and logistics agree mission identify motivators acquire appropriate resources present management reporting advocate the interests of test evaluate effectiveness of test effort Specific Responsibilities or Comments
Identifies and defines the specific tests to be conducted. Responsibilities include: identify test ideas define test details determine test results document change requests evaluate product quality
Page 70
Version: 1.3 Date: 20/11/2010
Human Resources Role Minimum Resources Recommended (number of full-time roles allocated) Test Designer 1 Defines the technical approach to the implementation of the test effort. Responsibilities include: Tester 2 define test approach define test automation architecture verify test techniques define testability elements structure test implementation Specific Responsibilities or Comments
Implements and executes the tests. Responsibilities include: implement tests and test suites execute test suites log results analyze and recover from test failures document incidents
Test System Administrator
Ensures test environment and assets are managed and maintained. Responsibilities include: administer test management system install and support access to, and recovery of, test environment configurations and test labs
Page 71
Version: 1.3 Date: 20/11/2010
Human Resources Role Minimum Resources Recommended (number of full-time roles allocated) Database Administrator, Database Manager 1 Ensures test data (database) environment and assets are managed and maintained. Responsibilities include: Designer 1 support the administration of test data and test beds (database). Specific Responsibilities or Comments
Identifies and defines the operations, attributes, and associations of the test classes. Responsibilities include: defines the test classes required to support testability requirements as defined by the test team
Implementer
Implements and unit tests the test classes and test packages. Responsibilities include: creates the test components required to support testability requirements as defined by the designer
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
Version: 1.3 Date: 20/11/2010
11. Iteration Milestones Milestone Planned Start Date TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD TBD Actual Start Date Planned End Date Actual End Date
Iteration Plan agreed Iteration starts Requirements baselined Architecture baselined User Interface baselined First Build delivered to test First Build accepted into test First Build test cycle finishes [Build Two will not be tested] Third Build delivered to test Third Build accepted into test Third Build test cycle finishes Fourth Build delivered to test Fourth Build accepted into test Iteration Assessment review Iteration ends
Page 73
Version: 1.3 Date: 20/11/2010
12. Risks, Dependencies, Assumptions, and Constraints Risk Testers not involved early enough during development. Mitigation Strateg Notify the testers on time concerning a specific project task. Contingency (Risk is realized) Have different testers available in case one of them disappoints.
Test not working as expected. Test harness doesnt load the system to the level required
Write out the test plan as required to meet the system requirements and start testing early enough. Test the servers to see how much information causes the CPU and network to start to slow down.
Errors are corrected early enough in the project. Have more testers available in order 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 which determines the result of the testing. 13.2 Assessing the Deliverables of this Test Plan The 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, test managers, programmers, who supervises the testing staff, review problems and solve them. 13.5 Traceability Strategies This section is mainly used by the following departments to ensure projects reliability and they are: 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.
Version: 1.3 Date: 20/11/2010
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 and sign when the test cycles are complete and effective for use
Page 75

BASIL - Master Test Plan

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

BASIL - Master Test Plan

Cargado por

Copyright:

Formatos disponibles

NYSS SOFTWARE SOLUTIONS

Version: 1.3 Date: 20/11/2010

Date 05/11/2010 17/11/2010 20/11/2010

Version 1.1 1.2 1.3

Revision History Description First draft Second draft Third draft

Author Ndumayak Onomo Ndumayak Onomo Ndumayak Onomo

Author: Ndumayak Onomo

NYSS SOFTWARE SOLUTIONS, 2012

Version: 1.3 Date: 20/11/2010

Author: Ndumayak Onomo

Version: 1.3 Date: 20/11/2010

11. 12. 13.

Author: Ndumayak Onomo

NYSS SOFTWARE SOLUTIONS, 2012

Version: 1.3 Date: 20/11/2010

Version: 1.3 Date: 20/11/2010

Version: 1.3 Date: 20/11/2010

5.2.2 Function Testing

Author: Ndumayak Onomo

NYSS SOFTWARE SOLUTIONS, 2012

Version: 1.3 Date: 20/11/2010

Technique Objective: Technique:

Oracles: Required Tools: Success Criteria: Special Considerations:

5.2.4 User Interface Testing

Version: 1.3 Date: 20/11/2010

5.2.6 Load Testing

Author: Ndumayak Onomo

NYSS SOFTWARE SOLUTIONS, 2012

Version: 1.3 Date: 20/11/2010

Technique Objective: Technique:

Version: 1.3 Date: 20/11/2010

Oracles: Required Tools: Success Criteria: Special Considerations:

Author: Ndumayak Onomo

NYSS SOFTWARE SOLUTIONS, 2012

Version: 1.3 Date: 20/11/2010

Technique Objective: Technique:

Author: Ndumayak Onomo

NYSS SOFTWARE SOLUTIONS, 2012

Version: 1.3 Date: 20/11/2010

6. Entry and Exit Criteria 6.1 Test Plan

Version: 1.3 Date: 20/11/2010

Version: 1.3 Date: 20/11/2010

Version: 1.3 Date: 20/11/2010

Tool Category or Type DBMS tools Project Management

Tool Brand Name Microsoft SQL management studio Microsoft project

Vendor or In-house Vendor Vendor

Version 2005 2007

Author: Ndumayak Onomo

NYSS SOFTWARE SOLUTIONS, 2012

Version: 1.3 Date: 20/11/2010

Test System Administrator

Author: Ndumayak Onomo

NYSS SOFTWARE SOLUTIONS, 2012

Version: 1.3 Date: 20/11/2010

Version: 1.3 Date: 20/11/2010

Author: Ndumayak Onomo

NYSS SOFTWARE SOLUTIONS, 2012

Version: 1.3 Date: 20/11/2010

Version: 1.3 Date: 20/11/2010

Author: Ndumayak Onomo

NYSS SOFTWARE SOLUTIONS, 2012

También podría gustarte