By now, you’ve undoubtedly come across the phrase, “test early and often.” However, for many organizations, it can be difficult to convince key stakeholders that testing earlier and at lower levels in the system or application is beneficial.
In this TechWell article from author Michael Sowers, he sheds light on approaches to testing earlier that have been successful in organizations he has worked with and for. From assuming accountability for driving the change to identifying, educating and mentoring key stakeholders and educate, Sowers’ advice is sure to guide your company as it strives to deliver better products to market faster. View his full write-up here.
Today, user experience is crucial to an application’s success, and that goes well beyond what color your button is or how prominently a call-to-action is placed. Users leave your site if pages don’t load fast enough or if the site simply feels sluggish when compared with your competitors’ sites.
The question is: is there a process for validating that your app is performing up to your customers’ expectations and have that process treat performance testing with the same amount of rigor as functional testing? Yes. It’s called Continuous Performance Validation. To learn more about this concept and the ways in which your organization can benefit from it, read on here.
Back in September, we wrote about a number of misconceptions people have about load testing in an agile environment. It just goes to show that there are various fallacies and misconceptions that surround load and performance testing, not only in an agile environment, but in any software development project.
Simply put, when you do the same thing many times, you can start to make false assumptions about your work process—and testing is no exception. In this article, Sofía Palamarchuk discusses some common fallacies about performance tests specifically, and how they can end up costing testers and developers significantly more than they should. Read more here.
From time to time, we are all forced to swallow some hard truths and constructive criticism in our pursuit of growth and improvement. So then, are there really things that shouldn’t be said to certain individuals in certain careers? Some people seem to think so. On the Test Huddle Forum, Daragh Murphy quoted a few different blog posts he’d come across listing some of the things you should never say to a software tester:
“Can you hurry up and finish testing soon? We’re under a very tight deadline.”
“You must be bored out of your mind.”
“I didn’t have time to read your bug report. Give me the 5-second version.”
What are your thoughts on the concept? Check out the full posting for other examples and to contribute your response.