We worked hard on the result table: from the way the metrics are displayed and sorted to the CSV export, we reviewed this
report item so you can get the most revealing information from it.
This short post describes the modifications made to OctoPerf for its last update, and how they can let you save time while preparing your load tests.
You may need to have a large performance test done for yesterday. In such case the process to get a license with the appropriate number of virtual users must be as straightforward as possible.
Performance testing covers a wide range of different tests.
The benefits can vary whether you test a single URL or a complete user journey through the application.
It might seem obvious, but to add the most value to your load tests you should make them as realistic as reasonably possible.
Quick and unrealistic load tests often prove useless or even counterproductive.
It is often the best way to be overwhelmed with unreliable data.
A realistic load test will allow you to:
Stress all layers of your application. This way you can assess the performance of all your servers and detect bottlenecks.
Pinpoint real bottlenecks. For example a simple load test based on a single URL might point to limitations on your front servers when actually the real users won't experience it because the backend is the first to fail.
Avoid false positives. If you fail to launch realistic tests and encounter a lot of errors, you might stress the CPU of your front servers to handle these errors. The same goes for the network if you don't simulate the load from the right location.
Validating a credit card number is really complex. Thankfully Stripe comes with a JavaScript API to validate the various fields of a credit card.
But an AngularJs integration is not that straightforward.
Note:
The method explained here can be used to validate the other fields of the credit card.
During my past years as a tester, I often wondered how to get a higher customer satisfaction.
I could go great lengths describing the required skill set and give examples (actually I already did that over here).
When actually the truth is much simpler.
It's not rocket science, it's all about preparations and prerequisites.
Over the years, I have worked with a lot of testers.
We more or less shared the same views on how to do our jobs and even when all was not going according to the plan.