Q
Manage Learn to apply best practices and optimize your operations.

Continuous performance testing cycles ease testing

As we move to continuous delivery, regular tasks like performance testing can lose focus. What's the best way to take on continuous performance tests?

When dealing with continuous performance testing, it's important to remember that routinely executing some tests...

is always better than doing none, and doing any is more than most development shops accomplish. All applications need (at minimum) performance testing on initial screens that involve user interaction. A continuous development software team can squeeze in valuable performance testing in several ways and on an ongoing basis.

First, test performance of an application on its own without the complexity of adding server load variations. You can add load testing later without having to update existing test cases because varying load is done on the server rather than the test case. Start building a small set of performance tests that are executed on the application itself and then add to it as performance related issues are reported or fixed.

If your organization has a number of performance tests but cannot execute them all continuously, consider developing a rotating test suite. To use a rotating test suite, first determine how many tests you can squeeze into the test cycle realistically without affecting the release schedule. Next, prioritize the tests based on risk, and then separate them into suites. When you separate tests into suites, make sure to include a balance of priority levels and at least one test for each main functional area. In other words, cover the bases but with the minimum number of players. During each test cycle, execute a different suite. The application still receives coverage for performance, hitting all areas, but with fewer tests.

The previous two suggestions assume the performance tests are automated. You can squeeze manual software performance tests into the testing cycle in the same way. The main difference with manual performance tests is that you need to rely on the knowledge and skills of the testers. Testers know how fast they expect an application to respond, whether it is a Web application or a mobile application. Use the real-world consumer skills of your testers combined with their application knowledge to create a small test suite of continuous performance tests that fit into the existing test cycle. Again, if necessary, spread them out over several test cycles by creating rotating suites of manual test cases.

Next Steps

Learn more about continuous development

Find tips on continuous testing

Check out tools for performance testing on AWS

And more traditional performance testing tools

Think about application performance metrics

This was last published in April 2015

Dig Deeper on Software Performance Management

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Join the conversation

2 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

Performance testing is something that we struggle with on my team. We don't typically develop web or mobile applications. They are mostly back-end data processing applications. We have one custom written tool that reports performance statistics in test; that's about it as far as automated performance testing goes. Building in time for manual performance testing is something that we should probably have more awareness of.
Cancel
I think the key here is NOT continuous performance testing, that taken to an extreme will cause a lot of weirdness during work hours.  All performance testing should be scheduled so as to be effective at knowing what is actually being tested at the time, and not the noise from normal operations.

Other than that, testing for performance as part of regular testing makes a lot of sense.
Cancel

-ADS BY GOOGLE

SearchMicroservices

TheServerSide

SearchCloudApplications

SearchAWS

SearchBusinessAnalytics

SearchFinancialApplications

SearchHealthIT

Close