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
Add Support for Transactions (#121) autocommit, commit, and rollback, and transaction isolation
* Added support for autocommit, commit, and rollback, and transaction isolation level for Postgresql, MySQL, ODBC, and Sqlite. Added tests for autocommit.
* Add tests for set/get TransactionIsolation.
* Remove commented-out block of code.
* Remove debug writeln statements and split main test into several files.
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+8-2
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,17 @@ DDBC aims to support a range of compiler versions across from dmd 2.097 and abov
2
2
3
3
## Tests
4
4
5
-
To help with testing there is a *docker-compose.yml* file in the root of the project so that multiple databases can be run locally for testing.
5
+
To help with testing there is a *docker-compose.yml* file in the root of the project so that multiple databases can be run locally for testing.
6
6
7
7
When making changes to DDBC please ensure that unit tests (test not requiring a working database) remain in the project source and any integration tests (those running against a local database) are placed the test project (under `./test/ddbctest/`).
8
8
9
-
unit tests can br run in the usual way with `dub test` and integration tests are run with `dub run --config=test`.
9
+
Unit tests can be run in the usual way with `dub test` and integration tests are run with `dub run --config=test`.
10
+
11
+
To summarize, testing should be done as follows:
12
+
1.`dub test` - Runs unit tests.
13
+
2.`docker-compose up` - Creates various locally running databases in containers.
14
+
3.`dub run --config=test` - Runs integration tests aganist the local databases.
15
+
4.`docker-compose down` - Destroys the locally created databases.
0 commit comments