partkeepr

fork of partkeepr
git clone https://git.e1e0.net/partkeepr.git
Log | Files | Refs | Submodules | README | LICENSE

commit 44bccdb4bd5af64dd31d96ae2bee8d1d9e4be581
parent aae407052d0c3d4800384f7103ac4329a90f447e
Author: Felicitus <felicitus@felicitus.org>
Date:   Wed, 16 Sep 2015 17:32:39 +0200

Updated the testing documentation about the preconfigured database adapters

Diffstat:
Ddocumentation/developer/UNIT-TESTS | 10----------
Mdocumentation/developer/UNIT-TESTS.md | 10+++++++++-
2 files changed, 9 insertions(+), 11 deletions(-)

diff --git a/documentation/developer/UNIT-TESTS b/documentation/developer/UNIT-TESTS @@ -1,9 +0,0 @@ -Unit tests are usually ran by calling "phing test". - -If you need to run individual tests, you can do so by using the following command: - -phpunit --bootstrap tests/bootstrap.php <yourtestcase> - -Full example: - -phpunit --bootstrap tests/bootstrap.php tests/Part/PartServiceTest.php- \ No newline at end of file diff --git a/documentation/developer/UNIT-TESTS.md b/documentation/developer/UNIT-TESTS.md @@ -1,15 +1,23 @@ # Functional / Unit Testing + +## Prerequisites + In order to run functional / unit tests, you first need to define the following environment variable to specify which test database you are using: `export SYMFONY__TESTDB=<databasetype>` -The following databases are supported: +The following databases are pre-configured in `config_test.yml`: - `mysql` - `pgsql` - `sqlite` + +Note that the database connections are configured for travis testing; you might need to change the database name, +user and password properties. + +## Running the tests The unit tests are ran by `phpunit -c app/`. This also generates a coverage report in the directory `reports/coverage`.