L3 - Default Context:
Some decision date filter tests have been observed to be unstable due to being dependent on the time they run. E.g. When the relative minute filter is used and the minute changes between test data setup and actual evaluation, see e.g. this failure:
https://ci.optimize.camunda.cloud/view/all/job/elasticsearch_compatibility/612/testReport/junit/org.camunda.optimize.service.es.filter.decision/DecisionEvaluationDateFilterIT/Elasticsearch_Integration_Tests___Elasticsearch_AWS_Integration___resultFilterByRollingEvaluationDateCurrentInterval_DateFilterUnit__1_/
AT:
- we should make use of LocalDateUtil in all date filtering tests to eliminate the depenency on the actual time and eliminate race conditions, like e.g. done in RollingDateFilterIT#testStartDateCurrentIntervalRollingLogic