i would like to get the “real” request under under request_ in a Gatling report.
each time i am going back to the scala simulation to find out this information and i am wondering if there’s no better way?
i would like to get the “real” request under under request_ in a Gatling report.
each time i am going back to the scala simulation to find out this information and i am wondering if there’s no better way?
Renaming request_ into something more meaningful?
Hello Stéphane,
thanks for replying. the thing is that i am using a recorded scenario from har file.
the generated report is great but when i need to check a specific request i want to know the details behind (eg uri and parameters).
so each time i am going back to the scenario (scala source) and searching the corresponding request to get this information.
i guess, there is a better way to do it and to have this information directly accessible from the report?