The latest News and Information on Software Testing and related technologies.
Every organization knows what quality should look like for the products they work on. However, what’s the best way of knowing whether the obtained quality compares to the expected quality of the product(s)? Quality can be both quantitative and qualitative. Many questions could be asked to determine quality. For example, "How do you feel about the product you use? How easy is it to use? Does it behave as expected? Do customers keep coming back to use our product?
We expect software to work. Slow mobile apps and buggy website functionality are unacceptable, given that two-thirds of us do our banking from a mobile app and a quarter of the workforce logs in from their home office. Low-quality, poorly designed software can undermine operational efficiency, create security vulnerabilities, and contribute to customer attrition.
Why should you invest in software testing? And if you’ve already invested heavily in your testing program, why should you invest in modernizing your current practices and tools? If these are questions you’ve heard or asked yourself, take a cue from your peers, Gartner, and the World Quality Report. When you modernize your testing, you make it easier for IT staff and business stakeholders to collaborate in ways that lead to faster software delivery and better business outcomes.
One morning, you realize you have a great idea for an API. You discuss it with your team, then start building out the business case and technical requirements. Where do you go from there? You could write out the business requirements for the API and then code it. Or you could describe your API in a specification language, like OpenAPI, and use that definition to improve your team's understanding of the API and do some early testing. But are either of these the best solution?
