|
|
1 неделя назад | |
|---|---|---|
| .. | ||
| integration | 1 неделя назад | |
| units | 1 неделя назад | |
| .env.example | 1 месяц назад | |
| README.md | 1 неделя назад | |
| bootstrap.php | 2 недель назад | |
| phpcpd.sh | 1 месяц назад | |
| phpunit.xml | 1 месяц назад | |
Unit tests for UNA.
http://getcomposer.org/doc/00-intro.md#installation-nix
Run the following from the script root folder (includes test tools from require-dev):
composer.phar install
or:
composer install
Alternatively:
phing prepare
Production / package installs should omit test tools:
composer install --no-dev
Run the following command from the script root folder after installation:
./plugins/bin/phpunit -c tests/phpunit.xml
or:
composer test
Alternatively:
phing test
JUnit report: logs/junit.xml.
Unit tests only:
phing test-units
or:
composer test-units
JUnit report: logs/junit-units.xml.
Integration tests only:
phing test-integration
or:
composer test-integration
JUnit report: logs/junit-integration.xml.
Integration tests read tests/.env when present (cp tests/.env.example tests/.env). Without that file they use installer defaults. Tests skip an account that is not installed.
Run the same suites inside the php service so PHP can reach MariaDB at host mysql. From the repository root, with docker compose up -d and UNA already installed:
Unit tests:
docker compose exec -w /opt/una php ./plugins/bin/phpunit -c tests/phpunit.xml --testsuite Units
Integration tests:
docker compose exec -w /opt/una php ./plugins/bin/phpunit -c tests/phpunit.xml --testsuite Integration
One test class or method:
docker compose exec -w /opt/una php ./plugins/bin/phpunit -c tests/phpunit.xml --filter TestName