Database testing - transaction

https://www.guru99.com/data-testing.html

http://www.softwaretestinghelp.com/database-testing-process/

https://dl.acm.org/results.cfm?coll=guide&dl=GUIDE&query=Yuetang+Deng&short=1

http://cis.poly.edu/tr/tr-cis-2003-04.pdf    Testing database transaction consistency

Testing database transaction concurrency

http://www.taodocs.com/p-20651612.html

https://max.book118.com/html/2015/0908/24919655.shtm

https://max.book118.com/html/2013/0707/4334875.shtm

two main issues of transaction to deal with:
1. failures of various kinds, such as hardware failures and system crashes;
2. concurrent execution of multiple transactions;

https://stackoverflow.com/questions/3740280/acid-and-database-transactions#

Atomicity means that you can guarantee that all of a transaction happens, or none of it does; you can do complex operations as one single unit, all or nothing, and a crash, power failure, error, or anything else won't allow you to be in a state in which only some of the related changes have happened.

Consistency means that you guarantee that your data will be consistent; none of the constraints you have on related data will ever be violated.

Consistency is both "check constraints" like UNIQUE, FOREIGN KEY as well as valid state (according to the business logic / requirement of the application) at the the end of the transaction.

Isolation means that one transaction cannot read data from another transaction that is not yet completed. If two transactions are executing concurrently, each one will see the world as if they were executing sequentially, and if one needs to read data that is written by another, it will have to wait until the other is finished.

Durability means that once a transaction is complete, it is guaranteed that all of the changes have been recorded to a durable medium (such as a hard disk), and the fact that the transaction has been completed is likewise recorded.

Atomicity: All changes to data are performed as if they are a single operation. That is, all the changes are performed, or none of them are. For example, in an application that transfers funds from one account to another, the atomicity property ensures that, if a debit is made successfully from one account, the corresponding credit is made to the other account. 

Consistency: Data is in a consistent state when a transaction starts and when it ends. For example, in an application that transfers funds from one account to another, the consistency property ensures that the total value of funds in both the accounts is the same at the start and end of each transaction. 

Isolation: The intermediate state of a transaction is invisible to other transactions. As a result, transactions that run concurrently appear to be serialized. For example, in an application that transfers funds from one account to another, the isolation property ensures that another transaction sees the transferred funds in one account or the other, but not in both, nor in neither. 

Durability: After a transaction successfully completes, changes to data persist and are not undone, even in the event of a system failure. For example, in an application that transfers funds from one account to another, the durability property ensures that the changes made to each account will not be reversed.

blog post: "ACID Does Not Make Sense".

http://blog.franslundberg.com/2013/12/acid-does-not-make-sense.html

[Gray] The Transaction Concept, Jim Gray, 1981. 
http://research.microsoft.com/en-us/um/people/gray/papers/theTransactionConcept.pdf

[Haerder] Principles of Transaction-Oriented Database Recovery, Haerder and Reuter, 1983.
http://www.stanford.edu/class/cs340v/papers/recovery.pdf