All Projects → nette → Tester

nette / Tester

Licence: other
Tester: enjoyable unit testing in PHP with code coverage reporter. 🍏🍏🍎🍏

Projects that are alternatives of or similar to Tester

concise
✅ Concise is test framework for using plain English and minimal code, built on PHPUnit.
Stars: ✭ 47 (-83.27%)
Mutual labels:  unit-testing, phpunit, assertions
wp-phpunit
WordPress core PHPUnit library. [READ ONLY] Versions for new WordPress releases are built daily.
Stars: ✭ 65 (-76.87%)
Mutual labels:  unit-testing, phpunit
Forms
📝 Generating, validating and processing secure forms in PHP. Handy API, fully customizable, server & client side validation and mature design.
Stars: ✭ 272 (-3.2%)
Mutual labels:  nette, nette-framework
angular-material-boilerplate
A straightforward and well structured boilerplate based on Google's Angular Material project.
Stars: ✭ 28 (-90.04%)
Mutual labels:  unit-testing, code-coverage
reCAPTCHA
‼️ Google reCAPTCHA (security) for Nette Framework \ Forms
Stars: ✭ 35 (-87.54%)
Mutual labels:  nette, nette-framework
behat-code-coverage
Generate Code Coverage reports for Behat tests
Stars: ✭ 48 (-82.92%)
Mutual labels:  xdebug, code-coverage
logging
💥 Universal logging support to Tracy / Nette Framework (@nette)
Stars: ✭ 18 (-93.59%)
Mutual labels:  nette, nette-framework
vim-UT
Unit Testing plugin for Vim
Stars: ✭ 18 (-93.59%)
Mutual labels:  unit-testing, assertions
playground
📚 Examples, projects, webprojects, skeletons for Nette Framework (@nette) from community members. Included @contributte @apitte @nettrine projects.
Stars: ✭ 23 (-91.81%)
Mutual labels:  nette, nette-framework
codeception
▶️ Integration of Nette Framework to Codeception.
Stars: ✭ 27 (-90.39%)
Mutual labels:  nette, nette-framework
php-skeleton
A skeleton to start new high-quality PHP projects without worrying about bootstrapping everything from scratch.
Stars: ✭ 23 (-91.81%)
Mutual labels:  xdebug, phpunit
NiftyGrid
DataGrid for Nette Framework
Stars: ✭ 34 (-87.9%)
Mutual labels:  nette, nette-framework
fileupload
🆙 File uploads on steroids for Nette Framework (@nette). Implements blueimp/jquery-file-upload.
Stars: ✭ 28 (-90.04%)
Mutual labels:  nette, nette-framework
application
✨ Extra contrib to nette/application (@nette)
Stars: ✭ 23 (-91.81%)
Mutual labels:  nette, nette-framework
migrations
🏃 Doctrine Migrations for Nette Framework
Stars: ✭ 36 (-87.19%)
Mutual labels:  nette, nette-framework
slim-nette-extension
Nette Extension for Slim API micro-framework using middlewares.
Stars: ✭ 17 (-93.95%)
Mutual labels:  nette, nette-framework
web-project
Standard Web Project: a simple skeleton application using the Nette
Stars: ✭ 88 (-68.68%)
Mutual labels:  nette, nette-framework
image-storage
🌠 Image storage for Nette framework
Stars: ✭ 27 (-90.39%)
Mutual labels:  nette, nette-framework
orm
🔥 Well-integrated Doctrine ORM for Nette Framework
Stars: ✭ 51 (-81.85%)
Mutual labels:  nette, nette-framework
command-line
⌨ Command line options and arguments parser.
Stars: ✭ 35 (-87.54%)
Mutual labels:  nette, nette-framework

Nette Tester: enjoyable unit testing

Downloads this Month Tests Build Status Windows Latest Stable Version License

Introduction

Nette Tester is a productive and enjoyable unit testing framework. It's used by the Nette Framework and is capable of testing any PHP code.

Documentation is available on the Nette Tester website. Read the blog for new information.

Support Tester

Do you like Nette Tester? Are you looking forward to the new features?

Buy me a coffee

Thank you!

Installation

The recommended way to install Nette Tester is through Composer:

composer require nette/tester --dev

Alternatively, you can download the tester.phar file.

  • Nette Tester 2.4 is compatible with PHP 7.2 to 8.0
  • Nette Tester 2.3 is compatible with PHP 7.1 to 8.0
  • Nette Tester 2.1 & 2.2 is compatible with PHP 7.1 to 7.3
  • Nette Tester 2.0 is compatible with PHP 5.6 to 7.3

Collecting and processing code coverage information depends on Xdebug or PCOV extension, or PHPDBG SAPI.

Writing Tests

Imagine that we are testing this simple class:

class Greeting
{
	function say($name)
	{
		if (!$name) {
			throw new InvalidArgumentException('Invalid name.');
		}
		return "Hello $name";
	}
}

So we create test file named greeting.test.phpt:

require 'src/bootstrap.php';

use Tester\Assert;

$h = new Greeting;

// use an assertion function to test say()
Assert::same('Hello John', $h->say('John'));

Thats' all!

Now we run tests from command-line using the tester command:

> tester
 _____ ___  ___ _____ ___  ___
|_   _/ __)( __/_   _/ __)| _ )
  |_| \___ /___) |_| \___ |_|_\  v2.4.0

PHP 7.3.3 | php -n | 8 threads
.
OK (1 tests, 0 skipped, 0.0 seconds)

Nette Tester prints dot for successful test, F for failed test and S when the test has been skipped.

Assertions

This table shows all assertions (class Assert means Tester\Assert):

  • Assert::same($expected, $actual) - Reports an error if $expected and $actual are not the same.
  • Assert::notSame($expected, $actual) - Reports an error if $expected and $actual are the same.
  • Assert::equal($expected, $actual) - Like same(), but identity of objects and the order of keys in the arrays are ignored.
  • Assert::notEqual($expected, $actual) - Like notSame(), but identity of objects and arrays order are ignored.
  • Assert::contains($needle, array $haystack) - Reports an error if $needle is not an element of $haystack.
  • Assert::contains($needle, string $haystack) - Reports an error if $needle is not a substring of $haystack.
  • Assert::notContains($needle, array $haystack) - Reports an error if $needle is an element of $haystack.
  • Assert::notContains($needle, string $haystack) - Reports an error if $needle is a substring of $haystack.
  • Assert::true($value) - Reports an error if $value is not true.
  • Assert::false($value) - Reports an error if $value is not false.
  • Assert::truthy($value) - Reports an error if $value is not truthy.
  • Assert::falsey($value) - Reports an error if $value is not falsey.
  • Assert::null($value) - Reports an error if $value is not null.
  • Assert::nan($value) - Reports an error if $value is not NAN.
  • Assert::type($type, $value) - Reports an error if the variable $value is not of PHP or class type $type.
  • Assert::exception($closure, $class, $message = null, $code = null) - Checks if the function throws exception.
  • Assert::error($closure, $level, $message = null) - Checks if the function $closure throws PHP warning/notice/error.
  • Assert::noError($closure) - Checks that the function $closure does not throw PHP warning/notice/error or exception.
  • Assert::match($pattern, $value) - Compares result using regular expression or mask.
  • Assert::matchFile($file, $value) - Compares result using regular expression or mask sorted in file.
  • Assert::count($count, $value) - Reports an error if number of items in $value is not $count.
  • Assert::with($objectOrClass, $closure) - Executes function that can access private and protected members of given object via $this.

Testing exceptions:

Assert::exception(function () {
	$h = new Greeting;
	$h->say(null);
}, InvalidArgumentException::class, 'Invalid name.');

Testing PHP errors, warnings or notices:

Assert::error(function () {
	$h = new Greeting;
	echo $h->abc;
}, E_NOTICE, 'Undefined property: Greeting::$abc');

Testing private access methods:

$h = new Greeting;
Assert::with($h, function () {
	// normalize() is internal private method.
	Assert::same('Hello David', $this->normalize('Hello david')); // $this is Greeting
});

Tips and features

Running unit tests manually is annoying, so let Nette Tester to watch your folder with code and automatically re-run tests whenever code is changed:

tester -w /my/source/codes

Running tests in parallel is very much faster and Nette Tester uses 8 threads as default. If you wish to run the tests in series use:

tester -j 1

How do you find code that is not yet tested? Use Code-Coverage Analysis. This feature requires you have installed Xdebug or PCOV extension, or you are using PHPDBG SAPI. This will generate nice HTML report in coverage.html.

tester . -c php.ini --coverage coverage.html --coverage-src /my/source/codes

We can load Nette Tester using Composer's autoloader. In this case it is important to setup Nette Tester environment:

require 'vendor/autoload.php';

Tester\Environment::setup();

We can also test HTML pages. Let the template engine generate HTML code or download existing page to $html variable. We will check whether the page contains form fields for username and password. The syntax is the same as the CSS selectors:

$dom = Tester\DomQuery::fromHtml($html);

Assert::true($dom->has('input[name="username"]'));
Assert::true($dom->has('input[name="password"]'));

For more inspiration see how Nette Tester tests itself.

Running tests

The command-line test runner can be invoked through the tester command (or php tester.php). Take a look at the command-line options:

> tester

Usage:
    tester [options] [<test file> | <directory>]...

Options:
    -p <path>                    Specify PHP interpreter to run (default: php).
    -c <path>                    Look for php.ini file (or look in directory) <path>.
    -C                           Use system-wide php.ini.
    -l | --log <path>            Write log to file <path>.
    -d <key=value>...            Define INI entry 'key' with value 'val'.
    -s                           Show information about skipped tests.
    --stop-on-fail               Stop execution upon the first failure.
    -j <num>                     Run <num> jobs in parallel (default: 8).
    -o <console|tap|junit|none>  Specify output format.
    -w | --watch <path>          Watch directory.
    -i | --info                  Show tests environment info and exit.
    --setup <path>               Script for runner setup.
    --temp <path>                Path to temporary directory. Default by sys_get_temp_dir().
    --colors [1|0]               Enable or disable colors.
    --coverage <path>            Generate code coverage report to file.
    --coverage-src <path>        Path to source code.
    -h | --help                  This help.
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].