Changes in Nette Tester 1.3.1

9 years ago by Miloslav Hůla  

The Nette Tester 1.3.1 has been released just yesterday. This new patch version fixes a 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 --stop-on-fail option, the testing progress is stopped in the initial phase too. For example, if you forgot to call (new TestCase)->run() in a @testCase annotated file.

If you are familiar with the Tester, you know that a test will fail when does not invoke any assertion. This feature didn't work with HHVM < 3.4.0 because of the HHVM bug. Since the HHVM 3.4.0, this feature works.

Besides the fixes, the --info output has been concentrated a little bit.

And that's all. Enjoy the testing!

Recent posts

Differentiated Error-Presenters 4×x and 5×x

Until now, when an error occurred in your application, you had a standard single setting for handling all errors. Nette Application 3.2 allows you to specify different presenters for different types of errors. Specifically, you can have one presenter for BadRequestException (4xx type errors) and…

2 hours ago  ·  a minute to read

#[Requires] Attribute Simplifies Access Control

The #[Requires] attribute allows you to define rules for accessing presenters or their methods. Imagine being able to restrict access to certain actions to POST requests only, or conversely, allow calls only from AJAX. This is now possible.

2 days ago  ·  2 minutes to read

Elegant Presenter Structuring

Do you appreciate order and structure? When everything is exactly where it should be, making it easy to navigate? Of course—who wouldn’t. Nette Framework 3.2 introduces a new way to organize presenters and their templates in your application.

5 days ago  ·  3 minutes to read