Which job?

It's quite simple, have you been given a full brief on what they want you to do? If so, follow it and do it, if not, ask for one.

They just said 'Do a detailed test execution plan'.

I had a look on google last night and couldn't even find an example of one on the whole of t'net :(

I ask for more information and boss says 'Er, what do you mean you don't know how to prepare a detailed test execution plan? You seem a bit out of your depth you are a test manager arn't you?' ...

All very messy .. I'll madly google around again tonight :/
 
Just to clear something up, are you just not able to comprehend what you are required to? Or is it an issue with the managers expectations. Sounds to me like you need to go and sit down with her and explain that you are stumped as to her criticisms and what it is that she required from you.

Managers tend to be the biggest talkers of **** that I have ever come across so it is worth finding out exactly what she is after. I find that miscommunications are usually resolved by a friendly sit down with the relevant party.
 
They just said 'Do a detailed test execution plan'.

I had a look on google last night and couldn't even find an example of one on the whole of t'net :(

I ask for more information and boss says 'Er, what do you mean you don't know how to prepare a detailed test execution plan? You seem a bit out of your depth you are a test manager arn't you?' ...

All very messy .. I'll madly google around again tonight :/

You won't find any on the internet, they are normally distributed amongst project team and stakeholders only.

They are also normally confidential, and once UAT is done and its signed off they will be archieved or destroyed.

Google is not going to help you.

Even if you do find one, it will be to a totally different brief.

I'd go back and ask for a mission statement or give up.
 
They just said 'Do a detailed test execution plan'.

I had a look on google last night and couldn't even find an example of one on the whole of t'net :(

I ask for more information and boss says 'Er, what do you mean you don't know how to prepare a detailed test execution plan? You seem a bit out of your depth you are a test manager arn't you?' ...

All very messy .. I'll madly google around again tonight :/

what's so hard about a detailed Testplan? Surely you came across those in your old job?

I'd give you an example from my company, but they're confidential, sorry ;)
 
Lol finding this quite quality really.

If by any remote chance said managers initials are VP let me know, but lets assume they aren't.
Its 1 of 2 things, BB here has never worked for a decent professional organisation with rigorous UAT plans or
2, the manager is clueless.

I'm afraid I suspect 1. He says himself its all been documented out for him before and now hes got to think and add value hes fish out of water.

Im slightly intrigued by the terminology though, everyone assuming 'Do a detailed test execution plan' means "Do a detailed test plan". I am wondering if by some sliht chance its a bit more systems testing that pure UAT...
 
Last edited:
Why didn't you ask for an example of what they expect of a test execution plan, degree of detail and planning. Key things and formatting that is acceptable to their norms.

Give them some BS about trying to make it fit in with them better to hopefully eek out enough information to help yourself. Currently you are being too vague as to any task at hand for anyone to really help you as you have a single phrase of you can do 85-90% of it all, but not this one thing.
 
[TW]Fox;18490653 said:
I presume it's a plan detailing the process to be followed when testing a new system before it goes live.

That.

But it does involve more than just the IT, its got to involve schedules for the stakeholder 'customer' to test and accept etc.

It's not really something anyone away from it can help with. Neither will google.

I'm not saying this to be nasty, I'm saying it because I've been unfortunate to go through a couple. Without the mega pay.
 
Last edited:
Why didn't you ask for an example of what they expect of a test execution plan, degree of detail and planning. Key things and formatting that is acceptable to their norms.

I'd think something like this would make sense, just ask them for a previous example of a test execution plan that they've had for a previous system. Explain that you'd like to understand precisely what it is they're looking for as there may be idiosyncrasies in their specific company and you want to make sure that you are going to provide a solution that works for them.

It's an option that doesn't involve letting them know exactly how little you know, if however they don't have one or aren't willing to let you see a previous example then you're still up the creek. It doesn't explain what you've been doing/not doing since you started the contract but as a contractor you should be able to come up with something for that.

If you have no luck getting a previous plan from them then I think you should be looking at bailing because you're doing no-one any good there.
 
The thing that confuses me here is that the reason a contractor is paid as much as they are is because they arrive, hit the ground running, and do the job. They dont need to ask for examples. They dont need to have management checking they are good enough. They just get on with it.

britboy is unable to do this so should look for a normal job.
 
Back
Top Bottom