The status of the testing phase and the role of the software tester are challenged and changing as organizations transition from a classical waterfall methodology to software development towards Agile approaches like Scrum. In his article “Reinventing Testers and Testing to prepare for the Future”, Patrick Prill shares his opinion about this situation and provides some hints for the evolution of software testing and the software tester role.
It is usual that software testers job descriptions will often mainly emphasize the business and technical requirements: experience working in the banking sector, Agile Testing, Selenium, etc. As in many other role however, successful software testing is more about a mindset and soft skills. In this article, Simon Frankish shares some keys attributes that should be considered when hiring a tester.
Since the publication of Peopleware by Tom DeMarco and Tim Lister in 1987, the importance of people in the success of software development projects could not be underestimated. This is also true in the software testing domain. In this article, Anna Royzman discusses some of the essential skills of modern software testers that managers should nurture and develop.
Software testers are limited by their role. Testers are only allowed to be testers. We need to break the current tester mold and replace it with a new role… the tester. The tester is a much bigger role than it currently is. Its much bigger, it much more valuable, its higher status and its much more fun. So do you want to be a tester? Or would you rather be a tester?
Test Engineering culture emphasises on quality ownership by all involved in a project and redefines the role of testers as engineers as quality enablers instead of gate keepers. This talk shares the experience to build a test engineering culture across the organization, how does it vary with the size of the team and the company and the role of software testersin building this culture by enabling others with tools and processes for quality improvements.
People are the most important success (or failure) factor in software development projects. This is also true in the software testing field. In his article “Testing Your Emotions”, Stephen Janaway explains why it is very important that software testers understand their emotions as they can be a great heuristic to guide testing.
Most of us have had to deal with red builds blocking our testing or have been told to test on flaky environments where half the issues you find would ‘never happen in production’. As a tester, I used to think this wasn’t my problem. What happens though when a thinking tester decides this is her problem and wants to be part of the solution?