Here at qa on request, we are advocates of the context driven approach to testing and incorporate it into our testing.
We work together with you, stakeholders and clients, to understand your information and testing needs, so that we can choose the testing strategies, tools, and artifacts that will be appropriate to investigate, learn, discover, and report information that’s important to you.
Working with you – the client/stakeholder
We put an emphasis on working closely with our clients and stakeholders to clearly determine the information that you are looking to get from each test request. No two test requests are the same, each test request is specific, with the stakeholders for each request looking for different things, often at different times within a product’s development lifecycle.
Prioritizing tests within your budget and timeframe
We understand the importance of budget and time, and we work with you to determine which parts of the product under test are of highest priority based on risk, information needs, time to market and other factors that may come into play. We work with you to determine platform and device coverage prioritization so that we focus tests on the highest priority features first, in order to be able to get you important information quickly.
Testing strategies based on your needs
Different strategies help discover different types of bugs. We take into consideration what your information needs are and accordingly choose test strategies that will help us discover key information and bugs related to your information needs.
We strive to focus our efforts on actual testing and test artifacts that will have some value to you. We don’t spend countless hours working on test artifacts and other documentation that you do not want, need, and have no value to you. But don’t get us wrong, we highly value test artifacts – the ones that contribute value to you!
We believe that there are no “best practices” that are best in every situation, but we rather believe in good practices that are dependent on the specific situation at hand. A practice that is “best” in one situation, is often not the “best” in another situation – therefore we believe in good practices based on context.
To learn more about context-driven testing, please visit http://context-driven-testing.com/