Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-6602

Fix flakiness in process overview ITs

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • backend, ci
    • None
    • Not defined

      We have seen some flakiness in the following test in our Engine compatibility tests:

      ProcessOverviewRetrievalIT.getProcessOverview_processesGetOrderedByOwnerAndDefinitionNameWhenOwnerNameIsMissingFromSomeDefinitions

      We should investigate the cause of this flakiness and fix the test so we no longer see failures in our nightly pipelines

      Example failure:

      09:16:53 Expected size: 4 but was: 5 in:09:16:53 [ProcessOverviewResponseDto(processDefinitionName=secondDefWithOwner, processDefinitionKey=secondDefWithOwner, owner=ProcessOwnerResponseDto(id=spiderman, name=Afraid of Spiders), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/secondDefWithOwner/dashboard/secondDefWithOwner/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=firstDefWithOwner, processDefinitionKey=firstDefWithOwner, owner=ProcessOwnerResponseDto(id=demo, name=firstName lastName), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/firstDefWithOwner/dashboard/firstDefWithOwner/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=firstDefKey, processDefinitionKey=firstDefKey, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/firstDefKey/dashboard/firstDefKey/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=fourthDefWithOwner, processDefinitionKey=fourthDefWithOwner, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/fourthDefWithOwner/dashboard/fourthDefWithOwner/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=thirdDefWithOwner, processDefinitionKey=thirdDefWithOwner, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/thirdDefWithOwner/dashboard/thirdDefWithOwner/, hasDefaultDashboard=false)]

        This is the controller panel for Smart Panels app

            [OPT-6602] Fix flakiness in process overview ITs

            Joshua Windels created issue -
            Joshua Windels made changes -
            Description Original: We have seen some flakiness in the following test in our Engine compatibility tests:

            {{ProcessOverviewRetrievalIT.getProcessOverview_processesGetOrderedByOwnerAndDefinitionNameWhenOwnerNameIsMissingFromSomeDefinitions}}

            We should investigate the cause of this flakiness and fix the test so we no longer see failures in our nightly pipelines             		New: We have seen some flakiness in the following test in our Engine compatibility tests:

            {{ProcessOverviewRetrievalIT.getProcessOverview_processesGetOrderedByOwnerAndDefinitionNameWhenOwnerNameIsMissingFromSomeDefinitions}}

            We should investigate the cause of this flakiness and fix the test so we no longer see failures in our nightly pipelines

            Example failure:
            *09:16:53* Expected size: 4 but was: 5 in:*09:16:53* [ProcessOverviewResponseDto(processDefinitionName=secondDefWithOwner, processDefinitionKey=secondDefWithOwner, owner=ProcessOwnerResponseDto(id=spiderman, name=Afraid of Spiders), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/secondDefWithOwner/dashboard/secondDefWithOwner/, hasDefaultDashboard=false),*09:16:53* ProcessOverviewResponseDto(processDefinitionName=firstDefWithOwner, processDefinitionKey=firstDefWithOwner, owner=ProcessOwnerResponseDto(id=demo, name=firstName lastName), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/firstDefWithOwner/dashboard/firstDefWithOwner/, hasDefaultDashboard=false),*09:16:53* ProcessOverviewResponseDto(processDefinitionName=firstDefKey, processDefinitionKey=firstDefKey, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/firstDefKey/dashboard/firstDefKey/, hasDefaultDashboard=false),*09:16:53* ProcessOverviewResponseDto(processDefinitionName=fourthDefWithOwner, processDefinitionKey=fourthDefWithOwner, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/fourthDefWithOwner/dashboard/fourthDefWithOwner/, hasDefaultDashboard=false),*09:16:53* ProcessOverviewResponseDto(processDefinitionName=thirdDefWithOwner, processDefinitionKey=thirdDefWithOwner, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/thirdDefWithOwner/dashboard/thirdDefWithOwner/, hasDefaultDashboard=false)]
            Joshua Windels made changes -
            Description Original: We have seen some flakiness in the following test in our Engine compatibility tests:

            {{ProcessOverviewRetrievalIT.getProcessOverview_processesGetOrderedByOwnerAndDefinitionNameWhenOwnerNameIsMissingFromSomeDefinitions}}

            We should investigate the cause of this flakiness and fix the test so we no longer see failures in our nightly pipelines

            Example failure:
            *09:16:53* Expected size: 4 but was: 5 in:*09:16:53* [ProcessOverviewResponseDto(processDefinitionName=secondDefWithOwner, processDefinitionKey=secondDefWithOwner, owner=ProcessOwnerResponseDto(id=spiderman, name=Afraid of Spiders), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/secondDefWithOwner/dashboard/secondDefWithOwner/, hasDefaultDashboard=false),*09:16:53* ProcessOverviewResponseDto(processDefinitionName=firstDefWithOwner, processDefinitionKey=firstDefWithOwner, owner=ProcessOwnerResponseDto(id=demo, name=firstName lastName), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/firstDefWithOwner/dashboard/firstDefWithOwner/, hasDefaultDashboard=false),*09:16:53* ProcessOverviewResponseDto(processDefinitionName=firstDefKey, processDefinitionKey=firstDefKey, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/firstDefKey/dashboard/firstDefKey/, hasDefaultDashboard=false),*09:16:53* ProcessOverviewResponseDto(processDefinitionName=fourthDefWithOwner, processDefinitionKey=fourthDefWithOwner, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/fourthDefWithOwner/dashboard/fourthDefWithOwner/, hasDefaultDashboard=false),*09:16:53* ProcessOverviewResponseDto(processDefinitionName=thirdDefWithOwner, processDefinitionKey=thirdDefWithOwner, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/thirdDefWithOwner/dashboard/thirdDefWithOwner/, hasDefaultDashboard=false)]             		New: We have seen some flakiness in the following test in our Engine compatibility tests:

            {{ProcessOverviewRetrievalIT.getProcessOverview_processesGetOrderedByOwnerAndDefinitionNameWhenOwnerNameIsMissingFromSomeDefinitions}}

            We should investigate the cause of this flakiness and fix the test so we no longer see failures in our nightly pipelines

            Example failure:{*}{*}
            {code:java}
            09:16:53 Expected size: 4 but was: 5 in:09:16:53 [ProcessOverviewResponseDto(processDefinitionName=secondDefWithOwner, processDefinitionKey=secondDefWithOwner, owner=ProcessOwnerResponseDto(id=spiderman, name=Afraid of Spiders), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/secondDefWithOwner/dashboard/secondDefWithOwner/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=firstDefWithOwner, processDefinitionKey=firstDefWithOwner, owner=ProcessOwnerResponseDto(id=demo, name=firstName lastName), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/firstDefWithOwner/dashboard/firstDefWithOwner/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=firstDefKey, processDefinitionKey=firstDefKey, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/firstDefKey/dashboard/firstDefKey/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=fourthDefWithOwner, processDefinitionKey=fourthDefWithOwner, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/fourthDefWithOwner/dashboard/fourthDefWithOwner/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=thirdDefWithOwner, processDefinitionKey=thirdDefWithOwner, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/thirdDefWithOwner/dashboard/thirdDefWithOwner/, hasDefaultDashboard=false)]{code}
            Joshua Windels made changes -
            Description Original: We have seen some flakiness in the following test in our Engine compatibility tests:

            {{ProcessOverviewRetrievalIT.getProcessOverview_processesGetOrderedByOwnerAndDefinitionNameWhenOwnerNameIsMissingFromSomeDefinitions}}

            We should investigate the cause of this flakiness and fix the test so we no longer see failures in our nightly pipelines

            Example failure:{*}{*}
            {code:java}
            09:16:53 Expected size: 4 but was: 5 in:09:16:53 [ProcessOverviewResponseDto(processDefinitionName=secondDefWithOwner, processDefinitionKey=secondDefWithOwner, owner=ProcessOwnerResponseDto(id=spiderman, name=Afraid of Spiders), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/secondDefWithOwner/dashboard/secondDefWithOwner/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=firstDefWithOwner, processDefinitionKey=firstDefWithOwner, owner=ProcessOwnerResponseDto(id=demo, name=firstName lastName), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/firstDefWithOwner/dashboard/firstDefWithOwner/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=firstDefKey, processDefinitionKey=firstDefKey, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/firstDefKey/dashboard/firstDefKey/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=fourthDefWithOwner, processDefinitionKey=fourthDefWithOwner, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/fourthDefWithOwner/dashboard/fourthDefWithOwner/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=thirdDefWithOwner, processDefinitionKey=thirdDefWithOwner, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/thirdDefWithOwner/dashboard/thirdDefWithOwner/, hasDefaultDashboard=false)]{code}             		New: We have seen some flakiness in the following test in our Engine compatibility tests:

            {{ProcessOverviewRetrievalIT.getProcessOverview_processesGetOrderedByOwnerAndDefinitionNameWhenOwnerNameIsMissingFromSomeDefinitions}}

            We should investigate the cause of this flakiness and fix the test so we no longer see failures in our nightly pipelines

            Example failure:
            {code:java}
            09:16:53 Expected size: 4 but was: 5 in:09:16:53 [ProcessOverviewResponseDto(processDefinitionName=secondDefWithOwner, processDefinitionKey=secondDefWithOwner, owner=ProcessOwnerResponseDto(id=spiderman, name=Afraid of Spiders), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/secondDefWithOwner/dashboard/secondDefWithOwner/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=firstDefWithOwner, processDefinitionKey=firstDefWithOwner, owner=ProcessOwnerResponseDto(id=demo, name=firstName lastName), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/firstDefWithOwner/dashboard/firstDefWithOwner/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=firstDefKey, processDefinitionKey=firstDefKey, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/firstDefKey/dashboard/firstDefKey/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=fourthDefWithOwner, processDefinitionKey=fourthDefWithOwner, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/fourthDefWithOwner/dashboard/fourthDefWithOwner/, hasDefaultDashboard=false),09:16:53 ProcessOverviewResponseDto(processDefinitionName=thirdDefWithOwner, processDefinitionKey=thirdDefWithOwner, owner=ProcessOwnerResponseDto(id=null, name=null), digest=ProcessDigestResponseDto(enabled=false), kpis=[], linkToDashboard=/collection/thirdDefWithOwner/dashboard/thirdDefWithOwner/, hasDefaultDashboard=false)]{code}
            Joshua Windels made changes -
            Issue Type Original: Bug Report [ 1 ] New: Task [ 3 ]
            Joshua Windels made changes -
            Status Original: Triage [ 10612 ] New: Open [ 1 ]

            Omran Abazeed added a comment -

            This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10245. Please use this link for any future references and continue any discussion there.

            Omran Abazeed added a comment - This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10245 . Please use this link for any future references and continue any discussion there.

              Unassigned Unassigned
              joshua.windels Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: