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)
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)