As software development companies grow, it becomes more important to have a formal quality assurance (QA) process. In this article, Veronika Olshevskaya discusses six mistakes that you might do when you set up your QA department and suggests solutions to avoid making them.
In theory everyone on an Agile team is responsible for software testing, but in practice this is rarely the case. Learn how to make quality a team sport in Scrum teams.
Software testing is an activity that is not always well considered in the software development community. When companies use a “silo” organization, the relationships between developers and testers are often tense. Developers complain that testers are not understanding the system and testers complain that developers write poor quality code. In this blog post, Emma Armstrong give some hints to help the software tester engineer to portray his role in a positive way.
Agile software development approaches encourage a collaborative setting in software development projects. Software developments and software testers and quality assurance people have to create a better context for working together. This article discusses how programmers can improve their relationships with the software quality assurance people.
Distributed software development teams and distributed software testing are here to stay. In this article, Lisa Crispin asks “How do we get quality software in these situations?” and proposes some hints on how to get good results when you perform software testing with distributed teams.
Johanna Rothman first started managing a software testing group in 1988. Since then, she managed software testers, coached testers or coached project managers and managers in what they should—and should not—expect from testers.
By working together to create the set of tests and then determining where that testing belongs, we can increase efficiency, reliability and reduce debugging time for failures in the future.