Test Lead's question

[Mich the Tester]

A Test Lead from another project just blew off some steam because he says he can't sign off some tests but the Project Managerman's going to go ahead anyway. He asked 'what is the point of testing if they do that?' So I answered 'the point is that you and I get paid for it; keep calm and carry on invoicing'.

Am I cynical, right, or both?

 

[eek]

A Test Lead from another project just blew off some steam because he says he can't sign off some tests but the Project Managerman's going to go ahead anyway. He asked 'what is the point of testing if they do that?' So I answered 'the point is that you and I get paid for it; keep calm and carry on invoicing'.

Am I cynical, right, or both?

Depends if he is a permie or contractor.

Either way document the fact the tests failed to cover his backside and smile.

 

[Mich the Tester]

Depends if he is a permie or contractor.

Either way document the fact the tests failed to cover his backside and smile.

Contractor.

 

[Troll]

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

 

[mudskipper]

Depends if he is a permie or contractor.

Either way document the fact the tests failed to cover his backside and smile.

This.

It's not for the tester to decide whether the failure of a test case constitutes a 'no-go'. He simply reports the issue, offers an opinion, and then says "I told you so" when it all goes tits-up.

 

[eek]

Contractor.

In which case hold nose, cover backside (laugh behind managers back) and keep invoicing....

 

[The Spartan]

As long as he's covered I don't think it matters, I guess he's just passionate about what he does. I had something similar happen to me in Switzerland and I just learned that I had to deal with it, I think this was helped immensely by the fact I was a contractor

 

[Mich the Tester]

This.

It's not for the tester to decide whether the failure of a test case constitutes a 'no-go'. He simply reports the issue, offers an opinion, and then says "I told you so" when it all goes tits-up.

NOOO! You document it all, you advise against going ahead but then when they do you help them as much as you can and send invoices for it. Never say 'I told you so'; that's a sure way to lose a contract. Better to suggest how to prevent problems next time around.

 

[Dallas]

For current project our build was completed by the bobs before even the requirements were signed off

then the rogue BA lead has his hand in undocumented/approved 'further tweaks' that i have no visibility of - yey .

I remember when SOX came out, none of these antics were tolerated, its a circus.

So yes, head down, raise all risks and publish them, then invoice

 

[mudskipper]

NOOO! You document it all, you advise against going ahead but then when they do you help them as much as you can and send invoices for it. Never say 'I told you so'; that's a sure way to lose a contract. Better to suggest how to prevent problems next time around.

When I said: say "I told you so"; I didn't mean to say it to the client - that would, as you rightly pointed out, be counter-productive. More a case of posting about your superior foresight and how awesome you are to some random strangers on an internet forum (or similar).