summaryrefslogtreecommitdiff
path: root/scripts/travis_test.sh
Commit message (Collapse)AuthorAgeFilesLines
* Avoid installing tests to site-packagesJon Dufresne2017-12-101-2/+2
| | | | | | | | For library end users, there is no need to install tests alongside the package itself. This keeps the tests available for development without adding extra packages to user's site-packages directory. Reduces the size of the installed package. Avoids accidental execution of test code by an installed package.
* Test against PG 10.0 on TravisDaniele Varrazzo2017-10-241-2/+3
|
* Run tests against PostgreSQL 10 beta1test-postgres-10beta1Daniele Varrazzo2017-06-081-3/+3
| | | | | | Use the new Postgres verisoning schema: 10 is a major version, 10.0 a patch release. See https://wiki.postgresql.org/wiki/New_in_postgres_10#Change_in_Version_Numbering
* Run the test suite with postgres versions not available on travisDaniele Varrazzo2017-02-061-14/+56
|
* Fixed travis test: unset green modeDaniele Varrazzo2016-12-261-1/+1
|
* Less verbose travis testsDaniele Varrazzo2016-12-261-2/+2
|
* Configure Travis to test replicationDaniele Varrazzo2016-12-251-2/+4
|
* Don't use separate databases for testsDaniele Varrazzo2016-12-241-12/+1
| | | | | I got this wrong: I thought parallel test ran in the same VM; they are isolated instead.
* Run the tests against all the available server versionsDaniele Varrazzo2016-12-241-0/+39