Firstly i will contact to TL ..after confirmation from him i will forward this bug to Concerned Developer.....

When you find any bug/defect while executing the script ensure that the script is failed and the system/functionality is not working as per requirement document. Prepare a note that will explain how actual result is contradiction with expected result of failed script also give the details such as environment test data etc.

This will help developers to understand the defect correctly.

Explaining a BUG is an ART for a TESTER...

So...it has lot of things inside

From my learning...I do this!

1. Moment you get the bug just double check in the bug DB for duplicates. I mean from the earlier build it might've been uncovered and recorded as a bug and the release manager might've decided to fix it in later builds.

2. Not there in DB then analyse the bug for confirmation. If you are strongly recomand that as a bug you can proceed OR please reconfirm with peers

3. Still BUG? So go ahead use the Bug Tracking database (if any) or use the excel bug reporting format (whatever you have) But tell everything clear.

a. Bug Title Bug Description The setup you have to reproced the Priority Impact

b. H/W and S/W used

c. Screen shots Log file (if any) SQL Qurey statements...If possible record the entire steps in a movie file and send the clip!!!

Justin

How to record as a Movie file? Is there any specfic tool to record as a Movie file? Pls repply.

Thanks

Sivaiah

Cognizant - Bangalore.