Expand step param and result integration tests to ensure all classes serialise correctly

[luhmirin-s]

Will be released in: 2025.3.0

Root cause analysis (for bugfixes only)

First known affected version: 2025.3.0

• When the step orchestrator cache restores step data, sometimes not all of the classes can be restored correctly.

Notable changes

• Added all of the step param and result classes to the orchestrator cache integration tests to make sure that all are written and read correctly.
• Fixes for a couple of classes that were not deserialising correctly.

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[BurningAXE]

Why is this needed? And will we need to do it for all subclasses? :(

[luhmirin-s]

Automatic data class "equals" implementation does not work with arrays (there is even a warning that we usually ignore). Without this, comparing data in tests becomes a major PITA.

It is only required when there are arrays in data classes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud