Respect is a major player when it comes to creating and maintaining a cohesive team, and plenty of testers today feel they’re lacking the respect of their peers. With test automation sometimes being seen as some magical solution to fixing bugs, the usefulness of manual testers has come into question.

When executing test modules, an interesting question to ask is “What needs to happen with issues that are found?” Hans Buwalda suggests making a distinction between issues found during a sprint and after the team has declared the functionality under test "done"—and describes how to proceed from there.

Unlike waterfall, where people had to do their best to explain the value of automation, agile more naturally promotes that need for these tools through its rapidity and integration of testing throughout the development process. Agile assumes automation is the key ingredient of your mission strategy.

In addition to the typical Internet-related security concerns, applications are being made specifically for IoT devices, all of which bring about additional security concerns that quality assurance teams need to consider.

Mobile or PC apps that crash, have poor user experience, don’t run smoothly, or lack features give your customer the idea that whatever they bought didn’t get the tender, loving care it deserved—even if they know the issues can be fixed in a later release.