Hubzilla core code
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Mario d184e2708f fix language tests 10 months ago
..
acceptance [TASK] Restructure tests/ folder. 4 years ago
travis 👷Extend Travis, add PostgreSQL10. 2 years ago
unit fix language tests 10 months ago
README.md [TASK] Restructure tests/ folder. 4 years ago
infection.json.dist 👷Improve Travis, add PHP7.2. 2 years ago
phpunit-pgsql.xml Add PostgreSQL to gitlab-ci setup. 1 year ago
phpunit.xml add gitlab-ci.yml and phpunit.xml 1 year ago
phpunit.xml.dist Make it little bit less likely to erase a real database. 2 years ago

README.md

The folder tests/ contains resources for automated testing tools.

Here you will find PHPUnit, Behat, etc. files to test the functionaly of Hubzilla. Right now it only contains some basic tests to see if feasable this can help improve the project.

Contents

  • unit/ PHPUnit tests These are unit tests to check the smallest parts, like single functions. It uses the tool PHPUnit https://phpunit.de/

  • acceptance/ functional/acceptance testing These are behavioral or so called functional/acceptance testing. They are used to test business logic. They are written in Gherkin and use the tool Behat http://behat.org/

How to use?

You need the dev tools which are defined in the composer.json in the require-dev configuration. Run composer install without --no-dev to install these tools.

To run unit tests run vendor/bin/phpunit tests/unit/

To run acceptance tests run vendor/bin/behat --config tests/acceptance/behat.yml