The Power of Continuous Performance Testing – Neotys Testing Roundup

1. The Power of Continuous Performance Testing

One of the key tenets of continuous integration is to reduce the time between a change being made and the discovery of defects within that change. When load and performance testing are pushed off until the end of a development cycle, however, there is often little to no time for developers to address identified defects. This can result in the push back of release dates and delay getting features out the door that customers need.

If testing teams implement continuous performance testing, it will give development teams a fighting chance against hard-to-diagnose performance and load-handling bugs, as well as the ability to quickly identify major functional bugs. View this article to learn more about why performance tests are powerful candidates for continuous testing.

2. How to Test an Application without Requirements

Now, you might be thinking it’s impossible to have an application without requirements, and you’d be correct. All software has requirements and is designed as a solution to a problem. Requirement-less software isn’t a possibility, but sometimes teams face an equally daunting reality: software projects that either lack documented requirements or have documentation that is insufficient, inaccurate or terribly outdated.

Rapid development cycles and the shift towards minimum or no documentation have left organizations without a well-documented functional/system requirement document with elaborate use cases and mock-up screens, for which, there really is no substitute. This article from Software Testing Help outlines some best practices for testers who find themselves in these kinds of situations. Read it here.

3. The Lean Startup Methodology and Its Value for Testers

It’s true, testers are rarely part of entrepreneurial startup teams. However, when it comes to the lean startup process, introduced by Eric Ries in his book, The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses, there are few lessons testers can learn.

Article author Lee Copeland lists and discusses the five major cornerstones of this process: Build-Measure-Learn, Minimum Viable Product, Validated Learning, Customer Development, and the One Metric That Matters. The basic idea behind lean startup: companies should focus their time and resources more effectively. Lee believes this concept can benefit any team, especially testers—so check out his full write-up here.

4. Discussion: Taxonomy of Software Testing Terms

If you frequent TEST Huddle, now is the time to provide some feedback. The TEST Huddle team is looking to create a taxonomy of terms which it will use to make resources on the website easily discoverable by relevant subject matter.

“The goal is to create a bank of content that can be efficiently searched by testers trying to solve a particular problem – whether directly related to testing or indirectly e.g. advice from others on managing people; communicating to stakeholders etc.”

Have any terms in mind? Contribute your ideas here!

Leave a Reply

Your email address will not be published. Required fields are marked *