PHPUnit Training Course for free

Today is an awesome day my dear fellow programmers.

Today is the day I decide to freely distribute the first couple of pages of the PHPUnit workshop I have been giving for some time now. It is a workshop that builds a small demo application the Test Driven Development way. The reason I open this workshop course is because I strongly believe everybody should understand and use PHPUnit in their projects. Another reason is marketing. As a Zend Framework Certified Engineer I am writing a wonderful book. Part of that book will have similar contents as the complete course, which today I decided to freely distribute. Yet those contents are only available when you attend the workshop (in which case you get a free copy of the entire PHPUnit e-book) or when you purchase my upcoming book, which will be available in pdf and paper format (in a bookstore near you).
Shamelessly I hope this free sample will peak your interest in either one of those.

But the bottom line: you get a nice introduction to PHPUnit for free. A course which has cost me many hours over several days to write. Hard work done with love, and with that love I share with you:

Warm winter greetings from Belgium


  1. Hari K T says:

    Previously I was not aware how much time a developer spends for writing a Book. But now I know how much time you guys spend for a single chapter and also all the other guys working behind this.
    So I appreciate your works and the valuable contents you are giving us. Also as you told I was not aware of PHP Unit until some guys asked me why you are not using it 🙂 .
    I hope this will also help some people move to learn phpunit :).

    Thanks again

  2. Fabian says:

    The training course is nice. Thanks for you work!

    You should really mention the @covers annotation, since every test should define which methods are tested. This allows finding some errors and uncovered parts of the code, write better tests and increase the real code coverage.

    And you should also make some examples for setUp() and tearDown() so the reader understands, that he must clean up the tests afterwards, to avoid tests that effect other tests.
    For example: We have an test.ini which is read and written to test parsing/writing functionality. Another tests also reads the test.ini but the test is failing, because the data is not restored.

  3. DigitalDoener says:

    Hi Nick,

    thanks you for this really detailed description. Very good introduction.

    greetings from Germany

  4. Ritchie Rossa says:

    I simply want to say that I am new to weblog and absolutely enjoyed this web site. Almost certainly I’m likely to bookmark your blog. You will absolutely come with impressive well written articles in future. Thanks for sharing with us your web-site.

  5. Karmick says:

    Very good work I really like.From above comments I am impressed and I’m thoroughly enjoying your blog.

Leave a Reply

Your email address will not be published. Required fields are marked *