• Icon: Bug Report Bug Report
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 2.7.0
    • None
    • backend
    • None

      Given:

      • The current time is `Integer.MAX_VALUE` ms away from a summer/winter time shift
      • The variable startDate in `reportEvaluationForOneProcessBigActivityDuration` is defined as `OffsetDateTime startDate = OffsetDateTime.now()` (instead of the current quickfix `OffsetDateTime startDate = OffsetDateTime.now().minusDays(20)`

      When:

      • I run `ProcessInstanceDurationByNoneWithProcessPartReportEvaluationIT .reportEvaluationForOneProcessBigActivityDuration()`

      Then:

      • The test fails when trying to assert the activityDuration value

      Expected:

      • The test should pass

        This is the controller panel for Smart Panels app

            [OPT-2740] Test for large activity duration fails

            Helene Waechtler added a comment - - edited

            Looks like Sebastian's already fixed this on master

            Helene Waechtler added a comment - - edited Looks like Sebastian's already fixed this on master

            Johannes added a comment -

            The problem was that the date transformation that we do directly to adjust the date values in the engine data base were not taking the time zone shifts into account. Thanks sebastian.bathke for pointing me to that

            Johannes added a comment - The problem was that the date transformation that we do directly to adjust the date values in the engine data base were not taking the time zone shifts into account. Thanks sebastian.bathke for pointing me to that

              Unassigned Unassigned
              helene.waechtler Helene Waechtler
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: