Over a million developers have joined DZone.

The How and Why of Earlier Performance Testing

DZone's Guide to

The How and Why of Earlier Performance Testing

· Performance Zone
Free Resource

Transform incident management with machine learning and analytics to help you maintain optimal performance and availability while keeping pace with the growing demands of digital business with this eBook, brought to you in partnership with BMC.

In traditional development, there is a standard protocol for performance testing that centers around load testing. According to a blog post at Internet Performance Expert,  the traditional way of thinking – even the concept of tradition in a constantly-evolving field – needs to be set aside.

Instead of just thinking about load testing, the performance testing process should be constant.

We have to be providing feedback earlier. Load testing though is not ideal for this, there are a lot of drawbacks – scripts have to be maintained, environments available, datasets managed, load models understood. These are surmountable but quicker feedback can be provided by simpler processes that can be added to a standard CI solution or executed manually but regularly.

There also needs to be better integration among the performance testing team and developers to better facilitate communication.

Check out the original article here.

Evolve your approach to Application Performance Monitoring by adopting five best practices that are outlined and explored in this e-book, brought to you in partnership with BMC.


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}