kolibri-discuss team mailing list archive

[Frode Danielsen <question150409@xxxxxxxxxxxxxxxxxxxxx>]

Question #150409 on Kolibri changed:
https://answers.launchpad.net/kolibri/+question/150409

    Status: Open => Answered

Frode Danielsen proposed the following answer:
Ah, the test framework support is quite outdated in the repo. Sorry
about not mentioning this before!

We started using phpspec in early 2009. Then we discovered that it
seemed to be a dead project. Like their Google Code page now says: "As
of 11 January 2008, PHPSpec 0.2.3 has been available for download.".

So we switched to phpunit on our biggest project with Kolibri, and
started porting over tests. phpunit had support for both story/scenarios
and Selenium for integration testing as well as unit tests, and it
worked well for us. Then phpunit announced they were dropping their
story/scenario support, and it is now deprecated.

We are still using phpunit and will continue to do so for unit tests,
but will probably start using Behat (http://behat.org/) for integration
testing (which has been suggested by phpunit devs).

When we have the time we'll make sure to update the repo with more
current testing support. But as you can probably guess we're a bit tired
of porting tests after dead and/or deprecated projects and features :)

A brief rundown of our current phpunit setup is this:
- no more test.php, and a "tests" directory instead of "specs", with "integration" and "unit" sub directories
- a bootstrap.php file which sets up necessary environment variables and loads the config
- a phpunit.xml file which is loaded by phpunit automatically and makes sure the bootstrap.php file is executed

If you need help getting started with testing properly before we get the
repo updated, I can help you with the bootstrap.php and phpunit.xml
files at least. Just give me an email or something to which I should
send it.

-- 
You received this question notification because you are a member of
Kolibri Discuss, which is an answer contact for Kolibri.