1 2 3Organization of test case files: 4 5 lsmtest1.c: Data tests. Tests that perform many inserts and deletes on a 6 database file, then verify that the contents of the database can 7 be queried. 8 9 lsmtest2.c: Crash tests. Tests that attempt to verify that the database 10 recovers correctly following an application or system crash. 11 12 lsmtest3.c: Rollback tests. Tests that focus on the explicit rollback of 13 transactions and sub-transactions. 14 15 lsmtest4.c: Multi-client tests. 16 17 lsmtest5.c: Multi-client tests with a different thread for each client. 18 19 lsmtest6.c: OOM injection tests. 20 21 lsmtest7.c: API tests. 22 23 lsmtest8.c: Writer crash tests. Tests in this file attempt to verify that 24 the system recovers and other clients proceed unaffected if 25 a process fails in the middle of a write transaction. 26 27 The difference from lsmtest2.c is that this file tests 28 live-recovery (recovery from a failure that occurs while other 29 clients are still running) whereas lsmtest2.c tests recovery 30 from a system or power failure. 31 32 lsmtest9.c: More data tests. These focus on testing that calling 33 lsm_work(nMerge=1) to compact the database does not corrupt it. 34 In other words, that databases containing block-redirects 35 can be read and written. 36 37 38 39 40 41