Quality Testing

Quality is delighting customers

Hi All,

I am new in software testing .So can anyone share sample bug reports ? It will help me to raising the bug properly.

 

Thanks to all

Views: 5600

Reply to This

Replies to This Discussion

Below sample bug/defect report will give you exact idea of how to report a bug in bug tracking tool.

Here is the example scenario that caused a bug:

Lets assume in your application under test you want to create a new user with user information, for that you need to logon into the application and navigate to USERS menu > New User, then enter all the details in the ‘User form’ like, First Name, Last Name, Age, Address, Phone etc. Once you enter all these information, you need to click on ‘SAVE’ button in order to save the user. Now you can see a success message saying, “New User has been created successfully”.

But when you entered into your application by logging in and navigated to USERS menu > New user, entered all the required information to create new user and clicked on SAVE button. BANG! The application crashed and you got one error page on screen. (Capture this error message window and save as a Microsoft paint file)

Now this is the bug scenario and you would like to report this as a BUG in your bug-tracking tool.

How will you report this bug effectively?

Here is the sample bug report for above mentioned example:
(Note that some ‘bug report’ fields might differ depending on your bug tracking system)

SAMPLE BUG REPORT:

Bug Name: Application crash on clicking the SAVE button while creating a new user.
Bug ID: (It will be automatically created by the BUG Tracking tool once you save this bug)
Area Path: USERS menu > New Users
Build Number: Version Number 5.0.1
Severity: HIGH (High/Medium/Low) or 1
Priority: HIGH (High/Medium/Low) or 1
Assigned to: Developer-X
Reported By: Your Name
Reported On: Date
Reason: Defect
Status: New/Open/Active (Depends on the Tool you are using)
Environment: Windows 2003/SQL Server 2005

Description:
Application crash on clicking the SAVE button while creating a new
user, hence unable to create a new user in the application.

Steps To Reproduce:
1) Logon into the application
2) Navigate to the Users Menu > New User
3) Filled all the user information fields
4) Clicked on ‘Save’ button
5) Seen an error page “ORA1090 Exception: Insert values Error…”
6) See the attached logs for more information (Attach more logs related to bug..IF any)
7) And also see the attached screenshot of the error page.

Expected result: On clicking SAVE button, should be prompted to a success message “New User has been created successfully”.

(Attach ‘application crash’ screen shot.. IF any)

Save the defect/bug in the BUG TRACKING TOOL.  You will get a bug id, which you can use for further bug reference.
Default ‘New bug’ mail will go to respective developer and the default module owner (Team leader or manager) for further action.

 

 Bhargav,

           great dude... the best answer I have ever seen from You..! keep it up...!

           I am short of words .. simply fabulous !!

thanks!!!

so till now i was not giving proper answers ;)

 

 No nothing like that but this one is Awesome ...!

Thanks one again...

Thanks a lot Bhargav

 

& What is meant by Steps To Reproduce??

Steps to reproduce the bug which is causing the problem.

 

 Steps to Reproduce also known as Steps to Replicate :-- It is the most important part of bug report.

It means :- to get the bug,  development team can execute the steps which has been given by the test team as Steps to Reproduce..

 

got it .

Thank you Samrat jha

Good n thanks

Wen a bug is identified while executing any of the test case it will be reproduce by test engineer mutiple times.

If identified issue is consistently reproducible it will be reported or locked using bug tracking tool.Based on project version & module bug tracking tool will auto assign the bug to development point of contact.Notification mails will be send to development point of contact and the author of the bug.

              Development point of contact will assign the bug to individual developer responsible for corresponding functional area this bug will be evaluated by the assigning & following the status

 

case1:Issue or bug locked is valid & reproduceble:

          In this case developer will investigate root cause of the error & modifies the code .This modified program will be included in the subsequent build.wen this build is install successfully in the testing server.Developer will change the status of the bug to submitted for testing.bug tracking tool will send a notification mail to the author of the bug.test engineer will conduct resting and regression testing for the fixed issue.if no new issues r identified bug status will be changed to verify and close.

case2:Bug is not reproducible:

          If the developer is not able to reproduce the issue by using reproduction steps mentioned in the bug.bug status will be changed to not reproducible as part of evaluation of the bug.Bug tracking tool will send a notification mail to author of the bug.test engineer will verify reported issue in the latest build available in testing servers.The issue is not not reproducible it will be closed as by the test engineer.If the issue is reproducible for the same reproducible steps are slightly modify reproducible steps will be updated in the bug.developer will verify the bug as per latest reproduction steps either in unit testing server or testing servers.If the reported issue occurs & valid it will be fixed.

case3:not a bug:

        During evaluation of the bug if application is working as per the design behavior.Developer will mark the bug as not a bug with valid justification.bug tracking tool will send a notification mail to author of the bug.If test engineer is convinced by developers justification,bug will be closed as not a bug.if the bug is lock because of incorrect information functional specification document.It will be converted as documentation bug.documentation team will update corresponding documents.If justification given by developer is not valid or not convincing test engineer will reopen the bug with valid reasons.

                   Notification mail will be send to assign of the bug by bug tracking tool.developer is convinced with test engineers justification bug will be fixed or else it will be marked as not a bug with new justification in the bug.At this stage test engineer will send a mail to domain expert to get correct behaviour information.If test engineer is r8 based on domain expert mail.developer will fix the bug.If developer argument is r8 bug will be closed as not a bug.

case3:Not feasible to fix:

             if reported bug is related to core programming technology it will be marked as not feasible to fix and a new bug will be lock according to programming technology company.

case4:Duplicate bug:

          If the reported issue is already locked by another test engineer.it will be marked as duplicate bug fixing the base issue will automatically resolves all the duplicate bugs.

case 5:Fix the bug:

       after evolution of the bug if the reported issue is valid.developer investigates the source of the problem.after identifying the cost associated program fill be check out from Software configuration management servers.These files will be locked till bug fixing is completed.modified files will be included in subsequent builds.

case6: verify the bug:

       Bugs which r reported will be fixed and included in the latest build.on successful installation of the build testing servers.Developer will change the status of the bug to submitted for testing.Bug tracking tool will send a notification mail to author of the bug.retesting and regression testing will be conducted for this bug.

  a)Issuer reported is not fix: In this case bug will be reopen by test engineer,by giving reopen justification.developer will investigate root causes of the issue & a modified patch(or)fix.

  b)Issue is resolve partially: If the reported issue is existing in multiple location &is fixed in few location is called partially resolve fix.a new bug will be locked for the scenarios which r not fix &original bug will be placed on hold.After fixing the new issue both the bugs will be retesting.If all the issues are addressed both the bugs will be closed.

 c)Regression: while executing regression test cases if any new issue is identified a new bug will be locked.If the associated test case is already executed and marked as past new issue will be called regression bug. while fixing the new issue developer will fix original issue and regression issue.if regression is happend in case of patch,old patch will be absoluted &new patch will be created for the regression bug.

        test case associated to the newly locked bug is not executed already then a mail will be sent to the developer to check the possibility of regression.if the new issue is occurring because of fixing the original issue developer will send a mail stating that newly reported bug is a regression bug or else new issue will be taking care in subsequent builds.

  d)not feasible to test: test engineers will mark a bug as not feasibility test in the following cases:

    * Issue is not reproducible internally.

    * In case of data fixes

    * If code changes can't be verified functionality point of view.

 

Fix:solution to internal bug which will be submitted for testing as part of new builds.

Patch:solution to customer or client bug or for an internal bug which is lock after releasing the application.

thanks a lot for ur useful reply & efforts  @ madhurima.

 

I have some doubts in ur reply

What is core programming technology?

What is root causes analysis?When we do this analysis?

What is meant by  data fixes?

Plz reply & thanks for advance

RSS

TTWT Magazine


Advertisement

Advertisement

Advertisement

Advertisement

© 2021   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service