Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Software testing

No description
by

Deepshi Goel

on 7 October 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Software testing

Overview
Testing means you are checking the software with the –

intent of finding the bug.

Tester assumes that the developed software has bugs

It is the process of evaluating the performance of the software to detect the differences between the given inputs and expected outcome.

It assess the quality of the software.

It is to be performed simultaneously with the Development phase.

It is a Verification and Validation process.


Testing Definition
"Software testing is performed to verify that the completed software package functions according to the expectations defined by the requirements/specifications. The overall objective is not to find every software bug that exists, but to uncover situations that could negatively impact the customer, usability and/or maintainability”.
Process
Software Testing
Purpose
● To discuss the distinctions between validation testing and defect testing
● To describe the principles of system and component testing
● To describe strategies for generating system test cases
● To understand the essential characteristics of tool used for test automation

How does a software fail?
Wrong requirement: without actually knowing what customer wants
Missing requirement
Requirement impossible to implement
Faulty design
Faulty code
Improperly implemented design

Testing Goals
Fault Identification:What fault has caused the failure??

Fault Correction:Change the correction.

Fault Removal:Take out the fault
Generally,testing are of two types:
TYPES OF TESTING
1)MANUAL TESTING:-

Is the process of manually testing software for defects. It requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behavior.
2.
AUTOMATION TESTING:
-

Is the process of testing application by using some automation testing tool,like JMETER,JCRAWLER,POWER TUTOR
MANUAL TESTING
The tester does not follow any rigorous testing procedure, but rather explores the user interface of the application using as many of its features as possible, using information gained in prior tests to intuitively derive additional tests

Test Suites or cases ,are designed during the testing phase and should have 100% test coverage.
Test cases:
A

test case, in software engineering, is a set of conditions or variables under which a tester will determine whether an application, software system or one of its features is working as it was originally established for it to do
.(
Prepared test cases for the BRUNCH,NEC,TRADECRM AND GSK)

It also makes sure that reported defects are fixed by developers and re-testing has been performed by testers on the fixed defects. Basically, this testing checks the quality of the system and delivers bug-free product to the customer.

Manual Testing has been performed by me on the following projects:
BRUNCH
NEC
TRADE CRM
GSK
WHAT I HAVE TESTED IN THESE TWO MONTHS??
WEB BASED APPLICATION
1)NEC(UNDER PROCESS),
2)BRUNCH(WEBSITE AND BRUNCH CMS)
3)TRADECRM(ADMIN PANEL)

MOBILE BASED APPLICATION
1)TradeCRM(both in Iphone and Android)

IVR(INTERACTIVE VOICE RESPONSE)
-GSK
How I tested the Actual functionality of the different modules in these projects??
BRIEF IDEA:
Requirement Gathering
Receive the SRS
Write the test cases,business rules,validations
software go for the development process
Once the build is received,written test cases are executed to check the functionality of the modules.
If any module is not working as per the requirement,then its considered as bug and then it is reported in the bug tracking tool.
RedMine tool is used to track the bug so that developer and tester can coordinate on this to fix the bug.
A proper bug life cycle is executed in fixing the bug.
Once the bug is fixed,its status changes to the CLOSED eventually.
What is Bug Life Cycle??
when,any of the functionality is not working as per the requirement of the software,then it's considered as a bug.
Once a bug is figured out,it is assigned to the developer with its status as"OPEN"
While working on these projects,
whenever any bug is encountered,I reported it on the RED MINE and assign it to the concerned developer.
IF its fixed by the developer,its status is made as "RESolved",and again I test the same issue.
If this is fixed,then I"closed" the bug and if not then it is "reopened".
if developer rejects the bug then a discussion between the concerned person is made.and if the status is "deferred" that means the bug is non-reproducable.
Live Testing done by me:
A)
Brunch WEBSITE/ADMIN PANEL
:
Prepared the test cases and execute them.
1) FUNCTIONALITY and USABILITY testing is done by me.
If any bug is figure out,then I uploaded the same on REDMINE and assign it to the developer with their priority and severity.
A proper bug life cycle is followed to fix the bug.
Regression testing is done to check the fixture and functionality of the bugs issued there.
Eventually,the bug is closed or reopened.
2)DATABASE testing is also performed parallelly to check whether the data uploaded from the front end is aptly inserting,,deleting and updating in he database and if any modification is done from DB then it is reflecting in the front end of application.
3)CROSS BROWSER testing is also done using IE TESTER.
IN this phase of testing,I tested the website of the BRUNCH on the different versions of the browsers to check the interface and functionality of the software or web.
It is required to check the browser testing so that it can be assured that software developed today will be compatible with the present and up coming versions or releases of same browser and the application will behave same in every version.

Continue
..

B)GSK(GLAXO SMITHKLINE)-client
Project:-Global Health Care(remote areas)

1)Written and Executed Test cases for the functionalities of the IVR(Interactive voice Response).
2)FUNCTIONALITY,INTERFACE AND USABILITY testing is done.
3.Bug Life Cycle is executed and bugs are rectified in the same manner.
4)DATABASE TRICKING is done here to check whether the insertion,deletion and Updation is properly happening or not.
5)Live CAll testing is done with Prateek.
6)DB is checked to ensure that what is inserting the DB of live call after droping a call in differnt scenarios.
6)Issues related to the IVR,exporting and importing data are reported in the sheet.
7)REGRESSION TESTING is done to ensure fixture of the bugs..

C) TRADE CRM (WAP AND WEBSITE BOTH)
WEB:
In this project,I have tested the WEB(admin panel)for the File upload functionality from the interface.
FUNCTIONAL,INTERFACE and USABILITY testing has been performed.
WRITTEN AND EXECUTED TEST CASES.
BUGs are tracked on REDMINE and are processed under the proper life cycle.
REGRESSION testing is performed to check whether the bugs are resolved or not.

WAP(IPHONE AND ANDROID):

once the .apk or .ipa files or build is received, I executed the written test cases and follow the same bug tracking and fixing procedure.
same application has been tested on both the OS,which are currently being used widely by the users.
Application were checked on different versions of OS so that application
NEW deal and Ground activations were supposed to behave as per the client's requirement.
This has been tested on
different resolutions of screen
to check the look and feel of the application so that it will be adjusted fairly on the screen and its interface is shown properly on it.
Android and Iphone has varied range of the
APIs
-APIs that allow you to control your application's UI for specific screen sizes and densities, in order to optimize your UI design for different screen configurations. For example, you might want a UI for tablets that's different from the UI for handsets.
NEC(UNDER PROCESS
In this project,
Received the SRS(in the form of PPT from the Project Manager)
Verification of the SRS is done.
Write the test cases,business rules and validations for the website and admin panel.
Project gone for development phase.
As,I received the build of admin panel,written test cases are executed and functionality of the project is assured through the written test cases.This is the validation phase of testing.
FUNCTIONAL,INTERFACE AND USABILITY testing is performed.
If any issue is occurred,then the same is reported in the test cases and also uploaded on the REDMINE. under technical documentation.
Bugs are assigned to the developer and are rectified by him.Otherwise the bug can be deferred or closed after resolving it.
REGRESSION TESTING is performed to cross check the issues and also to see,if any other issue has not arisen due to the fixture of that bug.
PERFORMANCE TESTING is also done to check the performance of the WEB.When some thousands of data was uploaded,its performance degrades and taking lot of time to load.
BOUNDARY VALUE ANALYSIS is a testing technique in which I tested the size of the labels and text fields and check them at the value,value one less than the value and above the value.
DATABASE testing is also done here to check if any insertion,deletion and updation anomalies are present or not.
Once the quality of the project is assured in terms of functionality,scalability,visibility ,then it is deployed on production
Before the build is released on production,it should be keep in mind that no critical bugs are pending and atleast 98% cases should have run correctly.
once the build is deployed on the production,Quick test or UAT is done to check the acceptance of the project.
HTMSL INVENTORY..
HANDSET

DPI

1)HTC HIGH
2)SAMSUNG ACE MEDIUM
3)LG OPTIMUS BLACK MEDIUM
4)MICROMAX LOW
5)DELL HIGH
6)HTC LOW
7)SAMSUNG GALAXY TAB MEDIUM
8)SAMSUNG PRO MEDIUM
Full transcript