Skip to content

Commit

Permalink
Merge README.tests into tests/README.TXT
Browse files Browse the repository at this point in the history
  • Loading branch information
amantia committed Apr 10, 2017
1 parent c03ae64 commit 0bde669
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 9 deletions.
6 changes: 3 additions & 3 deletions tests/README.TXT
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
In order to run the unit tests some steps must be followed:

1) a PostgreSQL server must be running and needs to be accessible via TCP under the "sqlate-postgres" name.
1) a PostgreSQL server must be running and needs to be accessible via TCP under the "sqlate-postgres" name on the default 5432 port.
If it is not possible to use this domain name, the SQLATE_DATABASE_HOST environment variable should contain the name or address of the PostgreSQL server instance.

2) the server must have two group roles: "sqladmins" and "sqlusers". The admin group should have database
create rights.
create rights. It is recommended to use an isolated, non production PostgreSQL install for the tests.

3) the server must have a user called "sqlate.user" with password "sql123456". The user must be in the
"sqladmins" and "postgres" groups and should inherit group rights. Should you want to use a different user
or password, you can override the default values with SQLATE_DATABASE_USER and SQLATE_DATABASE_PASSWORD
environment variables.
The user should be able to log in with "password" method.
The user should be able to log in with unencrypted, "password" method.


When run with ctest, the tests will create a database called "sqlate_test_HOSTNAME" where HOSTNAME is
Expand Down
6 changes: 0 additions & 6 deletions tests/README.tests

This file was deleted.

0 comments on commit 0bde669

Please sign in to comment.