Getting Started with Nette Tester

Have you ever written code like this in PHP?

$obj = new MyClass;
$result = $obj->process($input);

var_dump($result);

That is, have you printed out the result of a function call just to visually check if it returns what it should? You probably do this many times a day. Hand on heart: if everything works correctly, do you delete this code? Do you expect the class not to break in the future? Murphy's laws guarantee the opposite :-)

Basically, you wrote a test. It just needs a slight modification so that it does not require visual inspection but checks itself. And if you don't delete the test, you can run it at any time in the future to verify that everything still works as it should. Over time, you'll create a large number of such tests, so it would be useful to run them automatically.

And Nette Tester will help you with all this.

What Makes Tester Unique?

Writing tests for Nette Tester is unique in that each test is a standard PHP script that can be run standalone.

So, when you write a test, you can simply run it and find out if there is, for example, a programming error in it. If it works correctly. If not, you can easily step through it in your IDE and look for the bug. You can even open it in a browser.

And most importantly – by running it, you perform the test. You immediately find out whether it passed or failed. How? Let's show it. We'll write a trivial test of working with a PHP array and save it to the file ArrayTest.php:

<?php
use Tester\Assert;

require __DIR__ . '/vendor/autoload.php';  # load Composer autoloader
Tester\Environment::setup();               # initialize Nette Tester

$stack = [];
Assert::same(0, count($stack));   # we expect count() to return zero

$stack[] = 'foo';
Assert::same(1, count($stack));   # we expect count() to return one
Assert::contains('foo', $stack);  # verify that $stack contains the item 'foo'

As you can see, so-called assertion methods like Assert::same() are used to confirm that the actual value matches the expected value.

We have the test written, and we can run it from the command line. The first run will reveal possible syntax errors, and if you did not make a typo anywhere, it will print:

$ php ArrayTest.php

OK

Try changing the assertion in the test to a false one, like Assert::contains('XXX', $stack);, and watch what happens when running:

$ php ArrayTest.php

Failed: ['foo'] should contain 'XXX'

in ArrayTest.php(17) Assert::contains('XXX', $stack);

FAILURE

We continue about writing tests in the Writing Tests chapter.

Installation and Requirements

The minimum PHP version required by Tester is 7.1 (more details in the table Supported PHP versions). The preferred way of installation is using Composer:

composer require --dev nette/tester

Try running Nette Tester from the command line (without arguments it will only print help):

vendor/bin/tester

Running Tests

As the application grows, the number of tests grows with it. It would not be practical to run tests one by one. Therefore, Tester has a bulk test runner, which we call from the command line. As a parameter, we specify the directory in which the tests are located. A dot means the current directory.

vendor/bin/tester .

The test runner searches the specified directory and all subdirectories and looks for tests, which are files *.phpt and *Test.php. It will also find our test ArrayTest.php, since it matches the mask.

Then it starts testing. Each test is run as a new PHP process, so it runs completely isolated from the others. It runs them in parallel in multiple threads, making it extremely fast. And it first runs the tests that failed during the previous run, so you immediately find out if you managed to fix the bug.

During test execution, Tester continuously prints the results to the terminal as characters:

• . – test passed
• s – test has been skipped
• F – test failed

The output may look like this:

 _____ ___  ___ _____ ___  ___
|_   _/ __)( __/_   _/ __)| _ )
  |_| \___ /___) |_| \___ |_|_\  v2.5.2

Note: No php.ini is used.
PHP 8.3.2 (cli) | php -n | 8 threads

........s................F.........

-- FAILED: greeting.phpt
   Failed: 'Hello John' should be
       ... 'Hello Peter'

   in greeting.phpt(19) Assert::same('Hello Peter', $o->say('John'));

FAILURES! (35 tests, 1 failures, 1 skipped, 1.7 seconds)

35 tests were run, one failed, one was skipped.

We continue in the Running Tests chapter.

Watch Mode

Are you refactoring code? Or perhaps even developing according to the TDD (Test Driven Development) methodology? Then you'll like the watch mode. In this mode, Tester monitors the source codes and automatically runs itself when changed.

During development, you have a terminal in the corner of your monitor where a green status bar shines at you, and when it suddenly changes to red, you know that you have just done something not quite right. It's actually a great game where you program and try to keep the color.

Watch mode is started with the parameter –watch.

Code Coverage Reports

Tester can generate reports with an overview of how much source code the tests cover. The report can be either in human-readable HTML format or Clover XML for further machine processing.

See a sample HTML report with code coverage.

Supported PHP versions

Applies to the latest patch version.

Tester up to version 1.7 also supported HHVM 3.3.0 or higher (via tester -p hhvm). Support was discontinued from Tester version 2.0.