Uploaded image for project: 'Runtime'
  1. Runtime
  2. RUNTIME-2062

Tests must always drop all tables before running the application

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • 4.0M10
    • 4.0M8
    • None
    • None

        [RUNTIME-2062] Tests must always drop all tables before running the application

        But it has to not be.

        For every test, even those not for testing a JDBC feature, we have to ensure all tables needed are dropped. Then, when starting applciation, the SqlTablesInit will create them automatically. this prevents from having existing tables, but with incorrect columns (for instance, tables created from another branch test...)
        So, for every test, setUp will do a #_dropTables(), then #_startApplication(), and then #_populateTables() if needed (only for group, user and right tests normally)

        Simon Prieul (Inactive) added a comment - But it has to not be. For every test, even those not for testing a JDBC feature, we have to ensure all tables needed are dropped. Then, when starting applciation, the SqlTablesInit will create them automatically. this prevents from having existing tables, but with incorrect columns (for instance, tables created from another branch test...) So, for every test, setUp will do a #_dropTables(), then #_startApplication(), and then #_populateTables() if needed (only for group, user and right tests normally)

        Currently, the feature creating the READER profile was excluded from all tests

        Simon Prieul (Inactive) added a comment - Currently, the feature creating the READER profile was excluded from all tests

          sprieul Simon Prieul (Inactive)
          sprieul Simon Prieul (Inactive)
          Votes:
          0 Vote for this issue
          Watchers:
          1 Start watching this issue

            Created:
            Updated:
            Resolved: