Application Testing Proposal

Preparing for a fast-changing application world

Monday, August 25th

2014

PREPARED BY – OMSOFTWARE

WEBSITE – HTTP://WWW.OMSOFTWARE.NET/

About OM Software

OM SOFTWARE is a diversified IT outsourcing company. Our competencies lie in setting up dedicated

offshore software development teams for outsourced product development, web development,

application maintenance, Search engine marketing/Optimization and independent Software Testing with

a local Project management team. By Using our proven Project Management and mature development

methodology.

Our Service offerings –

ISO 9001:2008 CERTIFIED COMPANY

NASSCOM MEMBER

Application Development IT Infrastructure Service

Application Management E-business Solution

Testing Services SEO/SEM Services/Solutions

Table of Content

1. Introduction

2. Executive Summary

3. Basic Q’s on testing

4. Project Management Models

5. Testing Management Model

6. Types of Testing

7. Testing & Debugging

8. Testing Documentation

9. Testing Automation Tools

10. Testing Report or Bug Report

11. OMS Software Testing Life Cycle

12. Clientele Base

Computer programs are designed and developed by human beings and hence are prone to errors.Unchecked, they can lead to a lot of problems, including social implications.

Testing the software becomes an essential part of the software development lifecycle.Carrying out the testing activities for projects has to be practiced with proper planning and must be implemented correctly.

Our testing practice offers a comprehensive suite of Software testing services spanning consulting, enterprise services and functionality testing. Expertise on both the business and technical sides of testing has enabled us to create innovative approaches that deliver accelerated results. We use an established testing methodology and employ a wide range of industry-standard testing tools that leverage established methodologies to provide your organization with advantage.

We work hard to encourage a spirit of innovation in all our testing professionals and to share continually what we learn with customers.

1. Introduction

2. Executive Summary

The number and variety of consumer and enterprise applications has grown exponentially over the last few

years. Organizations need to ensure that every application meets a high quality bar in order to prevent revenue

loss, lost productivity and damage to brand reputation.

Testing Mobile applications is now different and more complex than testing traditional desktop and web

applications. Mobile applications need to be tested on a variety of software platforms and versions, on diverse

hardware and form factors, and under different network connectivity conditions. Moreover, the rapid pace of

mobile OS updates, the frequent introduction of new devices and the customer expectation

of quick upgrades require additional test cycles.

A comprehensive application testing strategy is essential for getting your applications to market on time and

within budget.

3. Basic Q’s on testing

Q – Why to test?

A - Testing becomes absolutely essential to make sure the software works properly and does the work that it

is meant to perform.

Q – What to test?

A – Any working product which forms part of the software application has to be tested. Both data and programs

must be tested.

Q – How often to test?

A – When a program (source code) is modified or newly developed, it has to be tested.

Q – Who tests?

A – Programmer, Tester and Customer/Client.

4. Project Management Model

OM Software follows Software Development Life Cycle for project development, which is a process consisting of series of planned activities to develop or alter the software products.

SDLC can be performed through following Models –

Agile Model

V Model

Iterative Model

Waterfall Model

Big Bang Model

RAD Model

Out of these models OMSoftware mainly works on Agile and V model, which are described in further slides.

5. Testing Management Model

Agile Model

We mainly use this model when we are working on Testingservices from the beginning of any Application.

Agile SDLC model is a combination of iterative and incrementalprocess models with focus on process adaptability andcustomer satisfaction by rapid delivery of working softwareproduct.

Agile Methods break the product into small incremental builds.These builds are provided in iterations. Each iteration typicallylasts from about one to three weeks. Every iteration involvescross functional teams working simultaneously on various areaslike planning, requirements analysis, design, coding, unittesting, and acceptance testing.

At the end of the iteration a working product is displayed to thecustomer and important stakeholders.

Iterative approach is taken and working software

build is delivered after each iteration. Each build is

incremental in terms of features; the final build

holds all the features required by the customer

V – shaped Model

We mainly use this model when we are working on Testing

services once the Application is already developed.

The V - model is SDLC model where execution of processes

happens in a sequential manner in V-shape. It is also known as

Verification and Validation model.

V - Model is an extension of the waterfall model and is based on

association of a testing phase for each corresponding

development stage. This means that for every single phase in

the development cycle there is a directly associated testing

phase. This is a highly disciplined model and next phase starts

only after completion of the previous phase.

Under V-Model, the corresponding testing phase of

the development phase is planned in parallel. So

there are Verification phases on one side of the .V.

and Validation phases on the other side. Coding

phase joins the two sides of the V-Model.

Testing Management Models Continue…

6. Types of Testing

Types of Testing OMSoftware perform on every applications

User Interface Testing (GUI) Compliance Testing

Functional Testing Interruption Testing

Performance and Stress Testing Monkey Testing

Usability Testing Network Testing

Compatibility testing Compatibility testing

Security Testing Adhoc Testing

7. Testing and Debugging

Testing Debugging

Testing is focused on identifying the problems in the product.

Debugging is to make sure that the bugs are removed or fixed

Done by Tester Done by Developer

Need not know the source code Need to know the source Code

Testing proves a programmer’s failure This is programmer’s vindication

Test execution and Design can be automated Automated Debugging is not possible

Testing can often be done by outsider It should be done by insider

8. Testing Documentation

Testing documentation involves the documentation of artifacts which should be developed before or during the testing of Software.

Documentation for Software testing helps in estimating the testing effort required, test coverage, requirement tracking/tracing etc. Here are some commonly used documented artifacts related to Software testing documented by OMSoftware QA Team :

Test Plan

Test Scenario

GUI Test Cases

Functional Test Cases

Databases Test Cases

Requirements Traceability Matrix

9. Testing Automation Tools

Load RunnerLoad Runner is an automated performance and test automation product from Hewlett-Packard for application load testing: examining system behavior and performance, while generating actual load.

Quick Test Professional (QTP)Unified Functional Testing software, formerly known as HP Quick Test Professional provides functional and regression test automation for software applications and environments. HP Unified Functional Testing can be used for enterprise quality assurance.

Neo LoadNeo Load is a load and stress testing tool to measure the performance of web and mobile applications. Neo Load provides pragmatic solutions to developers to help them optimize performance before the application goes into production.

Quality Center (QC)Quality Center is quality management software offered from the HP Software Division of Hewlett-Packard with many capabilities acquired from Mercury Interactive Corporation. It offers software quality assurance, including requirements management, test management and business process testing for IT and application environments.

10. Testing Report or Bug Report

We will share a Bug tracker Loin credentials for your project (http://bugtracker.omsoftware.co/), where you can find Bug Reports such as -TPR Id A unique identifier across the company

TPR Description A brief description of the problem

Date The date on which the TPR is raised

Author The tester who raised the TPR

Test Case Id The test case that caused this TPR to be raised

Problem Severity Show stopper/High/Medium/Low. This will be agreed by the lead tester and the development project manager.

Priority High/Medium/Low. How soon to fix?

Problem Detailed Description A description of what was tested and what happenedThis will be filled by the tester.

Problem Resolution After fixing the problem, the developer fills this section, with details about the fix. Developer gives this

Assigned to To whom the TPR is assigned to be fixed

Expected Closure When the problem to be closed Data

Actual closure dataTPR status

When the problem is actually rectified and closed This is a changing field to reflect the status of the TPR.

11. OMS, Software Testing Life Cycle

OMS_STLC _Cont.…

12. Clientele Base

Global Presence

Singapore :OM Software Pte. Ltd#18-00, 16 Colleyer Quay, Singapore+65-97962745

Australia : Level 1, Ann St Fortitude Valley Brisbane 4006+61 73177 1123

India :IN- Bhopal 33-3D Saket Nagar , Bhopal MP , India+91-9713032160IN – Hyderabad Unit 2 [302] MJR Magnifique Plot No 75-76 Beside Wells Fargo CenterGachibowli, Hyderabad

www.Omsoftware.net info@omscorps.com