5/12/2013

TEST PLAN IIT WEBSITE

Submitted to MUKSITUL M. TANIM HASAN (BSSE 0301) MD. SHIBBIR HOSSAIN (BSSE 0317)

Submitted to MOHAMMAD ASHIK ELAHI

1 | P a g e

Contents 1 Test Identifier .................................................................................................................................. 3

2 Reference ........................................................................................................................................ 3

3 Introduction .................................................................................................................................... 4

4 Test items ........................................................................................................................................ 5

4.1 Cross Checking the specifications ............................................................................................. 5

4.2 Interface & design specification ............................................................................................... 5

4.3 User Attendant ........................................................................................................................ 6

4.3.1 Questionnaire................................................................................................................... 6

4.4 Operation Guide ...................................................................................................................... 6

4.5 Verification & Validation Plan ................................................................................................... 6

5 Software risk issues ......................................................................................................................... 7

5.1 Product size risk ....................................................................................................................... 7

5.2 Business impact risk ................................................................................................................. 7

5.3 Customer Related Risk ............................................................................................................. 7

5.4 Development Environment Risks .............................................................................................. 8

5.5 Process Issue risk ..................................................................................................................... 8

5.6 Staff size & risk ......................................................................................................................... 8

5.7 Technical Issue Risk .................................................................................................................. 8

5.8 Technology Risk ....................................................................................................................... 9

5.9 Other Potential Risk ................................................................................................................. 9

6 FEATURES TO BE TESTED................................................................................................................ 10

6.1 External management ............................................................................................................ 10

6.2 Student management............................................................................................................. 10

6.3 Batch management ................................................................................................................ 10

6.4 Exam Management ................................................................................................................ 10

6.5 Course management .............................................................................................................. 10

6.6 Faculty management .............................................................................................................. 10

6.7 Teacher module ..................................................................................................................... 11

6.8 Profile management ............................................................................................................... 11

7 Features not to be tested............................................................................................................... 12

7.1 Authentication Module .......................................................................................................... 12

2 | P a g e

7.2 Database design ..................................................................................................................... 12

7.3 UI components ....................................................................................................................... 12

8 Approach ....................................................................................................................................... 13

8.1.1 Test tools ........................................................................................................................ 14

9 Item/Pass fail criteria ..................................................................................................................... 15

10 SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS ....................................................... 15

10.1 Suspension criteria ................................................................................................................. 15

10.2 Resumption Requirements ..................................................................................................... 15

11 Test Deliverables........................................................................................................................ 16

12 Remaining Test Tasks ................................................................................................................. 17

13 Environmental Needs ................................................................................................................. 17

14 Staffing and training Needs ........................................................................................................ 18

14.1 Staffs ...................................................................................................................................... 18

14.2 Training needs........................................................................................................................ 18

14.3 Trainer ................................................................................................................................... 18

15 Responsibilities .......................................................................................................................... 19

16 Schedule .................................................................................................................................... 21

17 Planning risk and contingencies ................................................................................................. 21

17.1 Time limitation ....................................................................................................................... 21

17.2 Lack of Expertise .................................................................................................................... 21

17.3 Lack of human resource ......................................................................................................... 21

17.4 Lack Hardware: ...................................................................................................................... 21

18 Approval .................................................................................................................................... 22

19 Glossary ..................................................................................................................................... 23

3 | P a g e

Test Plan

1 TEST IDENTIFIER

ITCMS101

2 REFERENCE

SRS Documentation of IIT Website

User requirements & questionnaire

www.seeedstudio.com/

austin.iiba.org/download/utp.doc

http://www.softwaretestinghelp.com

www.computing.dcu.ie/~davids/courses/CA267/ieee829mtp.pdf

http://msdn.microsoft.com/en-us/library/vstudio/dd286583(v=vs.110).aspx

4 | P a g e

3 INTRODUCTION

The system Test Plan has been developed to plan overall test strategy for IIT Website. It is also

implemented to evaluate the quality of IIT website. Mitigating the risk issues and contingencies

of the project Test plan is essential. Whole system is sub divided into modules; so this test plan

is designed in such a way that its whole approach and strategy ensure the integration of the

modularity. The point toward all testing activities, therefore, will be to exercise the complete

integrated functioning of the system and will include Test items (module, sub module, all types

of Management and all CMS), software functionality, User Interface and etc. Project Test plan

scope and the features which will be tested or not be tested, the whole thing is also included on

the Test Plan. Item/pass fail benchmarks, suspension guidelines and environmental

requirements is described precisely on this documentation.

5 | P a g e

4 TEST ITEMS

Things that are to be tested on this test plan is included here.

4.1 CROSS CHECKING THE SPECIFICATIONS

Here the functionality and modularity will be tested for the depicted system

• FACULTY MANAGEMENT

• STUDENT MANAGEMENT

• EXAM MANAGEMENT

• ADMISSION MANAGEMENT

• INTERNAL MANAGEMENT

• WEBSITE MANAGEMENT

• ADMIN MANAGEMENT

• PROGRAM MANAGEMENT

As per Quality assurance comes out, we will meet up certain demands.

User friendly collaboration

Augmented surfing capability

Security issues should be ensured for Admin management

4.2 INTERFACE & DESIGN SPECIFICATION

Following items will be tested to safeguard the quality of interface and meet up the design specification.

Browser compatibility issue

CSS issue

Pop ups and other web elements

6 | P a g e

4.3 USER ATTENDANT

On this section the user’s flexibility and usability will be tested along with the scalability issues also.

Some questionnaire can be listed for defining the test items for this segment. Prerequisites for User

Guide test items would be the users of the IIT website. As per our SRS documentation we identify the

below listed user-

Teacher

Student

Admin

Exam Committee

External visitors

4.3.1 Questionnaire

• Does any laying-off overcome in the system in terms of user communication?

• Is there is any difficulty can arise when user attendant will try to surf the website?

• Is functionality is satisfactory with all types user?

• Usability is efficient?

4.4 OPERATION GUIDE

On this segment the functionality of the website will be tested also the operations that are functioned in

every aspect of the system will also be tested. With a set of questionnaire and user acceptance this test

items can be defined.

4.5 VERIFICATION & VALIDATION PLAN Some set of valid inputs and outputs should be enlisted for verification and validation for the system.

These test items is pretty much essential for specification based testing. So there should be a plan for

identifying the inputs and expected result. BVA (Boundary Value Analysis) can be done to guarantee the

verification and validation with set of pairs.

7 | P a g e

5 SOFTWARE RISK ISSUES

We identify some project risk issues. Different types of risk can be arise in devolving a project. Issues

that is enlisted is given below. With set of questionaries’ we will figure out the project and software risk

issues.

5.1 PRODUCT SIZE RISK

• Size of database created or used by the product?

• Probable size of the product in LOC?

• Degree of assurance in estimated size estimate?

• Predictable size of product in number of programs, files, transactions?

• Percentage nonconformity in size of product from average for previous products?

5.2 BUSINESS IMPACT RISK

• If Admission Process is introduced then our project can be failed as per we assume the load

to a certain level. But on this occasion thread will be at its high. This sort of new feature can

affect the business impact of the project.

• IF new requirements came up with paradigm shift or business redesign came with new

feature can really hurt the project

• Rationality of delivery deadlines?

• Number of customers who will use this product and the consistency of their needs relative

to the product?

• Sophistication of end users?

5.3 CUSTOMER RELATED RISK

• Have you worked with the customer in the past?

• Does the customer have a solid idea of what is required?

• Has the customer taken the time to write this down?

• Will the customer agree to spend time in formal requirements gathering meetings to

identify project scope?

8 | P a g e

5.4 DEVELOPMENT ENVIRONMENT RISKS

Are compilers or code generators available and appropriate for the product to be built? Are testing tools available and appropriate for the product to be built? Are software configuration management tools available? Does the environment make use of a database or repository? Are all the software tools integrated with one another? Have members of the project teams received training in each of the tools? Are local experts available to answer questions about the tools? Is on-line help and documentation for the tools adequate?

5.5 PROCESS ISSUE RISK

Have document outlines and examples been developed for all deliverables defined as part of the project process?

Are formal technical reviews of the requirements specification, design, and code conducted regularly? Are the results of each formal technical review documented, including defects found and resources used?

5.6 STAFF SIZE & RISK

• We develop our project with whole 3rd batch so if any of our member were not present on

the project , then it could be risk issue for the project

• Are the best people available?

• Do the people have the right combination of skills?

• Are enough people available?

5.7 TECHNICAL ISSUE RISK

• Do you use a specific method for test case design?

• Are software tools used to support software planning and tracking activities?

• Are configuration management software tools used to control and track change activity

throughout the software process?

• Are software tools used to support the software analysis and design process?

• Are tools used to create software prototypes?

• Are software tools used to support the testing process?

• Are software tools used to support the production and management of documentation?

9 | P a g e

5.8 TECHNOLOGY RISK

Do requirements put excessive performance constraints on the product? Is the customer uncertain that the functionality requested is "do-able"?

5.9 OTHER POTENTIAL RISK

• Inefficient team structure reduces productivity

• Management review/decision cycle is slower than expected

• Budget cuts upset project plans

• Are the best people available

• Do the people have the right kind of skills

10 | P a g e

6 FEATURES TO BE TESTED

6.1 EXTERNAL MANAGEMENT i. News, events

ii. Programs

iii. Notice Board

iv. Education Archive

v. Achievements etc.

6.2 STUDENT MANAGEMENT i. Add Student

ii. Delete Student

iii. Manage Student

6.3 BATCH MANAGEMENT i. Batch creation

ii. Batch modification

iii. Integration

6.4 EXAM MANAGEMENT i. Exam dashboard

ii. Create Exam

iii. Delete exam

iv. Publish exam results

v. Exam notification

6.5 COURSE MANAGEMENT i. Course create, edit , modify

ii. Delete course

iii. Manage course

6.6 FACULTY MANAGEMENT i. Faculty create, edit, delete

ii. Batch manage

iii. Course manage

iv. Change course

11 | P a g e

6.7 TEACHER MODULE i. Attendance management

ii. Assignment management

6.8 PROFILE MANAGEMENT

i. Manage profile

ii. Upload photo

iii. Edit info

12 | P a g e

7 FEATURES NOT TO BE TESTED

7.1 AUTHENTICATION MODULE IIT Website is built on the framework called “CodeIgniter”. In” CodeIgniter” authentication and

security measures are handled automatically by the framework itself. So we will not test the

authentication module.

7.2 DATABASE DESIGN Our whole project is based on the primary design of our relational database. It is designed

cautiously. If we change the design at the phase of testing evaluation then project risks

increases. So we will not test database design feature.

7.3 UI COMPONENTS Design and templates will not be tested

13 | P a g e

8 APPROACH

Our project “IIT Website” will consist of following testing

1. Functionality testing

2. Data and Database Integrity Testing

3. Unit Testing

4. Acceptance Testing

5. Load Testing

6. Performance Testing

Our tests will be done by Testing team with the help of the Development team. How we will be

doing these tests is illustrated below.

1. Functionality testing

We will do Functionality testing in five steps.

i. The identification of functions that the software is expected to perform

ii. The creation of input data based on the function’s specifications

iii. The determination of output based on the function’s specification

iv. The execution of the test case

v. The comparison of actual and expected outputs

2. Data and Database Integrity Testing

Data integrity refers to maintaining and assuring the accuracy and consistency

of data over its entire life-cycle. Here we will verify all simultaneous CRUD operations.

3. Unit Testing

During the development phase the Development team will ensure that all code snippets

are unit testable. Unit testing information will be passed to the test team.

4. Acceptance Testing

This is a validation activity. We ask some questions here.

i. Did we build the right thing?

ii. Is this what the customer really needs?

Test will be performed by the actual end users with the assistance of the test manager and

development team leader.

5. Performance Testing

i. Verify response time of the external management system

ii. Verify loading time of the Homepage

iii. Verify response time to access external management system.

14 | P a g e

6. Load Testing

We will do load testing to determine system’s behavior under both normal and

anticipated peak load

conditions. Here our goal is to

i. How much user’s load our system can take using different load each time.

ii. Sending requests from different users at the same time from different

operating environment and evaluate test result.

8.1.1 Test tools

The tools that test team will be using for the above mentioned tests are

• Visual Studio

• Bugzilla

• Mantis

• Git: version control

• Various types of browser with various versions like IE -9, IE-10, Chrome, Mozilla

Firefox, Safari etc.

15 | P a g e

9 ITEM/PASS FAIL CRITERIA

This section of the test plan describes the pass/fail criteria for each of the items that we described

in Test items.

Our Pass/Fail criteria for System testing are given below.

80% of the test cases must pass

All test cases dealing with critical functionality must pass

All medium and high severity defects must be fixed

Test coverage must be at least 80%

10 SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS

10.1 SUSPENSION CRITERIA

1. IF any requirements added and feature also then testing will be suspended until the

resumption requirements met up.

2. If any requirements is been deleted then the testing will be suspended as development is

done it agile methodology

10.2 RESUMPTION REQUIREMENTS

1. New requirements specified

2. Approved by project manager

16 | P a g e

11 TEST DELIVERABLES

The deliverables of the Test Plan are outlined in the table below.

Deliverable

Owner Review/Distribution Due Date

Test Plan

Project Manager 20 November

Test Environment

- 22 November

Test Suite

Internal Peer review

23 November

Test Data Sets

Internal Peer review

24 November

Test Scripts

Internal Peer review

25 November

Test Defect Report

Project Manager 28 November

Test Results

-

30 November

Test Evaluation Report

Project Manager 4 December

17 | P a g e

12 REMAINING TEST TASKS

Task Assigned To Status

Data Integration Acceptance level Test Teams,PM,Developer

Module wise acceptance Test Teams,Dev

Whole system(Integrated of modules) acceptance

Test Teams

Verify Test report Dev, Client, TM

Select the Acceptance Percentage value Project Manager

13 ENVIRONMENTAL NEEDS

In order maintain external website and internal management we need some environmental

support

• Full Software Requirement Specification Document.

• Access to both the development and current official processes of IIT.

• Good Communication facility.

• Details of every existing processes.

• Full Software Requirement Specification Document.

• Access to the central database.

18 | P a g e

14 STAFFING AND TRAINING NEEDS

As our project is pretty much heavy we need staffing and training as per project demands

14.1 STAFFS

• Two tester.

• On testing period few others tester can be included.

14.2 TRAINING NEEDS

• Selenium (browser compatibility test)

• Visual Studio (load test)

• PHP Storm (Code Test)

• Bugzilla (bug tracking system)

14.3 TRAINER Mohammad Ashik Elahi

IIT DU

19 | P a g e

15 RESPONSIBILITIES

This table is suggesting who are responsible for which testing.

Detailed responsibilities of Test Manager and Test team are illustrated below.

Role

Responsibilities

Test Manager . Write Test Plan

· Maintenance of Test plan

· Monitoring Test Progress

· Monitoring Adherence to Test Plan.

· Decision making about entry and exit to and

from a testing stage.

· Decision making about suspension /

resumption of testing.

· Any change in test strategy / amendments in

test plan.

Tasks TM PM Dev Team

Test Team

Client

Acceptance test Documentation & Execution X X X X

Unit test documentation & Execution X X X

System Design Reviews X X X X X

Detail Design Reviews X X X X

Test procedure and rules X X X X

Change Control and regression testing X X X X X

20 | P a g e

Test Lead · Coordination of test team.

· Representation of testing team in various

meeting.

· Generating various reports and matrices.

· Risk identification, analysis and mitigation

· Reporting updates to Test Manager about

testing progress, any issues being faced and

risk identified.

Testers · Write / Execute test cases for other than

functional test cases (i.e. test cases for other

than functional testing regression testing,

scenario based testing, and end to end

functional testing)

· Find, report and track errors discovered

during system testing

· Analyze results

· Perform Compliance check to coding

standards, Help Navigation Testing, User

Experience and Usability Testing, Performance

Testing, Localization Testing, platform

Compatibility testing, Extensibility testing,

Backup and Restore testing, Installation

testing.

21 | P a g e

16 SCHEDULE

Milestone Task

Effort/s Start Date End Date

Test Planning

2 November 12 November 17

Test Design

4 November 17 November 19

Test Development

1 November 20 November 21

Test Execution

2 November 22 November 24

Test Evaluation

1 November 25 November 25

17 PLANNING RISK AND CONTINGENCIES

17.1 TIME LIMITATION Total testing process must be done inside a certain time borderline. For these reason task should

be done in due time; otherwise catching up with milestone would risky enough.

17.2 LACK OF EXPERTISE

As we said earlier that staffing and training is needed we gain the experience level along with

achieving expertise. The whole project development team as well as the testing team consists of

novice software engineering student.

17.3 LACK OF HUMAN RESOURCE

Number of active testers are very low in the testing team.

17.4 LACK HARDWARE:

More compatible hardware and speedy data connection is needed to run the load test.

22 | P a g e

18 APPROVAL

Role Name Signature

Client

Dr. Mahabubul Alam Joarder

Test Director

Mohammad Ashik Elahi

Project Manager

Asif Imtiaz

Database Manager Md. Irfaan

Head of Development Upal Roy

Test Team Leader

Tanim Hasan

23 | P a g e

19 GLOSSARY

1. Unit testing

In computer programming, unit testing is a method by which individual units of source

code, sets of one or more computer program modules together with associated control

data, usage procedures, and operating procedures are tested to determine if they are fit for

use.

2. CodeIgniter

CodeIgniter is an open source rapid development web application framework, for use in

building dynamic web sites with PHP

3. Framework

A software framework is an abstraction in which software providing generic functionality

can be selectively changed by additional user-written code, thus providing application-

specific software.

4. Bugzilla

Bug tracking used by the Mozilla projects

5. CMS

Content management system

6. Mantis

A popular free web-based bug tracking system

Reference:

www.wikipedia.org

www.mantisbt.org

http://www.bugzilla.org/