Need some suggestions!

mailramaa@gmail.com · 20-09-07, 03:55 PM

Hi Friends..
I have newly joined a company in which the testing process is different..

For every development team there is a tester tied up, who will connect to Developer system and test the functionality(task).

After it has passed this testing, it is given to build and after integration, it is tested at the build level by another QA team

Now the problem in this is the Dev-Tester often finds bug that might not be Bcoz of the particular developer's task. But is a pre-existing one. So, we cant fail the Dev task.

But if the same goes to build and tested by the QA Team, the particular task gets re-opened coz of the same bug as above. This is becoz the QA team wil not bother to check the source of the bug.

In this case the task tested by you is failed and your effort of finding the bug at the developer level is waste.
Can any one suggest a way to stop this....

**sk_kireeti** · 20-09-07, 04:31 PM

Rama Rajeswari,

To be frank, here is the approach you should follow to track these kind of issues.

If a bug in old code or bug in other developer's code is stopping us from completing a task or functionality, then either QA or developer has to log another new bug with details against specified person and that should be made as base bug for this or make it a dependent bug. Don't close the actual bug until the new bug is solved.

It means, after the new bug is solved, test your functionality and make sure your flow is passing. After verification only you have to close your bug.

If this kind of process is not already in place, then that initiation should come from managers. You can suggest this process change :)

Regards,
Krishna

mailramaa@gmail.com · 21-09-07, 03:54 PM

Hi,

As of now, we have started logging the bugs discovered while testing a task, which is not a root cause of the bug , but still the task is related to the bug.

We log this bug as related to the previous task and have of a refernce of ths task in the bug.

Now though the task gets closed , we check all the functionalities of the related tasks also once the bug gets fixed.

Thanks for your suggestion Krishna..!!

20-09-07, 03:55 PM	#1 (permalink)
mailramaa@gmail.com Senior Member Join Date: Oct 2006 Location: Pune Posts: 199 Thanks: 20 Thanked 41 Times in 26 Posts Rep Power: 9	Need some suggestions! Hi Friends.. I have newly joined a company in which the testing process is different.. For every development team there is a tester tied up, who will connect to Developer system and test the functionality(task). After it has passed this testing, it is given to build and after integration, it is tested at the build level by another QA team Now the problem in this is the Dev-Tester often finds bug that might not be Bcoz of the particular developer's task. But is a pre-existing one. So, we cant fail the Dev task. But if the same goes to build and tested by the QA Team, the particular task gets re-opened coz of the same bug as above. This is becoz the QA team wil not bother to check the source of the bug. In this case the task tested by you is failed and your effort of finding the bug at the developer level is waste. Can any one suggest a way to stop this.... __________________ Regards, Rama " Failure is the oppurtunity to begin again, more Intelligently! "
Offline

20-09-07, 04:31 PM	#2 (permalink)
sk_kireeti Super Moderator Join Date: Feb 2006 Posts: 2,379 Blog Entries: 4 Thanks: 118 Thanked 319 Times in 238 Posts Rep Power: 60	Re: Need some suggestions! Rama Rajeswari, To be frank, here is the approach you should follow to track these kind of issues. If a bug in old code or bug in other developer's code is stopping us from completing a task or functionality, then either QA or developer has to log another new bug with details against specified person and that should be made as base bug for this or make it a dependent bug. Don't close the actual bug until the new bug is solved. It means, after the new bug is solved, test your functionality and make sure your flow is passing. After verification only you have to close your bug. If this kind of process is not already in place, then that initiation should come from managers. You can suggest this process change :) Regards, Krishna __________________ Looking for trainees for a start up company
Offline

21-09-07, 03:54 PM	#3 (permalink)
mailramaa@gmail.com Senior Member Join Date: Oct 2006 Location: Pune Posts: 199 Thanks: 20 Thanked 41 Times in 26 Posts Rep Power: 9	Re: Need some suggestions! Hi, As of now, we have started logging the bugs discovered while testing a task, which is not a root cause of the bug , but still the task is related to the bug. We log this bug as related to the previous task and have of a refernce of ths task in the bug. Now though the task gets closed , we check all the functionalities of the related tasks also once the bug gets fixed. Thanks for your suggestion Krishna..!! __________________ Regards, Rama " Failure is the oppurtunity to begin again, more Intelligently! "
Offline

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
My frist interview... plz give me suggestions to face it effectively	nsumanth_4u	Success Stories	6	25-01-08 05:31 PM
need ur valuable suggestions	kiranmayi_p1	Ask for Suggestion	9	15-11-06 12:11 AM
thanks for good suggestions	sarabjeetdhillon	Ask for Suggestion	4	06-11-06 10:34 AM
hi, need your suggestions	vishwanath_jen	Introduce yourself here	6	18-09-06 05:16 PM

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)