The latest News and Information on Software Testing and related technologies.
Quality software starts with code review, but quality doesn’t begin and end with code. Documents and artifacts need proper attention to make sure nothing slips through the cracks. To ensure quality software, it's essential to review the software artifacts left behind from the code review process. If code review is the unglamorous task of eating your vegetables, artifact review might as well be getting your 10,000 steps in. Both can be downright boring, but they're good for you.
When you're in the early stages of launching a startup, rapid iteration and determining product-market fit should be your top priorities. Unless you know exactly what you need to build, you should write code quickly only to discard it later. Working on test automation doesn't really fit in at this early stage. However, as you develop your product and gain customers, you will need to expand your testing infrastructure or risk losing customers and acceleration.
Why this combination you ask? Load testing is my passion, and I am partial to Kubernetes. I challenged myself to share a use case that many could relate to, focused on a business critical application. Websites came to mind and WordPress is the world’s most popular website management system. Of course, nginx is the most popular web server so let’s throw that into the mix. And Kubernetes? With more than 50% of corporations adopting Kubernetes in 2021, what better system to run in.
Fixing mobile software errors is a collaborative effort. Errors and crashes will be identified throughout the software development lifecycle (SDLC) by QA, testers, customer support, or users themselves. Unfortunately, there is often a time lag and loss of information as these errors get routed to the programmers who can further triage and resolve.
We recently talked to Angie Jones in a podcast episode dedicated to best practices in software testing. In this article, drawing on our previous discussion, we’ll share her thoughts about the main factors to consider to build a comprehensive test automation strategy.
