The Nette Tester 1.3.1 has been released just yesterday. This new patch
version fixes few minor bugs.
The FileMock does not use
uniqid() anymore and it numbers mocked files sequentially. It
prevents possible collisions.
You can acquire multiple locks in one test by the Environment::lock() now. Before
1.3.1, every next lock may release the previous one.
If you use the
option, the testing progress is stopped in initial phase too. For example, if
you forgot to call
(new TestCase)->run() in a
@testCase annoted file.
If you are familiar with the Tester, you know that a test will fail when does
not invoke any assetion. This feature didn't work with HHVM < 3.4.0 because
of HHVM bug. Since the HHVM 3.4.0 this feature works.
Beside the fixes, the
--info output has
been concentrated a little bit.
And that's all. Enjoy the testing!
I would like to describe news and changes in Nette Tester 1.3.0. I'll start
from the tiny one.
FileMock class, introduced in the 1.2.0, now works with
Next change is a new command line option
-o (output format). The
option can enumerate from three values:
console value is the default one. But
when explicitly specified, Tester's ASCII logo is not printed. It is handy when
Tester runs from IDE. The
tap value is Test Anything Protocol
output format and it is replacement for deprecated
This deprecated option has been removed from help screen but still works to keep
backward compatibility. The
none value suppresses any output, only
bad usage exceptions are printed.
And the best for last. Tester now supports HHVM from version 3.3.0. And how
to use it? Simply pass HHVM binary name by
-p option. For
vendor/bin/tester -p hhvm tests
Nette Tester is a PHP testing tool. It has been four months since the Tester 1.0.0 has been
released, and it is a few days since the version 1.2.0 is
out. I would like to describe the changes in here.
If you are interested in how well your tests cover your code, the new
--coverage cc.html and
--coverage-src path should be useful. The first one enables the
collection of coverage details, and outputs it in
cc.html. You will
get a well-arranged HTML report. The second option reduces the path to the
analysed source files (instead of passing the directory, you can pass a single
file as a path since version 1.2.0).
Since running the tests in parallel has been shown as non-problematic, the
tests will now run in 33 parallel threads by default. That's all.
I will describe the next change via an example, imagine this simple
class MyTest extends Tester\TestCase
public function testSomething()
Assert::fail('I have no reason to be a success.');
Have you ever written following code in PHP?
$obj = new MyClass;
$result = $obj->process($input);
So, have you ever dumped a function call result just because to check it by
eye that it returns what it should return? You surely do it many times per day.
In case everything works do you delete this code and do you expect that the
class will not be broken in future? Murphy's Law guarantees opposite
In fact, we wrote the test. And if we didn’t delete it we could run it any
time in the future to verify that everything still works as it should. You may
create a large amount of these tests over the time, so it would be nice if we
were able to run them automatically. It would be useful to slightly modify test
not to require our inspection, simply to be able to check itself.
And the Nette Tester helps exactly with that. Meet the Nette Tester in the introduction…