Using AchillesTestResource, the way it current does is by using a static instance of StatementsCache. This could lead to issues when testing insertion / update on same entity type using different keyspaces because the insertions statements are kept in the static cache which has no way to reset.
How to reproduce:
- TestClassA inserts and updates on EntityA using KeyspaceA
- TestClassB inserts and updates on EntityA using KeyspaceB
- TestClassB fails because the insertions will target for KeyspaceA (due to the stmt cache from TestClassA's run) while updates will target KeyspaceB
Using AchillesTestResource, the way it current does is by using a static instance of StatementsCache. This could lead to issues when testing insertion / update on same entity type using different keyspaces because the insertions statements are kept in the static cache which has no way to reset.
How to reproduce: