vvk

 Profile Answers by vvk 

• Feb 13th, 2006

 

You have to perform 8 tests

Prasad Meduri

• Feb 14th, 2006

 

This is an interesting question??

We have to keep couple of things in mind.

1) The fixed entries will be updated in the BugTracking tool with your ReTest comments... is n't it? That's for sure.

But coming to the remaining 5 entries also you will write ReTest NOT OK in the BugTracking process. Are you doing like this???

Also the 3 new bugs you have found in the next build(previously they were not there when you found 10 bugs am i right???? ), i think you have to keep in mind and when the next build comes for testing you have update in the BugTool or else... i dont know....... that depends on how you get the builds,

but for a standard company devolopers will have nightly builds and at regular intervals (weekly,twice in a month...) test builds will come for the testing team...then only you are supposed to write your Retest Comments otherwise you have to consult the concerned devoloper and LOG it straightaway.

But a small suggestion in your communication,dont mind

1) we never assign bugs to devoloper directly, it goes to the database, manager will analyse it, sends you back for your assessment, you will reproduce it, write your comments,manager reviews it and finally he/she will assign it to the concerned devoloper based on the severity of the bug.

Also,

Some bugs can be open for a long time... Is it not?

That is upto the manager to decide and assign, we dont have rights to ask the devoloper vorally or whatever way to "fix" this.

There is a lot of operational and functional approach involved in bug fixing.

Dont hesitate to ask me if you need further clarification..

cheers

k_parvez123

 Profile Answers by k_parvez123 

• Mar 15th, 2006

 

Here we required to test 5 only since 5 only fixed. After the comments/reply/status (like fixed or not a bug or deferred or not reproducible etc...) came from developing people or manager or from authorized persons which is depending on company process, we have to test the remaining bugs.

Thanks,

ramesh,

QA, wipro technologies, ramesh.babumaguluri@wipro.com

raghuramsuravarapu

 Profile Answers by raghuramsuravarapu Questions by raghuramsuravarapu

• Jun 12th, 2006

 

This is very intresting question.But the qustion needs still more clarity.I am answering according to what i understood from your question.

10 defects are found while testing first time- i assume that 15 test cases are executed (because it is not mentioned how many test cases are executed while finding 10 defects).

In the revised build ,5 defects are fixed ,means i have executed 5 test cases where the defect lurks when i tested first time.

Found 3 new defects ,means i will log the 3 defects by assigning the status new .

What i want to say here is we need to execute those 15 test cases again on the revised build to know that those 10 defects are fixed or not and due to the fixing (changing the code) of these defects are there any adverse effects on the application functionality or not.This is also called as Regression testing.

Sreeni

• Oct 5th, 2006

 

You already retested the application which fixed 5 out of 10 defects(bugs). And now you have  5 old bugs. Then you found 3 more new bugs in new application. So now you have a total of  5(old)+3(new)=8  unfixed bugs.

So you need to restest 8 bugs if they fixed in new appliction(Build).

vigneshatgeek

 Profile Answers by vigneshatgeek 

• May 23rd, 2007

 

It is clearly a question of regression testing.. For instance, one(a tester) executes 20 test cases finds 10 defects.  prepares a bug report( logging the 10 defects)  and send it to the developer. The developer discusses with the client and tester and ensures that  all the defects claimed by the tester are actually defects.. once this is done.. the developer fixes the defect(in this case 5) and gives it back to the tester. therefore retesting is done.. Now the tester executes the defect-fixed test cases for the second time to find that they are actually fixed and do they have any adverse effects on other features or modules. Here it is mentioned 3 new bugs arises out of 5. therefore 8 bugs should be fixed...

testing121

 Profile Answers by testing121 

• Jun 12th, 2007

 

the question state how many are to be tested and not how they are to be tested so can you please confirm how many are to be tested and why

Sameera

• Oct 18th, 2007

 

Hi Mr. Prasad Meduri,

   I'm sorry to iinterrupt u, u've been made a comments like : "But a small suggestion in your communication,dont mind

1) we never assign bugs to developer directly, it goes to the database, manager will analyse it, sends you back for your assessment, you will reproduce it, write your comments,manager reviews it and finally he/she will assign it to the concerned developer based on the severity of the bug."

I think bug assignment process varies from company to company, b'coz in my company(I'm working for McAfee) we do assign the bugs directly to developer using bug tracking tool, even we'll have more interactions/meeting with Devs frequently. More over we can even assign the bug irrespective of the designation of the Dev, i mean that we can assign it to Dev manager/leader/engg he him self gives the solutions other wise he will reassign it to the concerned person.