Tuesday, December 20, 2011

Effective way of reporting Bug- Defect report


According to the standard way of Defect profile document format:

Bug Title: 
Title should be short, precise and point the issue correctly.


Bug Description: 
Though the title reflects the issue in short, define the bug in few lines
which gives brief description


Steps to reproduce:
Here clearly mention the steps where you face the error and what are
the steps to be reproduced for it. Mention the steps right from invoking
a browser , entering application url to the place where issue arised.


Screen shots:
Screen shots play an important role for effective bug report.Try to attach
 the screen shots which make others to understand easily on looking it.
Sometime the issue may be over looked while reproducing, hence attach
the screen shots for necessary bugs.
Make an habit of it.

Details:
Some data like environmental details may also help developers to understand
what exactly is the cause by knowing the environment. Environment details
such as Operating System, Browser and its version etc.. Some browsers may
not support some features and some issues may also does not occur in some browsers.
Hence this information helps developers to resolve issue sooner.

Shot directly:
Never report against any single person directly as XXX person developed this .

Priority:
When bug should be fixed? Priority is generally set from P1 to P5. P1 as “fix the bug with highest priority” and P5 as ” Fix when time permits”.
Severity:
This describes the impact of the bug.
Types of Severity:
  • Blocker: No further testing work can be done.
  • Critical: Application crash, Loss of data.
  • Major: Major loss of function.
  • Minor: minor loss of function.
  • Trivial: Some UI enhancements.
  • Enhancement: Request for new feature or some enhancement in existing one.



Current Result: 
What is the actual result on running above steps i.e. the bug behavior


Expected:
How application should behave on above mentioned steps.



Environment

This helps to answer question that the assignee may have.

Product: In which product you found this bug.
Version: The product version if any.
Component: These are the major sub modules of the product.
Platform: Mention the hardware platform where you found this bug. The various platforms like ‘PC’, ‘MAC’, ‘HP’, ‘Sun’ etc.
Operating system: Mention all operating systems where you found the bug. Operating systems like Windows, Linux, Unix, SunOS, Mac OS. Mention the different OS versions also if applicable like Windows NT, Windows 2000, Windows XP etc.



Simple Language :
Use simple language while explaining about any issue which is understood by anyone

Setup framework :Selenium, Maven, TestNG, Java, Eclipse IDE


Selenium Framework(Selenium,Eclipse,Maven,TestNG, Java)

Resources/Checklist:
JDk
Eclipse IDE
Selenium server
Selenium-java-client driver
Starting and stoppig Selenium server
TestNG in Eclipse IDE
Maven in Eclipse IDE


1. JDK:
Download the latest version of JDK from Java official web site (www.oracle.com)
in your computer and set the system environmental variables accordingly.
select the JDK package with respect to your system OS.

2. Eclipse IDE:
Download the latest version of Eclipse IDE from eclise official website : 
 http://www.eclipse.org/downloads/

3. Selenium server and client driver:
Download the Selenium server and Selenium java client driver of latest version.
http://seleniumhq.org/download/

find the attached screen shot

4. Start and Stop server

After downloading the server unzip it.
Open the cmd prompt and point to the location where you have installed the server and type the command
java -jar selenum-standaloner-server.jar and press "Enter" button.

The server will start in the port 4444 by default where you can find the logs while running the tests.


5. TestNG and Maven integration for Eclipse:

GoTo Help>>Eclipse Market place>> search for TestNG
TestNG integration for eclipse will appear first in list.

Same process is followed for Maven plugin