Our notable partnerships give us access to the best resources and tools for the job.
Get software testing training resources:
The phrase “test strategy” can refer to the general way, independent of project, that an organization carries out its testing, which often includes common patterns such as analytical risk-based testing, methodical testing, reactive testing, and model-based testing. The phrase “test strategy” can also refer to a document the describes this general way of testing.
This document is used to help determine the amount and quality of testing (or its scope) that is planned for or has been performed on a project. This analysis results in the testing effort being assigned to a particular Testing Level category.
Categorizing the quality and thoroughness of the testing that has been performed is useful when analyzing the metrics for the project. For example if only minimum testing was performed, how come so many person-hours were spent testing? Or if the maximum amount of testing was performed, how come there are so many trouble calls coming into the help desk?
This is an excerpt from my book, Expert Test Manager, written with James Rommens and Leo van der Aalst. I hope it helps you think more clearly about the test strategies you use.
A test policy contains the mission and objectives of testing along with metrics and goals associated with the effectiveness, efficiency, and satisfaction with which we achieve those objectives. In short, the policy defines why we test. While it might also include some high-level description of the fundamental test process, in general the test policy does not talk about how we test.
The document that describes how we test is the test strategy. In the test strategy, the test group explains how the test policy will be implemented. This document should be a general description that spans multiple projects. While the test strategy can describe how testing is done for all projects, organizations might choose to have separate documents for various types of projects. For example, an organization might have a sequential lifecycle test strategy, an Agile test strategy, and a maintenance test strategy.
Recorded February 26, 2018
Recorded August 10, 2015
Recorded June 12, 2015
Recorded September 5, 2014
Recorded May 22, 2014
Recorded November 7, 2012
Recorded May 22, 2012
Recorded April 3, 2012
Length: 1h 10m 9s
“Schools of Testing”: Useful Paradigm or Negative Influence? Are there really four different “schools of testing”? Do you have to belong to one? Or are there just different testing strategies, to be selected and blended as appropriate? Has the concept of “schools of testing” promoted clearer thinking about testing, or has this concept actually created a useless schism, sowing conflict and slowing growth of the profession? In this debate, Rex Black argued the negative side of the case, being one of the leading critics of the concept of “schools of testing.” One the other side, you’ll hear one of the originators of the concept, Cem Kaner, argue for its benefits. Love it or hate it, you can hear both sides and make up your own mind.
Length: 0h 38m 0s
For nearly ten years, RBCS has run a highly successful free webinar series. In 2018, we’re adding the Two Points of View at Two series to our monthly webinar rotation. In each of these sessions, Rex Black will talk with another software luminary about topics of mutual interest, where the two have some different views, and then Rex opens the floor to questions.
In this inaugural session, Rex is happy to welcome Maaret Pyhäjärvi . Maaret’s bio describes her as feedback fairy with a day job at F-Secure, where they call her a Lead Quality Engineer. She identifies as empirical technologist, tester and programmer, catalyst for improvement, author and speaker, and community facilitator and conference organizer. You can catch her latest thoughts on her blog at http://visible-quality.blogspot.fi
In this session, Rex and Maaret will discuss tester-developer collaboration and the relationships between testers and developers. How to approach developers for collaboration? How do testers-developers ratios affect relationships? What about people who move between tester and developer roles? Join Rex and Maaret to hear their thoughts and ask your questions.
The Expert Test Management Operational Test Manager Boot Camp, created by Rex Black, past President of the International Software Testing Qualifications Board (ISTQB), past President of the American Software Testing Qualifications Board (ASTQB) and co-author of the International Software Testing Qualifications Board Expert Level Syllabus Test Management, is ideal for testers and test teams preparing for certification in a short timeframe with time and money constraints.
The Expert Test Management Strategic Test Manager course, created by Rex Black, past President of the International Software Testing Qualifications Board (ISTQB), past President of the American Software Testing Qualifications Board (ASTQB) and co-author of the International Software Testing Qualifications Board Expert Level Syllabus Test Management, is ideal for testers and test teams preparing for certification.
This hands-on course provides test engineers with the ability to define and carry out the tasks required to put the strategy into action and is ideal for testers and test teams preparing for certification. In preparation for the exam, participants will learn the subject matter behind the test standard and deepen their understanding by working through case studies and exercises. In group exercises, typical review situations are played out and analyzed.