Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-12466

Failing tests due to suppressing sql errors

XMLWordPrintable

      Problems

      1. In SuppressSqlExceptionsTest shouldThrowExceptionOnInsert_ColumnSizeExceeded & shouldThrowExceptionOnUpdate fails on MariaDB 10.0
      2. SuppressSqlExceptionsTest#shouldThrowExceptionOnInsert_ColumnSizeExceeded fails on HistoryLevel == NONE
      3. ManagementServiceTest fails on DB2

      Root Causes

      1. Maria DB 10.0 does not throw an exception when the column size is exceeded; instead, the string is truncated at 255 characters
      2. The test is designed to be executed with a minimum history level of HISTORY_LEVEL_ACTIVITY
      3. The alias RES is missing when selecting columns

      Solutions

      1. Add test annotation @RequiredDatabase(excludes = DbSqlSessionFactory.MARIADB)
      2. Add test annotation @RequiredHistoryLevel(ProcessEngineConfiguration.HISTORY_ACTIVITY)
      3. Add the RES alias when selecting columns

        This is the controller panel for Smart Panels app

            [CAM-12466] Failing tests due to suppressing sql errors

            Tassilo Weidner created issue -
            Tassilo Weidner made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Tassilo Weidner made changes -
            Description Original: # {{SuppressSqlExceptionsTest#shouldThrowExceptionOnInsert_ColumnSizeExceeded}} fails on MariaDB 10.0
            # {{ManagementServiceTest}} fails on DB2             		New: # {{SuppressSqlExceptionsTest#shouldThrowExceptionOnInsert_ColumnSizeExceeded}} fails on MariaDB 10.0
            # {{SuppressSqlExceptionsTest#shouldThrowExceptionOnInsert_ColumnSizeExceeded}} fails on {{HistoryLevel == NONE}}
            # {{ManagementServiceTest}} fails on DB2
            Tassilo Weidner made changes -
            Mentioned Roles
            Tassilo Weidner made changes -
            Mentioned Groups
            Tassilo Weidner made changes -
            Description Original: # {{SuppressSqlExceptionsTest#shouldThrowExceptionOnInsert_ColumnSizeExceeded}} fails on MariaDB 10.0
            # {{SuppressSqlExceptionsTest#shouldThrowExceptionOnInsert_ColumnSizeExceeded}} fails on {{HistoryLevel == NONE}}
            # {{ManagementServiceTest}} fails on DB2             		New: h3. Problems

            # {{SuppressSqlExceptionsTest#shouldThrowExceptionOnInsert_ColumnSizeExceeded}} fails on MariaDB 10.0
            # {{SuppressSqlExceptionsTest#shouldThrowExceptionOnInsert_ColumnSizeExceeded}} fails on {{HistoryLevel == NONE}}
            # {{ManagementServiceTest}} fails on DB2

            h3. Root Causes

            # Maria DB 10.0 does not throw an exception when the column size is exceeded; instead, the string is truncated at 255 characters
            # The test is designed to be executed with a minimum history level of {{HISTORY_LEVEL_ACTIVITY}}; either, change the test case to work with runtime data or add {{}}
            # The alias {{RES}} is missing when selecting columns

            h3. Solutions

            # Add test annotation {{@RequiredDatabase(excludes = DbSqlSessionFactory.MARIADB)}}
            # Either change the test to work on runtime data or add test annotation {{@RequiredHistoryLevel(ProcessEngineConfiguration.HISTORY_ACTIVITY)}}
            # Add the {{RES}} alias when selecting columns
            Tassilo Weidner made changes -
            Mentioned Roles
            Tassilo Weidner made changes -
            Mentioned Groups
            Tassilo Weidner made changes -
            Description Original: h3. Problems

            # {{SuppressSqlExceptionsTest#shouldThrowExceptionOnInsert_ColumnSizeExceeded}} fails on MariaDB 10.0
            # {{SuppressSqlExceptionsTest#shouldThrowExceptionOnInsert_ColumnSizeExceeded}} fails on {{HistoryLevel == NONE}}
            # {{ManagementServiceTest}} fails on DB2

            h3. Root Causes

            # Maria DB 10.0 does not throw an exception when the column size is exceeded; instead, the string is truncated at 255 characters
            # The test is designed to be executed with a minimum history level of {{HISTORY_LEVEL_ACTIVITY}}; either, change the test case to work with runtime data or add {{}}
            # The alias {{RES}} is missing when selecting columns

            h3. Solutions

            # Add test annotation {{@RequiredDatabase(excludes = DbSqlSessionFactory.MARIADB)}}
            # Either change the test to work on runtime data or add test annotation {{@RequiredHistoryLevel(ProcessEngineConfiguration.HISTORY_ACTIVITY)}}
            # Add the {{RES}} alias when selecting columns             		New: h3. Problems

            # {{SuppressSqlExceptionsTest#shouldThrowExceptionOnInsert_ColumnSizeExceeded}} fails on MariaDB 10.0
            # {{SuppressSqlExceptionsTest#shouldThrowExceptionOnInsert_ColumnSizeExceeded}} fails on {{HistoryLevel == NONE}}
            # {{ManagementServiceTest}} fails on DB2

            h3. Root Causes

            # Maria DB 10.0 does not throw an exception when the column size is exceeded; instead, the string is truncated at 255 characters
            # The test is designed to be executed with a minimum history level of {{HISTORY_LEVEL_ACTIVITY}}
            # The alias {{RES}} is missing when selecting columns

            h3. Solutions

            # Add test annotation {{@RequiredDatabase(excludes = DbSqlSessionFactory.MARIADB)}}
            # Either change the test to work on runtime data or add test annotation {{@RequiredHistoryLevel(ProcessEngineConfiguration.HISTORY_ACTIVITY)}}
            # Add the {{RES}} alias when selecting columns
            Tassilo Weidner made changes -
            Mentioned Roles
            Tassilo Weidner made changes -
            Mentioned Groups

              thorben.lindhauer Thorben Lindhauer
              tassilo.weidner Tassilo Weidner
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: