“In 1931, Aldous Huxley envisioned a Brave New World that would be irrevocably transformed by technology in a negative way. Our world of testing is a brave new world, but it is negative only if we allow it to be.”
Last week, expert Gerie Owen began an 11-part series on everything you need to know about tomorrow’s testing today. In her first installment, she introduces the three new worlds created by rapidly advancing technology: new devices, infrastructure models and new software delivery models. As a result of these new worlds, development, testing and deployment approaches must evolve accordingly.
For a brief overview of these new worlds (the topics Owen will be discussing throughout the series), check out her write-up here.
As the demand for highly skilled QA professionals grows, so too do the implications for organizations that unexpectedly lose key quality assurance team members. Simply replacing these individuals with a new hire of equal experience and talent is impractical, to say the least.
These days, software testers are regarded as highly as developers and programmers by organizational leaders—and with good reason! Widely publicized software failures have again and again demonstrated the immense value of QA efforts. Testers are in high demand, which means replacing QA positions can be a costly challenge. So how can your organization bounce back after an abrupt QA departure? Read this article to find out.
To preface, this is an excellent article for anyone looking to introduce agile testing into an organization. As we all know, agile has come out on top in terms of software engineering, so why isn’t agile testing as widespread throughout the industry? There are considerable challenges for testers moving from a “test-last” approach to a “test early and often” approach, however, making this transition will result in continuous performance validation which, in turn, makes for a better performing application.
For a brief overview of agile testing as well as some useful guides on how to get started with the idea of agile testing, read this full post from author Thomas Peham.
“What is the best way to measure the productivity of software testing in agile teams?”
I’m sure many of you have heard this question thrown around. More often than not, it has the power to strike up debates about how organizations are and should be measuring team and individual productivity.
Based on your own experiences, what do you believe is the best way to measure tester productivity in agile? Contribute your response here.