You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently limit our transaction and connection BDD scenarios to open, isRead/Write, close and commit, sequentially and concurrently. However, we don't actually perform any operations within each open in transaction - such as attempting and expecting and exception on writing to a read transaction.
We need to test in parallel operations in various transactions. We should keep in mind this amounts to testing the isolation and serialisability of transactions in the DB, which should be designed properly
The text was updated successfully, but these errors were encountered:
Existing tests that should go in ACID tests: define.feature : uncommitted transaction writes are not persisted transaction.feature: write in a read transaction throws
We currently limit our transaction and connection BDD scenarios to
open
,isRead/Write
,close
andcommit
, sequentially and concurrently. However, we don't actually perform any operations within each open in transaction - such as attempting and expecting and exception on writing to a read transaction.We need to test in parallel operations in various transactions. We should keep in mind this amounts to testing the isolation and serialisability of transactions in the DB, which should be designed properly
The text was updated successfully, but these errors were encountered: