Test Lead's question

[original PM]

He just needs to make sure the risks are documented and if Programme accepts the risk then he or she has done their job

Too many testers think their job is to deliver a defect free deployment

Cover your ar5e and invoice away

Well it is not the job of the tester per se but it is the job of the testing team to ensure that all defects are gone.

That is not to say that the system does exactly what the customer wants but that technically the code works and does not error.

If you come out of testing and say you have 186 defects and therefore testing has been a success you are wrong as the whole point of testing is to ensure the system can be deployed to the business.

If you come out with 186 change requests then fine yes testing has been succesful.

 

[Dallas]

Well it is not the job of the tester per se but it is the job of the testing team and stakeholders to agree the level of tolerance and signoff the workaround and 2nd phase.

FIFY

 

[Mich the Tester]

Well it is not the job of the tester per se but it is the job of the testing team to ensure that all defects are gone.

No, the testing team can try to find as many of the defects as possible. It does not repair them and can only use the available techniques and tools in the available time to find them. No tester worth his salt would claim to be able to find all the bugs in a system; any tester who claims that just doesn't understand testing.

 

[original PM]

Sorry yes I do not expect all bugs to be found what I expect is that all various user stories, business processess etc etc etc have been tested and found to work.

if bugs exist elsewhere then yes they will not be found.

however for me it is still down to the test phase to ensure the product is bug free based on the agreed test criteria

 

[MicrosoftBob]

Both

 

[Mich the Tester]

Sorry yes I do not expect all bugs to be found what I expect is that all various user stories, business processess etc etc etc have been tested and found to work.

if bugs exist elsewhere then yes they will not be found.

however for me it is still down to the test phase to ensure the product is bug free based on the agreed test criteria

Ah yes, but that's not the problem my friend has; his problem is that he's found a load of bugs and the PM still wants to push on. Personally I don't have a problem with that because while I might know the software risks and some of the hardware risks, I don't have a complete picture of the business that's using the stuff and so I can't make the judgment call of whether to go ahead. I can however inform the PM and then act in such a way that I can continue invoicing.

 

[original PM]

Ah yes, but that's not the problem my friend has; his problem is that he's found a load of bugs and the PM still wants to push on. Personally I don't have a problem with that because while I might know the software risks and some of the hardware risks, I don't have a complete picture of the business that's using the stuff and so I can't make the judgment call of whether to go ahead. I can however inform the PM and then act in such a way that I can continue invoicing.

Ah yes indeed - I have tested there are still many many bugs and we should not proceed - but PM's neck is on the line so he accepts the risk....

and the whole thing becomes a pile of tulip!

stupid Project Managers!

 

[suityou01]

Tell your test Monkey mate to STFU. Prima donna's

 

[Mich the Tester]

Tell your test Monkey mate to STFU. Prima donna's

Says Mr Bugmaker himself.

 

[SpontaneousOrder]

Ok, it is your job to contest the PM. WHoever is paying for it has the final say.
deleted my previous post.