Missing `assertions.json` file after update into to version: >=3.10.0

[patrykks]

Missing `assertions.json` file after update into to version: >=3.10.0

[slandelle]

There's a wide range of official CI solutions plugins and integrations for Gatling Enterprise, including AzureDevOps pipelines.
There won't be any new free ones.

[slandelle]

This change is intended.
This file was never a publicly documented feature nor used internally in any Gatling official components.

[AnskCat]

Previously I was heavily using assertions.xml to reflect test/assertion statuses on Test report in AzureDevOps pipelines (as ADO can parse it as Junit results). I guess same happening in other CI solutions. Without having access to assertions.xml engineers are limited with results visualisation.
If there will be enough official plugins, issue can be eliminated.

[jonhattan]

This file was never a publicly documented feature nor used internally in any Gatling official components.

@slandelle indeed it was documented at https://gatling.io/docs/gatling/reference/current/core/assertions/#reports

It is a mess to lose features we rely on overnight.

[slandelle]

You're right, this was indeed documented.

Unfortunately, it was generating extra maintenance burden for us, while not serving any purpose in any official Gatling component, neither open-source nor Enterprise.

I've updated the documentation accordingly.

Regards