As a software testers, you may feel like you bear the brunt of the blame when things go wrong with an application. It’s unfair, but that’s the way the cookie often crumbles. Author and tester Namita Arora is all too familiar with this perspective of testing professionals. She notes that it’s weird that even when the quality of the product matters most from an end user perspective, software quality professionals are many times viewed as the “poorer cousins” of developers.
Arora believes that one factor keeps testers from receiving their dues: it’s the sense of negativity attached to the role itself. She asserts that software development teams need to move away from “breaking the product” culture to “building a successful” product culture. The remainder of her article is dedicated to exploring several concepts that can change the way testing teams are perceived. Read it here.
Regardless of whether you’re a “made” tester, driven to the profession by a lack of other options, or a “chosen” tester, having purposefully decided on the career, you have the ability to thrive as long as you invest the time and effort it takes to gain experience and understand the technicalities of the field.
As they say, “A passionate tester is more beneficial than an experienced developer.”
For testers, there are several goals that must remain top of mind throughout the testing process. Of course, it’s expected that testers find and prevent bugs, but the job doesn’t end there. For a look at the top seven major goals for software testers, dive into the full article here.
As the world of software testing leans more and more toward automation, many may wonder what’s in store for manual testers and their craft. Automated software testing brings a number of benefits to the table. It allows for precise and consistent executions on all iterations, it allows teams to save time and make ideal use of resources with constant and ongoing test executions, and it allows teams to execute a wide range of tests that negate human error.
It’s clear why so many organizations have adopted automation, but is it time to say goodbye to manual testing for good? The answer is no. Despite the overwhelming benefits of automation, there are certain testing scenarios where automation does not prove handy. For a look at the kinds of scenarios that warrant manual testing and the reasons this practice isn’t dead in the water, check out the full article here.
If you’re at all familiar with Agile software development, you know that communication is favored over documentation. But what does this mean for QA teams who still need and want to document testing processes to provide structure and guidance?
Michael Durrant posed this question to the Software Quality Assurance & Testing forum and is simply wondering what kind of high level structure in his QA team’s documentation would accommodate an Agile environment.
What are your thoughts? Contribute them here.