Maintaining Gatling tests

Gatling (Open-Source)
1

Hi,

We have been using Gatling quite successfully one of our projects and would like to continue using the integrating them to our our build/integration pipeline.

The issue we have is that our application is webform based and when changes are made to the system, it is not immediately obvious unlike a fixed api service. The Gatling tests may pass even though changes have been made to the UI.

Is there a approach we can take to maintain changes without to having to manually recreate tests and then compare the output to the Gatling test?

iress.com

Shazad Dad​

Senior Tester

Tel: +441926621417

shazad.dad@iress.com

www.iress.com

1 Kingmaker Court, Warwick Technology Park, Gallows Hill,
Warwick, Warwickshire, CV34 6DY

The contents of this email originated from Iress. For this purpose Iress includes Iress Limited and/or any of its subsidiaries, holding companies and trading entities.
​If you have received this email in error please notify the sender immediately and delete this email.

nosig

2

The Gatling tests may pass even though changes have been made to the UI.

IMHO, there’s an issue with you application here.
If some changes have been made in the application’s UI, such as adding a mandatory field to a form, and the test still passes with this field missing, there’s a bug either in the way your application handles such errors (eg the dreaded 200 status code with an error message) or in the way your Gatling tests detect request failures.