| || |
Testing strategy into packages
I have been working on a web usability company now for 1½ years and been working with the overall company testing strategy and testing processes. We develop user friendly web sites and are about 100 employees in one country. We mostly make intranets and external company web sites. Now I recieved a request to have the testing strategy devided into different packages for the customer/project manager to chose - small, medium and large. Small packages with only the absolutely most important tests for small projects, medium packages for medium projects and large test package with lots of testing for large projects.
Maybe it's hard for someone not on the company to decide but I am asking for some tips and advice how to do this. I have kept asking these questions to my colleagues for 1½ years and I recieve no reply. Therefore, I have to come up with something myself.
Which tests do you consider to be parts of the small, medium, large packages and why?
Which are the most important tests to perform, according to you?
Please explain what you are trying to do in more detail. I cannot tell what they are asking for.
Hi and thank you for your reply!
Originally Posted by bklabel1
I have written a testing strategy and since the company I am working at, is so immature when coming to test (they see it as hard, unneccessary and such), almost noone have read the testing strategy. So, the plan is to break it down into packages. The project managers have problems chosing which tests will be good for their projects and they see it as a hard thing to do, to discuss it with me since I tend to have a high ambition when coming to test, when they have not.
So, three or more packages to chose from, like:
Package Small for small projects - Includes unit testing, stress testing, browser compability testing
Package Medium for X sized projects - Includes bla bla bla
Package Large for X sized projects - Includes bla bla bla
I have to define what's included in these packages for the project manager to chose from. But I do not know which tests should be included. I have asked the question to my colleagues and the CEOs and such but I recieve no answer. They have what so ever no clue about how test works and which tests are good or what they want. So I have to decide myself and present a first draft to see their reactions.
Are you following me now?
The question is: Which tests should I consider putting into these three different packages? Which tests do you consider as major/critical, minor and such? Which tests should always be performed, no matter what, according to you? And so on..
Test methodologies, test strategies and test types are explained in this response. Expert John Overbaugh uses extensive examples to explain the various testing types.
[What are the] difference[s] between a testing methodology and testing strategy? What are most commonly used testing...
Sign in for existing members
Continue Reading This Article
Enjoy this article as well as all of our content, including E-Guides, news, tips and more.
corporate email address
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.