Migros - Referenzen

The common goal is to use load tests to work out where adjustments need to be made: i.e. load needs to be distributed differently.

Load tests provide a good indication of the user experience for the regular placement of advertising campaigns. To this end, we are in regular dialogue with our partners and carry out a monthly load test on average. The tests for server load are particularly important for campaigns in order to test the most realistic expectations of user behavior.

Load tests offer stakeholders the opportunity to follow the test live with our experts. This distinguishes this variant from many other test methods. The discussion and evaluation of the results in a joint exchange efficiently promote the subsequent development measures.

The case study: the Migros online counter. A seasonal campaign by Migros of products for the barbecue season.

1) Coding & Timing: The load tests for the Migros online counter were written approx. 2 weeks before the campaign went live. This corresponds to the average time of our load tests, which are usually carried out 2 to 3 weeks before a go-live.

Based on the internal Migros campaign analyses, a guideline value of 10,000 to 20,000 users per hour was defined for peak times. We write the tests based on this value. This involves converting how many users are expected per second. This value is initially used for testing in the ramp-up phase. A target value is set for the load, which is to be maintained over the duration.

4) Analysis & troubleshooting: If fluctuations occur outside the previously defined limits, these are discussed and analyzed. Frequent errors are due, for example, to the logic of the system or the placement of elements. During the analysis, we develop an action plan to improve the page performance. The dev team makes the adjustments. We remain in close dialogue during this period. Transferred configurations in the code are retested by us. This allows our partners to ensure that the corrected errors rule out further undesirable consequences.

The aim of the load test was to ensure that the expected traffic would be supported by the system when the online counter advertising campaign went live. The desired result: an unrestricted shopping experience for customers, regardless of the server load.

A load limit of 400% of the nominal value was set for the Migros online counter. This had to be tested to see how the system behaved.

A key component of the load test cases are scenarios that realistically reflect the behavior of the users. The most frequent user actions are incorporated, weighted and assigned grace periods. This approach maximizes the system's infrastructure.

Load tests are among the automated test procedures. However, this example makes it clear that there is always a demand for the highest possible degree of realism.

Four scenarios were defined for the Migros online counter. Each user in the load test is assigned to a scenario and weighted. The scenarios therefore flow directly into the load test and are tracked in their evaluation.

In the case of the Migros online counter, the result of the page performance was very responsive and only minor configuration problems occurred. Among other things, several activities of individual users were tested. Latency deviations occurred at these configuration points, which could be rectified based on the test results. After adjusting the load test results, the online counter campaign was launched as planned.

Migros plans load tests before launching new retail advertising campaigns

About Migros

QA goals

Results

Challenge

Goals and
test frequency

"The professional support from Appmatics in testing, ensures the optimum performance and success of our digital campaigns and promotions."

Test procedure

Result

Contact our team