PHPUnit Pocket Guide - Command Line Testing Tool_PHP Tutorial

The PHPUnit command line testing tool is called through the phpunit command. The following code shows how to run tests through the PHPUnit command line testing tool.

phpunit ArrayTest

phpunit ArrayTest
PHPUnit 2.3.0 by Sebastian Bergmann.

Time: 0.067288

OK (2 tests)

PHPUnit 2.3.0 by Sebastian Bergmann.

Time: 0.067288

OK (2 tests)

For each test, the PHPUnit command line testing tool prints a character indicating the process:

·The test successfully prints ".".

·When running the test method, an assertion failure occurs and "F" is printed.

· When running the test method, an error occurs and "E" is printed.

·The test is not completed or the test does not print "I" (see the chapter "Unfinished Tests" at the end of this book).

PHPUnit can distinguish between failures and errors. A failure is a PHPUnit assertion violation, and an error is an unexpected exception or a PHP error. Sometimes this distinction is useful because mistakes are easier to fix than failures. If you have a long list of issues, it's a good idea to resolve all the errors first and then see if any failures remain.

phpunit --help
PHPUnit 2.3.0 by Sebastian Bergmann.

Usage: phpunit [switches] UnitTest [UnitTest.php]
--coverage-data ＜file＞ Write code-coverage data in raw format to file.
--coverage-html ＜file＞ Write code-coverage data in HTML format to file.
--coverage-text ＜file＞ Write code-coverage data in text format to file.
--testdox-html ＜file＞ Write agile documentation in HTML format to file.
--testdox-text ＜file＞ Write agile documentation in Text format to file.
--log-xml ＜file＞ Log test progress in XML format to file.
--loader ＜loader＞ TestSuiteLoader implementation to use.
--skeleton Generate skeleton UnitTest class for Unit in Unit.php.
--wait Waits for a keystroke after each test.
--help Prints this usage information.
--version Prints the version and exits.

Let’s take a look at some of the following code command line testing tool options:

phpunit --help
PHPUnit 2.3.0 by Sebastian Bergmann.

Usage: phpunit [switches] UnitTest [UnitTest.php]
--coverage-data ＜file＞ Write code-coverage data in raw format to file.
--coverage-html ＜file＞ Write code-coverage data in HTML format to file.
--coverage-text ＜file＞ Write code-coverage data in text format to file.
--testdox-html ＜file＞ Write agile documentation in HTML format to file.
--testdox-text ＜file＞ Write agile documentation in Text format to file.
--log-xml ＜file＞ Log test progress in XML format to file.
--loader ＜loader＞ TestSuiteLoader implementation to use.
--skeleton Generate skeleton UnitTest class for Unit in Unit.php.
--wait Waits for a keystroke after each test.
--help Prints this usage information.
--version Prints the version and exits.

phpunit UnitTest

Run the test provided by the class UnitTest, which should be defined in the source file UnitTest.php.

The class UnitTest must inherit the PHPUnit2_Framework_TestCase class, or provide a public static method suite and return a class of the PHPUnit2_ Framework_Test object (for example, an instance of the class PHPUnit2_Framework_TestSuite)

phpunit UnitTest UnitTest.php

＜?xml version="1.0" encoding="UTF-8"?＞
＜testsuites＞
　＜testsuite name="ArrayTest" tests="2" failures="0" errors="0" time="0.020026"＞
　＜testcase name="testNewArrayIsEmpty" class="ArrayTest" time="0.014449"/＞
　＜testcase name="testArrayContainsAnElement" class="ArrayTest" time="0.005577"/＞
＜/testsuite＞
＜/testsuites＞

Run the test provided by the UnitTest class, which must be defined in the source file (UnitTest.php) specified by the command. --coverage-data, --coverage-html, and --coverage-text Control the analysis and collection of code coverage information for running tests (see the Code Coverage Analysis section at the end of this book) --testdox-html and --testdox-text Generate agile documentation for running tests in HTML or plain text format (see the "Other uses of testing" chapter at the end of this book) --log-xml Generate log files in XML format for running tests. The next example shows the XML log file generated for a test in ArrayTest.

＜testsuites＞ ＜testsuite name="ArrayTest" tests="2" failures="0" errors="0" time="0.020026"> ＜testcase name="testNewArrayIsEmpty" class="ArrayTest" time="0.014449"/＞ ＜testcase name="testArrayContainsAnElement" class="ArrayTest" time="0.005577"/＞ ＜/testsuite＞ ＜/testsuites＞

The following XML log file is generated for two tests of the test class named FailureErrorTest, one is testFailure and the other is testError. This shows how failures and errors are represented separately.

＜?xml version="1.0" encoding="UTF-8"?＞
＜testsuites＞
　＜testsuite name="FailureErrorTest" tests="2" failures="1" errors="1" time="0.013603"＞
　＜testcase name="testFailure" class="FailureErrorTest" time="0.011872"＞
　＜failure message="" type="PHPUnit2_Framework_AssertionFailedError"＞＜/failure＞
＜/testcase＞
＜testcase name="testError" class="FailureErrorTest" time="0.001731"＞
　＜error message="" type="Exception"＞＜/error＞
＜/testcase＞
＜/testsuite＞
＜/testsuites＞
--loader

＜testsuites＞
＜testsuite name="FailureErrorTest" tests="2" failures="1" errors="1" time="0.013603"＞
＜testcase name="testFailure" class="FailureErrorTest" time="0.011872"＞
＜failure message="" type="PHPUnit2_Framework_AssertionFailedError"＞＜/failure＞
＜/testcase＞
＜testcase name="testError" class="FailureErrorTest" time="0.001731"＞
＜error message="" type="Exception"＞＜/error＞
＜/testcase＞
＜/testsuite＞
＜/testsuites＞
--loader
Specifies the test suite loader to be used.

phpunit --skeleton Sample
PHPUnit 2.3.0 by Sebastian Bergmann.
Wrote test class skeleton for Sample to
SampleTest.php.
phpunit SampleTest
PHPUnit 2.3.0 by Sebastian Bergmann.
I
Time: 0.007268
There was 1 incomplete test case:
1) testSampleMethod(SampleTest)
OK, but incomplete test cases!!!
Tests run: 1, incomplete test cases: 1.

The standard test suite loader will look for source files in the current working directory and the path defined by PHP's include_path configuration directive. According to the naming rules of PEAR, the source file mapped to a class name in the form Project_Package_Class is Project/Package/Class.php.

--skeleton

public function testSampleMethod( ) {}

A framework that generates a test case class named UnitTest (in the file UnitTest.php) for the class Unit (in the file Unit.php). For each method of the original class, an unfinished test case is provided in the generated test case class (see the "Unfinished Tests" section at the end of this book).

The following example shows how to generate a test class skeleton for a class named Sample.

phpunit --skeleton Sample
PHPUnit 2.3.0 by Sebastian Bergmann.
Wrote test class skeleton for Sample to SampleTest.php.

phpunit SampleTest

PHPUnit 2.3.0 by Sebastian Bergmann. I Time: 0.007268 There was 1 incomplete test case: 1) testSampleMethod(SampleTest) OK, but incomplete test cases!!! Tests run: 1, incomplete test cases: 1.

When you write tests for existing code, you have to repeat a lot of the same code snippets, such as: PHPUnit can help you analyze existing code and generate a framework of test case classes. --wait At the end of each test, wait for a keystroke. This is useful especially if you are running tests in a window where only the test is running at all times.

Tip: When there is a PHP syntax error in the code being tested, the text interface test will exit directly without outputting any error message. The standard test suite loader checks the test suite's source files for PHP syntax errors, however, it does not check the source files included in the test suite for syntax errors. Future versions of PHPUnit will address this issue using sandboxed PHP interpreter classes. http://www.bkjia.com/PHPjc/508482.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/508482.htmlTechArticlePHPUnit command line testing tool is called through the phpunit command. The following code shows how to run tests through the PHPUnit command line testing tool. phpunit ArrayTest PHPUnit 2.3.0 by Sebastian...