Active TopicsActive Topics  Display List of Forum MembersMemberlist  CalendarCalendar  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin


 One Stop Testing ForumSoftware Testing @ OneStopTestingBeginners @ OneStopTesting

Message Icon Topic: Testing Policies

Post Reply Post New Topic
Author Message
himanshu_joshi
Newbie
Newbie
Avatar

Joined: 13Sep2008
Location: India
Online Status: Offline
Posts: 1
Quote himanshu_joshi Replybullet Topic: Testing Policies
    Posted: 25Sep2008 at 5:18am

There are various types of testing,one can used for testing an web based application mainly E-Commerce based:

 
(i) Unit Testing: In the Unit testing we tested the separate modules of the software i.e. Login module, Gift Certificate etc. We carried out Black box testing where each module or component of the application is tested individually. We tested the components by passing data through it and we monitored data to find the errors.

 

 

 

(ii) Integration Testing: In this method of testing we implemented the software at the client’s location and run it. So we tested the product on client’s network. As part of testing, we looked for any signs of the collision between our software components and those of the clients. We want to make sure there is no confusion among the application on the network when they are running simultaneously.

 

We began from the login window and gone through all the functions till successful order being placed. We have carefully looked for any sort of collision between several different applications.

 

 

 

(iii) System Testing: System testing is performed on the entire system of application in the context of Functional Requirement Specification (FRS) and / or System Requirement Specification (SRS).In this investigatory testing phase, the focus is to have almost a destructive attitude like having password input in case-sensitive format and input invalid amount in Gift Certificate etc.

 

 

We test not only the design but also the behaviour and even the believed expectations of all the three possible customers. This testing is also intended to test up to and beyond the bounds defined in the software / hardware requirement specification(s).

 

 

(iv)User Acceptance Testing: User Acceptance Testing is the final step before rolling out the developed system. Usually the end users, who will be using this application; test the application before ‘accepting’ the application. This testing also helps nail bugs related to usability of the application.

 

Prerequisites: Before the User Acceptance testing the application  is fully developed. Various levels of testing (Unit, Integration and System) are already completed before User Acceptance Testing is done. As various levels of testing have been completed most of the technical bugs have already been fixed before UAT.

 

To ensure an effective User Acceptance Testing, following Test cases are created.
These Test cases are created using various use cases identified during the Requirements definition stage. During this type of testing our specific focus is on exact real customer usage of application.

 

The User Acceptance Testing is done in an environment that simulates the production environment. The test cases are written using real possible scenarios for the application.


Always eager to learn and share the knowledge.



Post Resume: Click here to Upload your Resume & Apply for Jobs

IP IP Logged
Post Reply Post New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum



This page was generated in 0.430 seconds.
Vyom is an ISO 9001:2000 Certified Organization

© Vyom Technosoft Pvt. Ltd. All Rights Reserved.

Privacy Policy | Terms and Conditions
Job Interview Questions | Placement Papers | Free SMS | Freshers Jobs | MBA Forum | Learn SAP | Web Hosting