SYNOPSIS

ON

LATUR POLICE WEBSITE TESTING

IN PARTIAL FULFILLMENT OF

MASTER OF COMPUTER APPLICATION

BY

SHUBHAM PRAMOD KHOGRE

MCA – III SEM - V

2017-2020

SUBMITTED TO

SAVITRIBAI PHULE PUNE UNIVERSITY

SINHGAD INSTITUTE OF MANAGEMENT

PUNE-411 041

1
INTRODUCTION

1.1 About the System under Test

Introduction

The purpose of the Test Plan is to gather all the information necessary to plan and
control the test effort for testing Latur Police Website. It describes the approach to
testing the software, and will be top-level plan used by testers to direct the test effort.

This test plan for Testing Latur Police Website supports the following objectives:

 Identifies the modules that should be targeted by the tests.

 To check the performance of the website.
 Check to reduce the load of the website.
 Check the speed and connection time of the website
 Identifies idea behind the test areas to be covered.

2
1.2 Scope of Work

This test plan describes the unit, subsystem integration and system level tests that will
be performed on the components of a website
Unit tests will be done through the test driver program that perform boundary checking
and basic black box testing.
Subsystem tests will be define interfaces between the following packages:

1) GUI
2) Main Application

The following performance measurements will be tested:

1) Request to response time taken by system

2) Testing the system for the given idle condition
3) FTP Authentication will be tested
4) Throughput timing or connection time of website will be tested

3
1.3 Operating Environment- Hardware and Software

 Hardware Specifications:-

 Processor:- Intel Pentium core IV and above

 Hard Disk:- Minimum 20GB
 RAM:- Minimum 2GB

 Software Specifications;-

 Operating System:- Windows 7,8

 Testing Tools:- Apache Jmeter

4
1.4 Detailed Description of Tools Used in Testing

Apache Jmeter:

Apache JMeter is an apache project that can be used as a load testing tool for
analyzing and measuring the performance of a variety of services, with a focus on web
applications.

JMeter Plugins is an independent project for Apache JMeter. Each plugin serves
different purpose and expedites the process of creating and executing JMeter Test Plan.
Users can install plugins via the Plugin Manager.

jMeter is an Open Source testing software. It is 100% pure Java application for load
and performance testing.

jMeter is designed to cover various categories of tests such as load testing, functional
testing, performance testing, regression testing, etc., and it requires JDK 5 or higher.

This tutorial provides an in-depth coverage of jMeter framework including its test
plans, listeners, functions, and regular expressions.

JMeter is a Java desktop application with a graphical interface that uses the Swing
graphical API. It can therefore run on any environment / workstation that accepts a
Java virtual machine, for example − Windows, Linux, Mac, etc.

The protocols supported by JMeter are −

 Web − HTTP, HTTPS sites 'web 1.0' web 2.0 (ajax, flex and flex-ws-amf)

 Web Services − SOAP / XML-RPC

 Database via JDBC drivers

 Directory − LDAP

 Messaging Oriented service via JMS

 Service − POP3, IMAP, SMTP

 FTP Service

5
How it works:

JMeter simulates a group of users sending requests to a target server, and returns
statistics that show the performance/functionality of the target server/application via
tables, graphs, etc.

Take a look at the following figure that depicts how JMeter works −

Step 1: Verify Java Installation

First of all, verify whether you have Java installed in your system. Open your console
and execute one of the following java commands based on the operating system you
are working on.

Step 2: Set Java Environment

Set the JAVA_HOME environment variable to point to the base directory location,
where Java is installed on your machine.

Step 3: Download JMeter

Download the latest version of JMeter
fromhttps://jmeter.apache.org/download_jmeter.cgi. For this tutorial, we
downloaded apache-jmeter-2.9 and copied it into C:\>JMeter folder.

6
Step 4: Run JMeter
After downloading JMeter, go to the bin directory. In this case, it
is/home/manisha/apache-jmeter-2.9/bin

Windows jmeter.bat

Writing a Test Plan:

Step 1: Start the JMeter Window

Open the JMeter window by clicking /home/manisha/apache-jmeter-
2.9/bin/jmeter.sh

Step 2: Add/Remove Elements

Elements (which will be discussed in the next chapter Test Plan Elements) can be
added to a test plan by right-clicking on the Test Plan node and choosing a new
element from the "add" list.

Alternatively, you can load an element from a file and add it by choosing the "merge"
or "open" option.

For example, let us add a Thread Group element to a Test Plan as shown below −

To remove an element, make sure the element is selected, right-click on the element,
and choose the "remove" option.

Step 3: Load and Save the Elements

To load an element from file −

 Right-click on the existing tree element to which you want to add the loaded
element.

 Select Merge.

7
  Choose the file where you saved the elements.

 JMeter will merge the elements into the tree.

By default, JMeter does not save the element, you need to explicitly save it.

To save tree elements −

 Right-click on the element.

 Choose the Save Selection As ... option.

JMeter will save the element selected, plus all the child elements beneath it. By default,
JMeter doesn't save the elements, you need to explicitly save it as mentioned earlier.

Step 4: Configuring the Tree Elements

Any element in the Test Plan can be configured using the controls present in JMeter's
right-hand side frame. These controls allow you to configure the behavior of that
particular test element. For example, the Thread Group can be configured for a number
of users, ramp up periods, etc.

Step 5: Saving the Test Plan

You can save an entire Test Plan by using either Save or "Save Test Plan As ..." from
the File menu

Step 6: Run the Test Plan

You can run the Test Plan by clicking Start(Control + r) from the Run menu item.
When JMeter starts running, it shows a small green box at the right-hand end of the
section just under the menubar.

Step 7: Stop the Test Plan

You can stop your test in two ways −

 Using Stop (Control + '.'). It stops the threads immediately if possible.

 Using Shutdown (Control + ','). It requests the threads to stop at the end of any
current work.

8
TEST PLANNING

2.1 Objective of Testing

 Finding defects which may get created by the website developer while
developing the website.
 To Test weather the website is performing its functioning correctly
 To prevent the website from defect and make it error free.
 To make sure that end result meets the user requirement.
 To gain the confidence from the customer by providing them the quality
website.

9
2.2 Software Requirement Specification

A software requirement specification (SRS) is a document that captures

complete description about how the system is expected to perform. It is usually
signed off at the end of requirements engineering phase.

1. Introduction
1.1 Purpose
1.2 Scope of Testing

2. Non-functional Requirements

1. Introduction

1.1 Purpose

 Testing the form to ensure its consistency and integrity throughout the
website.
 Testing various links present or defined for a website
 Website validation is done to ensure website is authorized or not and
established standards, which is used to optimize the website at SEO
level.
 Response time, throughput and speed of the website under different load
 Testing design, layout and presentation of the website as per the user’s
need & expectation.

10
1.2 Scope of Testing

The scope of software testing itself is to cover both functional and non—
functional aspects of the entire product under test.

The functional requirements are the use cases relevant to the user visible
features of the system.

Non-functional requirements are the ones that needed to have the system
functioning correctly.

Testing provides over system error free with the help of:

Modules of Testing:

1) Missing Persons
2) Stolen Vehicles
3) Accident Compensation
4) Report/Complaint

Manual Testing:
 Test Scenario
 Test Cases Design
 Defect Report
 Test Summary Report

Automation Testing:

 Performance Testing
 Load Testing

11
2. Non-functional Requirements

Security
The security related to the website that only the authorised users can access
the
Website and make the order or use the facility.

Reliability
The system provides storage of all database on redundant computers with
automatic switchover. The reliability of the separate components. The main
pillars of reliability of the system is the backup of the database witch is
continuously maintained and updated to reflect the most recent changes.
Thus the overall stability of the system depends on the stability of the
container and its underlying OS.

Availability
The system should be available all the all times, meaning the user can access
it using a web browser , only restricted by the down time of the server on
which the system runs. In case of a hardware failure or database corruption,
a replacement page will be shown. Also in case of a hardware failure or
database corruption, backups of the database should be retrieved from the
server and saved by the administrator. Then the service will be restarted. It
means 24*7 availability .

Maintainability
A commercial database is used for maintaining the database and the
application server takes care of the site. In case of a failure, a initialization of
the program will be done. Also the software design is begin done with
modularity in mind so that maintainability can be done efficiently.

Portability
An end-user is using this system on any OS, either it is Windows or Linux.
The system shall run on PC, Laptops, and Tablets, Smartphone’s etc.

12
2.3 Master Test Plan (IEEE Format)

The purpose of this document is to present a detailed description of online food

delivery. It will explain the purpose and the features of the system the interfaces of the
system, what the system will do the constraints under which it must operate and how the
system will react to external stimuli. This document is intended for both the
stakeholders and the developers of the system.

Team Interaction:

 The following describes the level of team interaction necessary to have a

successful product.

 The Test Team will work closely with the Development Team to achieve a high
quality design and user interface specifications based on customer requirements.

 The Test Team will work closely with Development Team to determine whether
or not the application meets standards for completeness. If an area is not
acceptable for testing, the code complete date will be pushed out, giving the
developers additional time to stabilize the area.

 Since the application interacts with a back-end system component, the Test
Team will need to include a plan for integration testing.

13
Test Objective

 To check the throughput time of the website.

 To reduce the load of the website
 To check the response time of the website.
 To check the latency of the website
 To check the connection time of the website

Process Overview

UNIT TESTING

MODULE TESTING

Component Testing
SUB-SYSTEM TESING

Integration Testing SYSTEM TESTING

ACCEPTANCE TESTING
User Testing
Performance testing

This test will be conducted to evaluate the fulfilment of a system with specified
performance requirements. It will be done using apache Jmeter tool.

14
Functionality Testing:-

Test web applications/web sites to ensure that all aspects of your site functions properly
such as images, text, form elements, dialogs, menus appear correctly, HTML links
work, form submissions succeed, etc.

Integration Testing

Automate Localization Testing of your web applications/web sites to test multi-

language deployments of your applications without re-recording.

Load Testing

Test Web Applications/Web Sites to ensure that is capable of handling a predetermined

peak load by generating 1000’s of users on Web site.

Web Services Functional Testing:-

Test Web Services to ensure that the functionality works correctly by validating the
responses sent to each HTTP request.

Web Services Performance Testing:-

Test Web Services to gather the performance and stability information of web services
by realistically simulating the load on your web site

15
Sr. Requirements Typical Components Detailed Description

a) Test Strategy and

Approach

b) Test Scope
1) Introduction

c) Test Assumptions

a) Defects Discovered and

Corrected

b) Improvement Ideas

c) Structured

Walkthrough Programming Compliance

2)
(Static Testing)

d) Language Standards

e) Development
Documentation Standards

a) Input Test Data

Test Cases
b) Initial Conditions
3) (Dynamic
Testing)
c) Expected Results

16
 d) Test Log Status

a) Test Strategy and

Approach

b) Platform

c) Libraries
Environment
4)
Requirements
d) Tools

e) Test Procedures

f) Status Reporting

Function Validation Testing

It ensure that we built the right application. In doing this test, we will try to find the
errors in the inputs and outputs, that is, we will test each function to ensure that it
properly implements the

Bug Tracking / Bug process:

During testing, the testing team members normally encounter behavior that goes against
a specified or implied design requirement in the product When this happens, we will
document and reproduce the bugs for the developers

17
Test Schedule

It is section contains the overall project schedule. It discusses the phases and key
milestones as they relate to quality assurance. e.g., Usability Testing, Code Complete
Acceptance, Beta Testing, Integration Testing, Regression Testing, System Testing.

 Test plan document - this document should address testing objectives, criteria,
standards, schedule and assignments, and testing tools.
 Unit Testing Plan
 Integration Plan
 System Testing Plan

 Test Design Document

 Unit white-box test design – covers white testing criteria, methods and test
cases
 Unit black-box test design – covers black-box testing criteria, methods and
test cases
 System test design – covers system test criteria, methods, and test cases,
scripts.

 Test report document

 Unit white-box test report – covers unit white box test results, problems,
summary and analysis
 Unit black-box test report – covers unit black box test results, problems,
summary and analysis
 System Test report – covers system test results, problems, summary and
analysis

18
2.4 Review of Test Basis (prototype testing)

Test Basis is defined as the source for creation of test Cases. It can be the Application
itself or the requirement documents like SRS (Software Requirement Specification),
BRS (Business Requirement Specification), etc.

A few test cases among the many you could have thought of are listed below

 Check the response when valid Email ID is entered, and send is pressed
 Check the response when invalid Email ID are entered and send is pressed
 Check the response when Email ID is empty and send is pressed

You may have also realized that to create test cases you need to look at something to
base your test. This is nothing but Test Basis. This test basis could be the actual
Application Under Test(AUT), or maybe even by experience but most of the times,
like, in this case, would be based on documents. Where test plans are created using the
corresponding documents, and once the code is ready, it is ready for testing.

19