In this episode, recorded February 10, 2016, The Testing Show talks Super Bowl aftermath, analytics in sports and how accurate they are (or not), expectations and wild guesses, and the benefits of having a beginner’s mind to a situation and how that may give a person a better chance at seeing how things will turn out (it also shows pretty clearly who on the panel actually pays attention to football).
We talk a bit about legacy systems and what happens when critical systems go down (the IRS being a prime example), and the fact that organizations with legacy apps are reorganizing around Scrum and Agile, not so much for new software development, but to help maintain and continue development on legacy systems. Can we do better? We think “yes”!
In this episode, The Testing Show crew takes a trip to New York City to participate in James Bach’s presentation to the NYC Testers Meetup. We discuss a bit about the GitHub site outage, and the ramifications of inevitable downtime. This leads into the main topic, which is “what do we do when we don’t have enough testers?”
Is testing really a bottleneck, or is it set up in a way that delays are inevitable? What can we as organizations, and as testers, do to mitigate these issues, and what means do we have to change the process?
In this episode, The Testing Show crew is joined by Yaron Kottler, Qualitest’s Americas CEO. We discuss the changes at Yahoo and the elimination of most dedicated software testers, how this change is happening in a variety of companies, and what these changes actually mean for the dedicated testing role, and what may happen in the future.
We discuss the idea of software testing as a trusted advisor to an organization, and the benefits of wham that role works, as well as the frustrations and costs when that role does not work.
In this episode, The Testing Show tackles the NEST Thermostat, early release of inmates in Washington state due to a computer error, and what can we do when our password site gets hacked?
We discuss test design, bug advocacy, long term auditions,
and think about how robots can help you see the way software testers pivot