SlideShare a Scribd company logo
1 of 24
Download to read offline
5/12/2013

TEST PLAN
IIT WEBSITE

Submitted to
MOHAMMAD ASHIK ELAHI

Submitted to
MUKSITUL M. TANIM HASAN (BSSE 0301)
MD. SHIBBIR HOSSAIN (BSSE 0317)
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
4.5
5

Operation Guide ...................................................................................................................... 6
Verification & Validation Plan ................................................................................................... 6

Software risk issues ......................................................................................................................... 7
5.1
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
6

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

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

FEATURES TO BE TESTED................................................................................................................ 10
6.1
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
7

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

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

Features not to be tested............................................................................................................... 12
7.1

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

1|P ag e
7.2

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

7.3

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

8

Approach ....................................................................................................................................... 13
8.1.1

9

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

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

2|P ag 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

3|P ag 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.

4|P ag 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

5|P ag 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




4.3.1

Teacher
Student
Admin
Exam Committee
External visitors
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.

6|P ag 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
•
•
•
•

7|P ag e

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?
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
•
•
•
•
•
•
•

8|P ag e

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?
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
•
•
•
•
•

9|P ag e

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
6 FEATURES TO BE TESTED
6.1 EXTERNAL MANAGEMENT
i.
ii.
iii.
iv.
v.

News, events
Programs
Notice Board
Education Archive
Achievements etc.

6.2 STUDENT MANAGEMENT
i.
ii.
iii.

Add Student
Delete Student
Manage Student

6.3 BATCH MANAGEMENT
i.
ii.
iii.

Batch creation
Batch modification
Integration

6.4 EXAM MANAGEMENT
i.
ii.
iii.
iv.
v.

Exam dashboard
Create Exam
Delete exam
Publish exam results
Exam notification

6.5 COURSE MANAGEMENT
i.
ii.
iii.

Course create, edit , modify
Delete course
Manage course

6.6 FACULTY MANAGEMENT
i.
ii.
iii.
iv.
10 | P a g e

Faculty create, edit, delete
Batch manage
Course manage
Change course
6.7 TEACHER MODULE
i.
ii.

Attendance management
Assignment management

6.8 PROFILE MANAGEMENT
i.
ii.
iii.

11 | P a g e

Manage profile
Upload photo
Edit info
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

12 | P a g e
8 APPROACH
Our project “IIT Website” will consist of following testing
1.
2.
3.
4.
5.
6.

Functionality testing
Data and Database Integrity Testing
Unit Testing
Acceptance Testing
Load Testing
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.

13 | 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
•
•
•
•
•

14 | P a g e

Visual Studio
Bugzilla
Mantis
Git: version control
Various types of browser with various versions like IE -9, IE-10, Chrome, Mozilla
Firefox, Safari etc.
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

15 | 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
23 November

Test Suite
Internal Peer review

24 November

Test Data Sets
Internal Peer review

25 November

Test Scripts
Internal Peer review
Test Defect Report

Project Manager

28 November
30 November

Test Results
Test Evaluation Report

16 | P a g e

Project Manager

4 December
12 REMAINING TEST TASKS
Task
Data Integration Acceptance level
Module wise acceptance
Whole system(Integrated of modules)
acceptance
Verify Test report
Select the Acceptance Percentage value

Assigned To

Status

Test
Teams,PM,Developer
Test Teams,Dev
Test Teams
Dev, Client, TM
Project Manager

13 ENVIRONMENTAL NEEDS
In order maintain external website and internal management we need some environmental
support
•
•
•
•
•
•

17 | P a g e

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.
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

18 | P a g e
15 RESPONSIBILITIES
This table is suggesting who are responsible for which testing.
Tasks

TM

PM

Acceptance test Documentation & Execution

X

X

Unit test documentation & Execution

X

System Design Reviews

X

Detail Design Reviews

Dev
Team

Test
Team
X

X
X

X

X

X

X

X

Test procedure and rules

X

X

X

X

Change Control and regression testing

X

X

X

X

X

X

X

Client

X

X

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.

19 | 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.

20 | 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.

21 | P a g e
18 APPROVAL
Role
Client

Name
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

22 | P a g e

Signature
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 applicationspecific 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/

23 | P a g e

More Related Content

What's hot

Sample test-plan-template
Sample test-plan-templateSample test-plan-template
Sample test-plan-templateamikdamaru
 
Chapter 4 - Quality Characteristics for Technical Testing
Chapter 4 - Quality Characteristics for Technical TestingChapter 4 - Quality Characteristics for Technical Testing
Chapter 4 - Quality Characteristics for Technical TestingNeeraj Kumar Singh
 
ISTQB - Foundation level testing topics
ISTQB - Foundation level testing topicsISTQB - Foundation level testing topics
ISTQB - Foundation level testing topicsShan Kings
 
Software Testing Life Cycle
Software Testing Life CycleSoftware Testing Life Cycle
Software Testing Life CycleUdayakumar Sree
 
ISTQB / ISEB Foundation Exam Practice - 6
ISTQB / ISEB Foundation Exam Practice - 6ISTQB / ISEB Foundation Exam Practice - 6
ISTQB / ISEB Foundation Exam Practice - 6Yogindernath Gupta
 
What is Test Plan? Edureka
What is Test Plan? EdurekaWhat is Test Plan? Edureka
What is Test Plan? EdurekaEdureka!
 
Strategies For Software Test Documentation
Strategies For Software Test Documentation Strategies For Software Test Documentation
Strategies For Software Test Documentation Vishwak Solution
 
02 software test plan template
02 software test plan template02 software test plan template
02 software test plan templateAndrei Hortúa
 
Đồ Án Tìm Hiểu Phần Mềm Loadrunner Kiểm Tra Hiệu Năng Website
Đồ Án Tìm Hiểu Phần Mềm Loadrunner Kiểm Tra Hiệu Năng Website Đồ Án Tìm Hiểu Phần Mềm Loadrunner Kiểm Tra Hiệu Năng Website
Đồ Án Tìm Hiểu Phần Mềm Loadrunner Kiểm Tra Hiệu Năng Website nataliej4
 
14.project online eamination system
14.project online eamination system14.project online eamination system
14.project online eamination systemjbpatel7290
 
Manual testing interview questions and answers
Manual testing interview questions and answersManual testing interview questions and answers
Manual testing interview questions and answerskaranmca
 
Chapter 5 - Improving the Testing Process
Chapter 5 -  Improving the Testing ProcessChapter 5 -  Improving the Testing Process
Chapter 5 - Improving the Testing ProcessNeeraj Kumar Singh
 
Chapter 4 - Deployment & Delivery
Chapter 4 - Deployment & DeliveryChapter 4 - Deployment & Delivery
Chapter 4 - Deployment & DeliveryNeeraj Kumar Singh
 
Test Plan Simplicity
Test Plan SimplicityTest Plan Simplicity
Test Plan SimplicityJohan Hoberg
 
Chapter 3 - The Generic Test Automation Architecture
Chapter 3 - The Generic Test Automation Architecture Chapter 3 - The Generic Test Automation Architecture
Chapter 3 - The Generic Test Automation Architecture Neeraj Kumar Singh
 
Software testing and process
Software testing and processSoftware testing and process
Software testing and processgouravkalbalia
 

What's hot (20)

Sample test-plan-template
Sample test-plan-templateSample test-plan-template
Sample test-plan-template
 
Chapter 4 - Quality Characteristics for Technical Testing
Chapter 4 - Quality Characteristics for Technical TestingChapter 4 - Quality Characteristics for Technical Testing
Chapter 4 - Quality Characteristics for Technical Testing
 
ISTQB - Foundation level testing topics
ISTQB - Foundation level testing topicsISTQB - Foundation level testing topics
ISTQB - Foundation level testing topics
 
Software Testing Life Cycle
Software Testing Life CycleSoftware Testing Life Cycle
Software Testing Life Cycle
 
ISTQB / ISEB Foundation Exam Practice - 6
ISTQB / ISEB Foundation Exam Practice - 6ISTQB / ISEB Foundation Exam Practice - 6
ISTQB / ISEB Foundation Exam Practice - 6
 
What is Test Plan? Edureka
What is Test Plan? EdurekaWhat is Test Plan? Edureka
What is Test Plan? Edureka
 
Strategies For Software Test Documentation
Strategies For Software Test Documentation Strategies For Software Test Documentation
Strategies For Software Test Documentation
 
Test plan
Test planTest plan
Test plan
 
02 software test plan template
02 software test plan template02 software test plan template
02 software test plan template
 
System testing
System testingSystem testing
System testing
 
Đồ Án Tìm Hiểu Phần Mềm Loadrunner Kiểm Tra Hiệu Năng Website
Đồ Án Tìm Hiểu Phần Mềm Loadrunner Kiểm Tra Hiệu Năng Website Đồ Án Tìm Hiểu Phần Mềm Loadrunner Kiểm Tra Hiệu Năng Website
Đồ Án Tìm Hiểu Phần Mềm Loadrunner Kiểm Tra Hiệu Năng Website
 
14.project online eamination system
14.project online eamination system14.project online eamination system
14.project online eamination system
 
Manual testing interview questions and answers
Manual testing interview questions and answersManual testing interview questions and answers
Manual testing interview questions and answers
 
Chapter 5 - Improving the Testing Process
Chapter 5 -  Improving the Testing ProcessChapter 5 -  Improving the Testing Process
Chapter 5 - Improving the Testing Process
 
Software Testing
Software TestingSoftware Testing
Software Testing
 
Chapter 4 - Deployment & Delivery
Chapter 4 - Deployment & DeliveryChapter 4 - Deployment & Delivery
Chapter 4 - Deployment & Delivery
 
ISTQB Technical Test Analyst 2012 Training - Structure-Based Testing
ISTQB Technical Test Analyst 2012 Training - Structure-Based TestingISTQB Technical Test Analyst 2012 Training - Structure-Based Testing
ISTQB Technical Test Analyst 2012 Training - Structure-Based Testing
 
Test Plan Simplicity
Test Plan SimplicityTest Plan Simplicity
Test Plan Simplicity
 
Chapter 3 - The Generic Test Automation Architecture
Chapter 3 - The Generic Test Automation Architecture Chapter 3 - The Generic Test Automation Architecture
Chapter 3 - The Generic Test Automation Architecture
 
Software testing and process
Software testing and processSoftware testing and process
Software testing and process
 

Viewers also liked

Accessible design with html5 JS Everywhere 2012 Oct 26 Fairmont Hotel San Jos...
Accessible design with html5 JS Everywhere 2012 Oct 26 Fairmont Hotel San Jos...Accessible design with html5 JS Everywhere 2012 Oct 26 Fairmont Hotel San Jos...
Accessible design with html5 JS Everywhere 2012 Oct 26 Fairmont Hotel San Jos...Raj Lal
 
HTML5 Accessibility
HTML5 AccessibilityHTML5 Accessibility
HTML5 AccessibilityUser Vision
 
Real World Web Standards
Real World Web StandardsReal World Web Standards
Real World Web Standardsgleddy
 
Accessibility of HTML5 and Rich Internet Applications - CSUN 2012
Accessibility of HTML5 and Rich Internet Applications - CSUN 2012Accessibility of HTML5 and Rich Internet Applications - CSUN 2012
Accessibility of HTML5 and Rich Internet Applications - CSUN 2012Steven Faulkner
 
Post3 d test plan wk13
Post3 d test plan wk13Post3 d test plan wk13
Post3 d test plan wk13iros321
 
Test Plan for online auction system
Test Plan for online auction systemTest Plan for online auction system
Test Plan for online auction systemKomalah Nair
 
29 Essential AngularJS Interview Questions
29 Essential AngularJS Interview Questions29 Essential AngularJS Interview Questions
29 Essential AngularJS Interview QuestionsArc & Codementor
 
Web 3.0 The Semantic Web
Web 3.0 The Semantic WebWeb 3.0 The Semantic Web
Web 3.0 The Semantic WebHatem Mahmoud
 

Viewers also liked (12)

Accessible design with html5 JS Everywhere 2012 Oct 26 Fairmont Hotel San Jos...
Accessible design with html5 JS Everywhere 2012 Oct 26 Fairmont Hotel San Jos...Accessible design with html5 JS Everywhere 2012 Oct 26 Fairmont Hotel San Jos...
Accessible design with html5 JS Everywhere 2012 Oct 26 Fairmont Hotel San Jos...
 
HTML5 and CSS3
HTML5 and CSS3HTML5 and CSS3
HTML5 and CSS3
 
HTML5 Report Card
HTML5 Report CardHTML5 Report Card
HTML5 Report Card
 
HTML5 Accessibility
HTML5 AccessibilityHTML5 Accessibility
HTML5 Accessibility
 
Real World Web Standards
Real World Web StandardsReal World Web Standards
Real World Web Standards
 
Accessibility of HTML5 and Rich Internet Applications - CSUN 2012
Accessibility of HTML5 and Rich Internet Applications - CSUN 2012Accessibility of HTML5 and Rich Internet Applications - CSUN 2012
Accessibility of HTML5 and Rich Internet Applications - CSUN 2012
 
Checklist for website testing
Checklist for website testingChecklist for website testing
Checklist for website testing
 
Post3 d test plan wk13
Post3 d test plan wk13Post3 d test plan wk13
Post3 d test plan wk13
 
Test Plan for online auction system
Test Plan for online auction systemTest Plan for online auction system
Test Plan for online auction system
 
Angular 2
Angular 2Angular 2
Angular 2
 
29 Essential AngularJS Interview Questions
29 Essential AngularJS Interview Questions29 Essential AngularJS Interview Questions
29 Essential AngularJS Interview Questions
 
Web 3.0 The Semantic Web
Web 3.0 The Semantic WebWeb 3.0 The Semantic Web
Web 3.0 The Semantic Web
 

Similar to TestPlan for IIT website

Quality Assessment Handbook
Quality Assessment HandbookQuality Assessment Handbook
Quality Assessment HandbookMani Nutulapati
 
test-plan-template-05.pdf
test-plan-template-05.pdftest-plan-template-05.pdf
test-plan-template-05.pdfgintpt
 
A guide for automated testing
A guide for automated testingA guide for automated testing
A guide for automated testingMoataz Nabil
 
Advanced security tester syllabus ga 2016
Advanced security tester syllabus   ga 2016Advanced security tester syllabus   ga 2016
Advanced security tester syllabus ga 2016Yasir Ali
 
Scm process assessment guide
Scm process assessment guideScm process assessment guide
Scm process assessment guideRajesh Kumar
 
SAD - Waiter on Wheels
SAD - Waiter on WheelsSAD - Waiter on Wheels
SAD - Waiter on WheelsPrince Kumar
 
Fundamentals of testing
Fundamentals of testingFundamentals of testing
Fundamentals of testingM HiDayat
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test processmuhammad afif
 
Các nhân tố ảnh hưởng đến sự hài lòng của khách hàng đến viettel post
 Các nhân tố ảnh hưởng đến sự hài lòng của khách hàng đến viettel post Các nhân tố ảnh hưởng đến sự hài lòng của khách hàng đến viettel post
Các nhân tố ảnh hưởng đến sự hài lòng của khách hàng đến viettel postLuanvantot.com 0934.573.149
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test processIrvan Febry
 
Fundamental test process
Fundamental test process Fundamental test process
Fundamental test process alex swandi
 
software-testing-framework 3
software-testing-framework 3software-testing-framework 3
software-testing-framework 3pradeepcutz
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test processDinul
 

Similar to TestPlan for IIT website (20)

Quality Assessment Handbook
Quality Assessment HandbookQuality Assessment Handbook
Quality Assessment Handbook
 
Testing guide
Testing guideTesting guide
Testing guide
 
test-plan-template-05.pdf
test-plan-template-05.pdftest-plan-template-05.pdf
test-plan-template-05.pdf
 
A guide for automated testing
A guide for automated testingA guide for automated testing
A guide for automated testing
 
FINAL_SPM_document
FINAL_SPM_documentFINAL_SPM_document
FINAL_SPM_document
 
Advanced security tester syllabus ga 2016
Advanced security tester syllabus   ga 2016Advanced security tester syllabus   ga 2016
Advanced security tester syllabus ga 2016
 
Prototyping
PrototypingPrototyping
Prototyping
 
Scm process assessment guide
Scm process assessment guideScm process assessment guide
Scm process assessment guide
 
SAD - Waiter on Wheels
SAD - Waiter on WheelsSAD - Waiter on Wheels
SAD - Waiter on Wheels
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test process
 
Fundamentals of testing
Fundamentals of testingFundamentals of testing
Fundamentals of testing
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test process
 
Các nhân tố ảnh hưởng đến sự hài lòng của khách hàng đến viettel post
 Các nhân tố ảnh hưởng đến sự hài lòng của khách hàng đến viettel post Các nhân tố ảnh hưởng đến sự hài lòng của khách hàng đến viettel post
Các nhân tố ảnh hưởng đến sự hài lòng của khách hàng đến viettel post
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test process
 
Rbi final report
Rbi final reportRbi final report
Rbi final report
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test process
 
Fundamental test process
Fundamental test process Fundamental test process
Fundamental test process
 
software-testing-framework 3
software-testing-framework 3software-testing-framework 3
software-testing-framework 3
 
data warehousing
data warehousingdata warehousing
data warehousing
 
Fundamental test process
Fundamental test processFundamental test process
Fundamental test process
 

More from Muksitul M Tanim Hasan (8)

Best Interior Concept for your Dream Home
Best Interior Concept for your Dream HomeBest Interior Concept for your Dream Home
Best Interior Concept for your Dream Home
 
ERP - Benefits of ERP in RMG sector
ERP - Benefits of ERP in RMG sectorERP - Benefits of ERP in RMG sector
ERP - Benefits of ERP in RMG sector
 
ERP - Benefits of ERP in RMG sector
ERP - Benefits of ERP in RMG sectorERP - Benefits of ERP in RMG sector
ERP - Benefits of ERP in RMG sector
 
The Internship
The InternshipThe Internship
The Internship
 
Technology behind Quality of life
Technology behind Quality of lifeTechnology behind Quality of life
Technology behind Quality of life
 
Selection of words
Selection of wordsSelection of words
Selection of words
 
Ups
UpsUps
Ups
 
Charity Foundation website
Charity Foundation websiteCharity Foundation website
Charity Foundation website
 

Recently uploaded

Scenario Library et REX Discover industry- and role- based scenarios
Scenario Library et REX Discover industry- and role- based scenariosScenario Library et REX Discover industry- and role- based scenarios
Scenario Library et REX Discover industry- and role- based scenariosErol GIRAUDY
 
UiPath Studio Web workshop series - Day 1
UiPath Studio Web workshop series  - Day 1UiPath Studio Web workshop series  - Day 1
UiPath Studio Web workshop series - Day 1DianaGray10
 
Technical SEO for Improved Accessibility WTS FEST
Technical SEO for Improved Accessibility  WTS FESTTechnical SEO for Improved Accessibility  WTS FEST
Technical SEO for Improved Accessibility WTS FESTBillieHyde
 
Introduction to RAG (Retrieval Augmented Generation) and its application
Introduction to RAG (Retrieval Augmented Generation) and its applicationIntroduction to RAG (Retrieval Augmented Generation) and its application
Introduction to RAG (Retrieval Augmented Generation) and its applicationKnoldus Inc.
 
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptxGraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptxNeo4j
 
Extra-120324-Visite-Entreprise-icare.pdf
Extra-120324-Visite-Entreprise-icare.pdfExtra-120324-Visite-Entreprise-icare.pdf
Extra-120324-Visite-Entreprise-icare.pdfInfopole1
 
How to become a GDSC Lead GDSC MI AOE.pptx
How to become a GDSC Lead GDSC MI AOE.pptxHow to become a GDSC Lead GDSC MI AOE.pptx
How to become a GDSC Lead GDSC MI AOE.pptxKaustubhBhavsar6
 
March Patch Tuesday
March Patch TuesdayMarch Patch Tuesday
March Patch TuesdayIvanti
 
Explore the UiPath Community and ways you can benefit on your journey to auto...
Explore the UiPath Community and ways you can benefit on your journey to auto...Explore the UiPath Community and ways you can benefit on your journey to auto...
Explore the UiPath Community and ways you can benefit on your journey to auto...DianaGray10
 
Keep Your Finger on the Pulse of Your Building's Performance with IES Live
Keep Your Finger on the Pulse of Your Building's Performance with IES LiveKeep Your Finger on the Pulse of Your Building's Performance with IES Live
Keep Your Finger on the Pulse of Your Building's Performance with IES LiveIES VE
 
.NET 8 ChatBot with Azure OpenAI Services.pptx
.NET 8 ChatBot with Azure OpenAI Services.pptx.NET 8 ChatBot with Azure OpenAI Services.pptx
.NET 8 ChatBot with Azure OpenAI Services.pptxHansamali Gamage
 
TrustArc Webinar - How to Live in a Post Third-Party Cookie World
TrustArc Webinar - How to Live in a Post Third-Party Cookie WorldTrustArc Webinar - How to Live in a Post Third-Party Cookie World
TrustArc Webinar - How to Live in a Post Third-Party Cookie WorldTrustArc
 
Outage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedIn
Outage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedInOutage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedIn
Outage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedInThousandEyes
 
AI Workshops at Computers In Libraries 2024
AI Workshops at Computers In Libraries 2024AI Workshops at Computers In Libraries 2024
AI Workshops at Computers In Libraries 2024Brian Pichman
 
Emil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptx
Emil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptxEmil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptx
Emil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptxNeo4j
 
Oracle Database 23c Security New Features.pptx
Oracle Database 23c Security New Features.pptxOracle Database 23c Security New Features.pptx
Oracle Database 23c Security New Features.pptxSatishbabu Gunukula
 
2024.03.12 Cost drivers of cultivated meat production.pdf
2024.03.12 Cost drivers of cultivated meat production.pdf2024.03.12 Cost drivers of cultivated meat production.pdf
2024.03.12 Cost drivers of cultivated meat production.pdfThe Good Food Institute
 
Graphene Quantum Dots-Based Composites for Biomedical Applications
Graphene Quantum Dots-Based Composites for  Biomedical ApplicationsGraphene Quantum Dots-Based Composites for  Biomedical Applications
Graphene Quantum Dots-Based Composites for Biomedical Applicationsnooralam814309
 
The New Cloud World Order Is FinOps (Slideshow)
The New Cloud World Order Is FinOps (Slideshow)The New Cloud World Order Is FinOps (Slideshow)
The New Cloud World Order Is FinOps (Slideshow)codyslingerland1
 

Recently uploaded (20)

SheDev 2024
SheDev 2024SheDev 2024
SheDev 2024
 
Scenario Library et REX Discover industry- and role- based scenarios
Scenario Library et REX Discover industry- and role- based scenariosScenario Library et REX Discover industry- and role- based scenarios
Scenario Library et REX Discover industry- and role- based scenarios
 
UiPath Studio Web workshop series - Day 1
UiPath Studio Web workshop series  - Day 1UiPath Studio Web workshop series  - Day 1
UiPath Studio Web workshop series - Day 1
 
Technical SEO for Improved Accessibility WTS FEST
Technical SEO for Improved Accessibility  WTS FESTTechnical SEO for Improved Accessibility  WTS FEST
Technical SEO for Improved Accessibility WTS FEST
 
Introduction to RAG (Retrieval Augmented Generation) and its application
Introduction to RAG (Retrieval Augmented Generation) and its applicationIntroduction to RAG (Retrieval Augmented Generation) and its application
Introduction to RAG (Retrieval Augmented Generation) and its application
 
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptxGraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
GraphSummit Copenhagen 2024 - Neo4j Vision and Roadmap.pptx
 
Extra-120324-Visite-Entreprise-icare.pdf
Extra-120324-Visite-Entreprise-icare.pdfExtra-120324-Visite-Entreprise-icare.pdf
Extra-120324-Visite-Entreprise-icare.pdf
 
How to become a GDSC Lead GDSC MI AOE.pptx
How to become a GDSC Lead GDSC MI AOE.pptxHow to become a GDSC Lead GDSC MI AOE.pptx
How to become a GDSC Lead GDSC MI AOE.pptx
 
March Patch Tuesday
March Patch TuesdayMarch Patch Tuesday
March Patch Tuesday
 
Explore the UiPath Community and ways you can benefit on your journey to auto...
Explore the UiPath Community and ways you can benefit on your journey to auto...Explore the UiPath Community and ways you can benefit on your journey to auto...
Explore the UiPath Community and ways you can benefit on your journey to auto...
 
Keep Your Finger on the Pulse of Your Building's Performance with IES Live
Keep Your Finger on the Pulse of Your Building's Performance with IES LiveKeep Your Finger on the Pulse of Your Building's Performance with IES Live
Keep Your Finger on the Pulse of Your Building's Performance with IES Live
 
.NET 8 ChatBot with Azure OpenAI Services.pptx
.NET 8 ChatBot with Azure OpenAI Services.pptx.NET 8 ChatBot with Azure OpenAI Services.pptx
.NET 8 ChatBot with Azure OpenAI Services.pptx
 
TrustArc Webinar - How to Live in a Post Third-Party Cookie World
TrustArc Webinar - How to Live in a Post Third-Party Cookie WorldTrustArc Webinar - How to Live in a Post Third-Party Cookie World
TrustArc Webinar - How to Live in a Post Third-Party Cookie World
 
Outage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedIn
Outage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedInOutage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedIn
Outage Analysis: March 5th/6th 2024 Meta, Comcast, and LinkedIn
 
AI Workshops at Computers In Libraries 2024
AI Workshops at Computers In Libraries 2024AI Workshops at Computers In Libraries 2024
AI Workshops at Computers In Libraries 2024
 
Emil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptx
Emil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptxEmil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptx
Emil Eifrem at GraphSummit Copenhagen 2024 - The Art of the Possible.pptx
 
Oracle Database 23c Security New Features.pptx
Oracle Database 23c Security New Features.pptxOracle Database 23c Security New Features.pptx
Oracle Database 23c Security New Features.pptx
 
2024.03.12 Cost drivers of cultivated meat production.pdf
2024.03.12 Cost drivers of cultivated meat production.pdf2024.03.12 Cost drivers of cultivated meat production.pdf
2024.03.12 Cost drivers of cultivated meat production.pdf
 
Graphene Quantum Dots-Based Composites for Biomedical Applications
Graphene Quantum Dots-Based Composites for  Biomedical ApplicationsGraphene Quantum Dots-Based Composites for  Biomedical Applications
Graphene Quantum Dots-Based Composites for Biomedical Applications
 
The New Cloud World Order Is FinOps (Slideshow)
The New Cloud World Order Is FinOps (Slideshow)The New Cloud World Order Is FinOps (Slideshow)
The New Cloud World Order Is FinOps (Slideshow)
 

TestPlan for IIT website

  • 1. 5/12/2013 TEST PLAN IIT WEBSITE Submitted to MOHAMMAD ASHIK ELAHI Submitted to MUKSITUL M. TANIM HASAN (BSSE 0301) MD. SHIBBIR HOSSAIN (BSSE 0317)
  • 2. 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 4.5 5 Operation Guide ...................................................................................................................... 6 Verification & Validation Plan ................................................................................................... 6 Software risk issues ......................................................................................................................... 7 5.1 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 6 Product size risk ....................................................................................................................... 7 Other Potential Risk ................................................................................................................. 9 FEATURES TO BE TESTED................................................................................................................ 10 6.1 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 7 External management ............................................................................................................ 10 Profile management............................................................................................................... 11 Features not to be tested............................................................................................................... 12 7.1 Authentication Module .......................................................................................................... 12 1|P ag e
  • 3. 7.2 Database design ..................................................................................................................... 12 7.3 UI components....................................................................................................................... 12 8 Approach ....................................................................................................................................... 13 8.1.1 9 Test tools ........................................................................................................................ 14 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 2|P ag e
  • 4. 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 3|P ag e
  • 5. 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. 4|P ag e
  • 6. 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 5|P ag e
  • 7. 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     4.3.1 Teacher Student Admin Exam Committee External visitors 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. 6|P ag e
  • 8. 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 • • • • 7|P ag e 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?
  • 9. 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 • • • • • • • 8|P ag e 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?
  • 10. 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 • • • • • 9|P ag e 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
  • 11. 6 FEATURES TO BE TESTED 6.1 EXTERNAL MANAGEMENT i. ii. iii. iv. v. News, events Programs Notice Board Education Archive Achievements etc. 6.2 STUDENT MANAGEMENT i. ii. iii. Add Student Delete Student Manage Student 6.3 BATCH MANAGEMENT i. ii. iii. Batch creation Batch modification Integration 6.4 EXAM MANAGEMENT i. ii. iii. iv. v. Exam dashboard Create Exam Delete exam Publish exam results Exam notification 6.5 COURSE MANAGEMENT i. ii. iii. Course create, edit , modify Delete course Manage course 6.6 FACULTY MANAGEMENT i. ii. iii. iv. 10 | P a g e Faculty create, edit, delete Batch manage Course manage Change course
  • 12. 6.7 TEACHER MODULE i. ii. Attendance management Assignment management 6.8 PROFILE MANAGEMENT i. ii. iii. 11 | P a g e Manage profile Upload photo Edit info
  • 13. 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 12 | P a g e
  • 14. 8 APPROACH Our project “IIT Website” will consist of following testing 1. 2. 3. 4. 5. 6. Functionality testing Data and Database Integrity Testing Unit Testing Acceptance Testing Load Testing 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. 13 | P a g e
  • 15. 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 • • • • • 14 | P a g e Visual Studio Bugzilla Mantis Git: version control Various types of browser with various versions like IE -9, IE-10, Chrome, Mozilla Firefox, Safari etc.
  • 16. 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 15 | P a g e
  • 17. 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 23 November Test Suite Internal Peer review 24 November Test Data Sets Internal Peer review 25 November Test Scripts Internal Peer review Test Defect Report Project Manager 28 November 30 November Test Results Test Evaluation Report 16 | P a g e Project Manager 4 December
  • 18. 12 REMAINING TEST TASKS Task Data Integration Acceptance level Module wise acceptance Whole system(Integrated of modules) acceptance Verify Test report Select the Acceptance Percentage value Assigned To Status Test Teams,PM,Developer Test Teams,Dev Test Teams Dev, Client, TM Project Manager 13 ENVIRONMENTAL NEEDS In order maintain external website and internal management we need some environmental support • • • • • • 17 | P a g e 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.
  • 19. 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 18 | P a g e
  • 20. 15 RESPONSIBILITIES This table is suggesting who are responsible for which testing. Tasks TM PM Acceptance test Documentation & Execution X X Unit test documentation & Execution X System Design Reviews X Detail Design Reviews Dev Team Test Team X X X X X X X X Test procedure and rules X X X X Change Control and regression testing X X X X X X X Client X X 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. 19 | P a g e
  • 21. 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. 20 | P a g e
  • 22. 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. 21 | P a g e
  • 23. 18 APPROVAL Role Client Name 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 22 | P a g e Signature
  • 24. 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 applicationspecific 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/ 23 | P a g e