As the Agile environment has efficient principles that allow quick responses to changes and the ability to deal with uncertainty, exploratory testing may seem like a perfect match for such projects. However, this is only partially true. In reality, diverse reasons impede its usage in Agile projects, and companies should take them into account before designing QA strategies.
The best way to ensure users have a positive customer experience is to use error monitoring to catch errors in real time so you can respond immediately. Error monitoring provides hope for avoiding poor app store ratings and for keeping customers satisfied.
Testing continuous technological change can seem like chaos. There are many challenges that need to be managed, such as unavailability of power, excessive temperature, incorrect configuration, unexpected behavior of services, network downtime, and processing slowdown in production. By deliberately engineering chaos, we’ll be able to discover many of our systems’ weaknesses before our users do.
DevOps does speed up your processes and make them more efficient, but companies must focus on quality as well as speed. QA should not live outside the DevOps environment; it should be a fundamental part. If your DevOps ambitions have started with only the development and operations teams, it’s not too late to loop in testing. You must integrate QA into the lifecycle in order to truly achieve DevOps benefits.
QA testers often take on more of a role than just testing software code. When the team needs help, QA should lend a hand in assisting with business analysis, customer communication, user experience, and user advocacy.
As if working at Lego isn’t fun enough, Sherri Sobanski delights in finding new ways to test. Faced with a situation requiring a complete product redesign, she shares the route her team took to overhaul testing.
QA is often considered that lonely department of testers whose job is to find defects before the customer does. It's not always glamorous, but QA deserves to be recognized as a key cog in the testing machine. To achieve business goals, it is Susan Bradley's view that the QA process needs to be embraced throughout the entire software development lifecycle.
Melissa Benua, director of engineering at mParticle, chats with TechWell community manager Owen Gotimer about the importance of whole team quality, how to get started using the test pyramid, and how developers can start writing testable code.
Greg Paskal, test automation lead at Ramsey Solutions, talks about data lakes and how to effectively use data visualization. Done well, data visualization should help practitioners, managers, and stakeholders easily consume, understand, and act on the information the visual displays.
In this interview, Sam Kaufman, the founder and CTO of BugReplay, explains why most teams don’t put enough emphasis on bug reporting—even though agile and DevOps have made it even more important than before. He also details where DevOps can improve and where he sees it in five years.
Are you a leader with a quality problem? Every organization struggles with quality at some point in their product lifecycle. Knowing what to measure and how to build a culture of quality with specific and actionable methods is key.
Too often quality is identified as solely owned by the quality assurance team. By taking a broader approach to roles, tools, and ideology, you can restructure your vision of how to provide rapid, frequent releases that empower all delivery team members.
Modern software development organizations often build teams around features. Unfortunately, these teams tend to become siloed, building tools and processes without being aware of how other teams have solved the same problems.