Hi guys, i want to know whether testers job is to just to find the bug and give it to developer for fixing or to mention why that bug is happening.
Printable View
Hi guys, i want to know whether testers job is to just to find the bug and give it to developer for fixing or to mention why that bug is happening.
Testers job is not only limited to find and report the bug, but he has lot of other roles.
Some of the roles which the Tester in an organization should perform are:
1. Analyze the requirement document and generate the possible test scenarios out of it.
2. To estimate the identified scenarios for its complexity, whether simple, medium or complex.
3. To write test cases for the identified scenarios and to write test script if the testing is done using automation tools.
4. To cross review the test cases written
5. To log bug for the failed test cases. While raising the bug the notes should be clearly mentioning the cause of the bug.
6. To retest the defect once it is fixed, and change the status accordingly.
Above mentioned were the roles of a tester who is a fresher or having below 1 or 2 years of experience, and for a more experienced person the roles will differ and will be more.
Hi Balaji,
A tester's role would definitely not be limited to just reporting a bug to a Developer.
But I would say based on the designation of a tester responsibilites could vary. Like SridharrGanesan has mentioned, it could comprise of all the following plus a few additional responsibilites OR incase of Junior tester or Test Executors as called, would be limited to only executing testcase and logging defects.
On a General note though, a Tester would have to -
1) Study SRS as well as FRS and using use-cases come up with Test Scenarios.
2) Based on the scenarios which indicate workflow, come up with detailed testcases for specified functionalities.
3) Execute testcases and document the test results
4) Log defects with proper documentation explaining the circumstances when and how the defect occurs.
5) Follow up on the fixed defect in terms of re-testing it and regression test the affected modules...
Cheers.....
HI,
I feel its always better to back up ur defect findings with some amout of investigation done. Whether it is the cause or discrepancy from requirements.
Reshma
[QUOTE=balajip82;21460]Hi guys, i want to know whether testers job is to just to find the bug and give it to developer for fixing or to [B]mention why that bug is happening.[/B][/QUOTE]
[B]mention why that bug is happening.[/B]
Tester never mention, why bug is happening, even if tester can fix the bug, he will never do it. His task is to find and report bug as soon as possible.Only developer will fix the bug and it's developer task to see why there is bug?
[QUOTE=jainbrijesh;21511][B]mention why that bug is happening.[/B]
Tester never mention, why bug is happening, even if tester can fix the bug, he will never do it. His task is to find and report bug as soon as possible.Only developer will fix the bug and it's developer task to see why there is bug?[/QUOTE]
As far as my experience is concerned, I feel stating a defect is important but if you can also depict the cause that makes you a gud tester. we cannot and should not work in closed ended KRA's in practical life.
you can do so, may be that can help you if you are doing white box testing, as per black box, i never feel so.Although i know the root cause of the bug, still never feel to comment, as it can spoil our relatioship with developers.
nice info!!!!!!!!!!
Hi Balaji,
The role of a tester is "To find out bugs as early as possible and make them to get fixed"
Still there are some other roles that a tester has to perform.
1.He should communicate truth.
2.Document his things
3.Have to suggest the Dev team ,that it can be done in a better way..
4. should have a smooth communication with the developer when he is not accepting the bug you raised.
These are some of the things i know.....
Thanks,
Krishna.
--The Undertaking of a New Action brings New Strength---
[QUOTE=rzilpilwar;21514]As far as my experience is concerned, I feel stating a defect is important but if you can also depict the cause that makes you a gud tester. we cannot and should not work in closed ended KRA's in practical life.[/QUOTE]
Agreed, and if you have already come across any such defect and know the solution for it then you can always suggest the possible solution for it as comments. Implementing it or not.... should be left to the developers.
what is difference between sevority and priority