first i will send detail bug description to corresponding
developer and tell the strong reasons.if they didn't accept
i will inform to my pm and all are(developer,tester and
manager)discuss and we will finalize
Here the problem is about confusion...At this time tester
should have idea about user requirements and should be able
to explain the bug analysis to the team lead/project
manager based on the requirements.
**A clear discussion will leads to conculsion.
** arguments leads to further problem's.
Providing him a snapshot with bug.
providing him the test case ID.
providing him the user requirement specifications.
and a copy of actual and expected results of the test case.
Ultimately the ball will remain in tester's court as he
should be able to attach screenshot along with detail
analysis of the requirement and how it can be reproduced.
Even after that dev is unable to reproduce in his
environment, then lead needs to show the bug in your own
environment. it could be possible that the bug is surfacing
in your machine because of wrong version of internet
explorer or other config issues.
After confirming its a bug from your end always take screen
shot & attach it while reporting bug.It may possible that
developer is not following recreate steps which are
reported by you in bug reporting tool.You can reproduce bug
& show it to developer.Still developer is not ready to
accept it then you can discuss this issue with your test
lead then test lead will settle this issue.
not exactly kannan,
The screen shot will be an secondary thing.. when the
developer says that it is not a bug we suppose to send the
'requirement ID', i guess its enough to identify where the
bug is if not then we can attach the 'screen shots' as the
proof of the bug.
regards,
Dhesi.
1Who performed sanity and smoke testing :-- developers or
testers ? Explain with example and prove ur answer.
2 Company has developed a project for company B, company B
has to introduce this project into the market. The
acceptance testing is performed at Company B. is it called
as alpha testing or beta testing ? Explain with example and
prove ur answer.
Please anybody explain the interaction of tester with
developers and team lead regarding bugs or any issue, how
they interact? How they discuss... Plz be clear in detail
Suppose " You are given a build with 5 modules to test as
per the Customer request after finalization of SRS, But the
SRS contains only documentation about 4 modules. On what
basis you will continue the testing of 5th module." ?