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


 One Stop Testing ForumTypes Of Software Testing @ OneStopTestingManual Testing @ OneStopTesting

Message Icon Topic: Error Guessing

Post Reply Post New Topic
Author Message
Mithi25
Senior Member
Senior Member
Avatar

Joined: 23Jun2009
Online Status: Offline
Posts: 288
Quote Mithi25 Replybullet Topic: Error Guessing
    Posted: 01Aug2009 at 5:51am

Overview


Error Guessing is a test case design technique where the tester has to guess what faults might occur and to design the tests to represent them.


Contents:

Definition


Ability to guess based on previous experience in Software Testing environment.


Adhoc method to identify tests likely to expose errors based on experience and intuition. Some areas to guess are Empty or null strings, Zero instances, occurrences, Blank or null characters in strings, Negative numbers

Purpose


The purpose of error guessing is to focus the testing activity on areas that have not been handled by the other more formal techniques, such as equivalence partitioning and boundary value analysis.  Error guessing is the process of making an educated guess as to other types of areas to be tested. 


For example, educated guesses can be based on items such as metrics from past testing experiences, or the tester's identification of situations in the Functional Design Specification or Detailed Design Specification, that are not addressed clearly.


Examples


Though metrics from past test experiences are the optimum basis for error guessing, these may not be available. Examples of error prone situations include:

? initialization of data, (e.g., repeat a process to see if data is properly removed),

? wrong kind of data, (e.g., negative numbers, non-numeric versus numeric),


? handling of real data, (i.e., test using data created through the system or real records, because programmers tend to create data that reflects what they are expecting),

? error management, (e.g., proper prioritization of multiple errors, clear error messages, proper retention of data when an error is received, processing continues after an error if it is supposed to),

? calculations, (e.g., hand calculate items for comparison),

? restart/recovery, (i.e., use data that will cause a batch program to terminate before completion and determine if the restart/recovery process works properly),

? proper handling of concurrent processes, (i.e., for event driven applications, test multiple processes concurrently).




Edited by Mithi25 - 01Aug2009 at 6:01am



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