Related Content
 |
Visual Regression Testing: A Critical Part of a Mobile Testing Strategy Despite our best efforts to replicate customers' behavior in our test automation suites, teams often forget about nonfunctional requirements. An important one is visual perception—how users see and feel each application they use. Visual regression testing can fill a significant gap in user experience expectations. |
|
 |
2 Quick Wins for Building Context in Testing Testers fill in their assumptions about the project, domain, and technology with things they learn while testing and while talking with people. Sometimes the information they learn is good, but sometimes they miss something important. Here are two quick wins for filling in those assumptions with good information. |
|
 |
6 Steps to Achieve Realistic, Reliable Load Testing Simulating real users’ behavior gives you a transparent picture of your software's load capabilities. To reproduce users' actions accurately, you can use a request flow design from when the system is in the production environment. Here are six steps for achieving the most realistic load for your load testing process. |
|
 |
Integrating Threat Modeling into Agile Development Threat modeling helps you determine where to focus your security testing efforts when building your app. But people often wonder how it can fit into their existing agile software development process. Here are three things you can do to integrate threat modeling into your agile workflow, either early on or mid-project. |
|
 |
Merging New Codeless Test Automation with Your Existing Code-Based Test Scripts Adopting a codeless solution can be an amazing boost to quality, productivity, and tester career growth, but in most organizations, such test suites will have to be merged into existing code-based test scripts. To succeed, developers, testers, and management all should consider the differences between the two options. |
|
 |
Bringing Empathy into Quality Engineering Testers have always been advocates for the end-user. But there are now more opportunities to be that advocate, including emotional intelligence-based testing and role-based testing, which form a critical part of empathetic testing. Building empathy into our software engineering process ends up benefiting everyone. |
|
 |
A Holistic View of Test Coverage No single person on the team knows much about test coverage at a high level. Developers might understand it for parts of the code base they worked on. Testers might understand it for the last handful of features they tested. But neither is able to talk about test coverage in a meaningful way. We need a holistic view. |
|
 |
Before Rolling Out Products, Walk a Mile in Their Shoes Beyond focus groups and surveys, different paths lead to uncovering ways to delight your customers. It is important to recognize the problems, challenges, wants, and needs of people. “Before you criticize someone, walk a mile in their shoes” is also good advice for rolling out products. |
