I get this a lot, and thought I'd deal with these as a group. For the record: a strategy helps you plan. Good ones tend to arise either from a closely involved team, or after plenty of deep questions from some sort of expert. There are no genuine templates, only examples. Strategies - testing or otherwise - are as different and unique as the projects they serve. The more all-encompassing the strategy, the shorter it should be; no-one needs a 50-page strategy. There is always a strategy, and you can find it by following the decisions - the written strategy may not be the same as the actual strategy.
Here are some examples of the genre . . .
Can you please send me few examples and templetes for Test Strategy....
Thanks for getting in touch. Could you tell me a little more about your project and your goals?
About my project... The project is Retail management(Web-Based Application) and its new project... the development area is J2EE. Now we are in Functional Designing phase... hope after finishing the functional design spec. we are planning to come up with Test Strategy and Test Approach and Plans...
My Ultimate goal is to deliver a Quality product to my Client...
So, can you please send me few sample Test Strategy Templates for it... hope you will do needful to me...
Thanks for this information. It sounds as though you are at a good point in the project to be developing a test strategy. You may already have a workable idea of the technical constraints and potential patterns of failure that could drive aspects of your test design. However, what will be more important to your test strategy are the values that inform your test decisions, and you've not included information about what they might be.
Technical environment and business context are important to a strategy, and it might help to see a strategy for another project in the same environment. However, there are no publicly-available examples I know of that cover this particular pairing.
I've worked on products that have a fair fit with your description. The test strategies for the projects were very different, reflecting the values and priorities of the organisation. For commercial and copyright reasons, I can't supply copies of those strategies to you.
I feel strongly that a test strategy is something that should *not* be created from a template, and I don't supply test strategy templates - either for free, or during a paid interaction. I try to make my position clear here: http://www.workroom-productions.com/strategy.html . The page does include a checklist, which may serve as a stimulus for discussion within your team.
I'm sorry not to be of more help. If you would like to speak with me on this, please call me.
I am working as a Test Manager for one of the big program has teken up my company. Program contains number of projects and applications on different technologies like Java, ATG, Web Services, Data Stage, Mainframe COBOL etc... and it has nearly 250 inbound and outbound systems. Can you please provide inputs for test strategy for these kind of programs? and it will be grate if you provide any sample or template for test strategy.
Thanks for your enquiry. Your project sounds substantial, and I don't think it can be dealt with in an simple email exchange. If you would like to speak with me on this, please call me during London business hours.
Please note: I don't supply test strategy templates - either for free, or during a paid interaction. I try to make my position clear here: http://www.workroom-productions.com/strategy.html . The page does include a checklist, which may serve as a stimulus for discussion within your team.
I'm having a self study training on test strategies and going through your website was wondering if you had Knowledge of examples or references for Test strategies of payroll based systems of which I am conversant with a few. Any help will be appreciated
I can't give you any examples that are specifically tuned to payroll systems. The purpose of a system is important to a strategy, but so are the values of the organisation, the technology of that system, the power and constraints of the potential resources.
If you're working on a self-study course, you could do worse than study the test strategies used on the payroll systems you are familiar with. You are likely to find the actual strategy is very different from the stated strategy - if one even exists. You could also write two or more *different* strategies for the *same* product and context, to expose potential alternatives and underlying rules. Try to keep such strategies short; less than 3 pages or so. I have a rule-of-thumb - the higher-level the strategy, the shorter it should be.
I am a Senior software tester and working for a consultancy company called [obscured supplier]. I am trying to prepare a Test Strategy document for the client [obscured client].Is this any free consulation given by the Work room Productions based on test strategy document .Please let me know this.
Thankyou for your enquiry. Please let me know your ideas so far - and what you might require from consultancy. I notice that [obscured client] are a US-based healthcare company.