Unit Testing #21

New issue

Closed

opened 2014-03-12 02:20:17 +00:00 by jamie · 6 comments

jamie commented

2014-03-12 02:20:17 +00:00

(Migrated from git.hazaar.io)

We need to implement some sort of unit testing scheme, probably based on PHPUnit.

Zend reference: http://framework.zend.com/manual/2.1/en/modules/zend.test.phpunit.html

We need to implement some sort of unit testing scheme, probably based on PHPUnit. Zend reference: http://framework.zend.com/manual/2.1/en/modules/zend.test.phpunit.html

jamie commented

2014-03-12 02:57:35 +00:00

(Migrated from git.hazaar.io)

Test scripts should go in to a /test directory. We can then execute a hazaar test project command to execute the unit test with full logging.

Test scripts should go in to a `/test` directory. We can then execute a `hazaar test project` command to execute the unit test with full logging.

jamie commented

2014-03-17 22:07:28 +00:00

(Migrated from git.hazaar.io)

As of 3b2614f7c we have some basic unit testing under way. There is only one test, but it's a start for testing the continuous integration service we have set up in GitLab.

Tests can be run manually by executing PHPUnit directly with:

phpunit --bootstrap tests/bootstrap.php tests

As of 3b2614f7c we have some basic unit testing under way. There is only one test, but it's a start for testing the continuous integration service we have set up in GitLab. Tests can be run manually by executing PHPUnit directly with: ``` phpunit --bootstrap tests/bootstrap.php tests ```

jamie commented

2014-03-17 23:43:57 +00:00

(Migrated from git.hazaar.io)

This is working well and integrated with the GitLab CI server. Pushes to master will cause the unit testing to execute automatically.

jamie commented

2015-12-03 02:27:10 +00:00

(Migrated from git.hazaar.io)

mentioned in commit 3b2614f7cc

mentioned in commit 3b2614f7cc42cca21eed7e40828aa1f7659903a6

jamie commented

2016-06-27 23:31:26 +00:00

(Migrated from git.hazaar.io)