Home >Backend Development >PHP Tutorial >Organizing phpunit function points_PHP tutorial
Organizing phpunit function points_PHP tutorial
- WBOYOriginal
- 2016-07-14 10:07:18838browse
Set the scene
Create array Fixtures
[php]
protected function setUp()
{
//Create array fixture.
$this->fixture = array();
}
"Kit-level assembler" shared fixture is sharedFixture
The $sharedFixture attribute of the PHPUnit_Framework_TestSuite object is available in both the PHPUnit_Framework_TestSuite object collection and the PHPUnit_Framework_TestCase object.
[php]
protected function setUp()
{
$this->sharedFixture = new PDO(
'mysql:host=wopr;dbname=test',
'root',
''
);
}
provider data provider
Using data providers
Organizing test suites
The PHPUnit_Framework_TestSuite class of the PHPUnit framework allows us to organize some tests in a hierarchical structure composed of several test suites. Let's look at the PHPUnit-specific test suite through an example.
Example 7.1 shows a truncated version of Tests/AllTests.php, and Example 7.2 shows a truncated version of Tests/Framework/AllTests.php.
Level 1:
[php]
if (!defined('PHPUnit_MAIN_METHOD')) {
define('PHPUnit_MAIN_METHOD', 'AllTests::main');
}
require_once 'PHPUnit/Framework.php';
require_once 'PHPUnit/TextUI/TestRunner.php';
require_once 'Framework/AllTests.php';
// ...
class AllTests
{
public static function main()
{
PHPUnit_TextUI_TestRunner::run(self::suite());
}
public static function suite()
{
$suite = new PHPUnit_Framework_TestSuite('PHPUnit');
$suite->addTest(Framework_AllTests::suite());
// ...
return $suite;
}
}
if (PHPUnit_MAIN_METHOD == 'AllTests::main') {
AllTests::main();
}
?>
Level 2:
[php]
if (!defined('PHPUnit_MAIN_METHOD')) {
define('PHPUnit_MAIN_METHOD', 'Framework_AllTests::main');
}
require_once 'PHPUnit/Framework.php';
require_once 'PHPUnit/TextUI/TestRunner.php';
require_once 'Framework/AssertTest.php';
// ...
class Framework_AllTests
{
public static function main()
{
PHPUnit_TextUI_TestRunner::run(self::suite());
}
public static function suite()
{
$suite = new PHPUnit_Framework_TestSuite('PHPUnit Framework');
$suite->addTestSuite('Framework_AssertTest');
// ...
return $suite;
}
}
if (PHPUnit_MAIN_METHOD == 'Framework_AllTests::main') {
Framework_AllTests::main();
}
?>
Level 3:
[php]
/**
* PHPunit test suite
* /tests/Framework/Framework/AssertTest.php
* @anthor Chen Wei Han
* @copyright 2011-7-6 02:10:29 pm
* @package phpunit
* @todo
*/
//require_once 'PHPUnit/Framework.php';
class Framework_Framework_AssertTest extends PHPUnit_Framework_TestCase{
public function testNewArrayIsEmpty()
{
// Create array fixture.
$fixture = array();
// Assert that the size of the array fixture is 0. // Add an element to the array fixture.
$fixture[] = 'Element';
//Assert that the size of the array fixture is 1.
$this->assertEquals(1, sizeof($fixture));
}
}
?>
Class Framework_AssertTest is a standard test case that extends PHPUnit_Framework_TestCase.
Running Tests/AllTests.php will use the TextUI test launcher to run all tests, while running Tests/Framework/AllTests.php will only run tests of class PHPUnit_Framework_*.
Kit level assembler
Class PHPUnit_Framework_TestSuite provides two template methods, setUp() and tearDown(), which are called before the first test and after the last test of the test suite respectively.
[php]
require_once 'MyTest.php';
class MySuite extends PHPUnit_Framework_TestSuite
{
public static function suite()
{
return new MySuite('MyTest');
}
protected function setUp()
{
print "nMySuite::setUp()";
}
protected function tearDown()
{
print "nMySuite::tearDown()";
}
}
?>
Incomplete and skipped tests
public function testSomething()
{
}
If we separate successful tests and failed tests as green and red lights, we also need a yellow light to mark unfinished or unimplemented tests. PHPUnit_Framework_IncompleteTest is a marking interface used to mark exceptions raised when the test result is incomplete or not currently implemented.
[php]
require_once 'PHPUnit/Framework.php';
class SampleTest extends PHPUnit_Framework_TestCase
{
public function testSomething()
{
//Optional: You can test anything.
$this->assertTrue(TRUE, 'This should already work.');
// Stop here and mark the test as incomplete.
$this->markTestIncomplete(
'This test has not been implemented yet.'
);
}
}
?>
Skipped test
Not all tests may run in a specific environment. Consider an example of a database extraction layer with multiple drivers to support different database systems. MySQL driven tests can of course only be run on a MySQL server. $this->markTestSkipped
[php]
require_once 'PHPUnit/Framework.php';
class DatabaseTest extends PHPUnit_Framework_TestCase
{
protected function setUp()
{
if (!extension_loaded('mysqli')) {
$this->markTestSkipped(
'The MySQLi extension is not available.'
);
} }
}
public function testConnection()
{
// ...
}
}
?>
PHPUnit_Framework_TestResult
When you are running all these tests, you need to store all the results somewhere: how many tests were run, which ones failed, and how long they took.
PHPUnit comes with two specific test decorators: PHPUnit_Extensions_RepeatedTest and PHPUnit_Extensions_TestSetup. The former is used to run a test repeatedly and only count as successful if all iterations succeed. The latter one is discussed in Chapter 6.
To customize PHPUnit_Framework_TestResult, there is no need to write its entire subclass. Most of the time, it is enough to implement a new PHPUnit_Framework_TestListener (see Table 22.14) and attach it to the PHPUnit_Framework_TestResult object before running the test.
Example 23.4: Running and observing a test suite
[php] www.2cto.com
require_once 'PHPUnit/Framework.php';
require_once 'ArrayTest.php';
require_once 'SimpleTestListener.php';
// Create a test suite including tests from class ArrayTest.
$suite = new PHPUnit_Framework_TestSuite('ArrayTest');
// Create a test result and attach a SimpleTestListener object as an observer to it.
$result = new PHPUnit_Framework_TestResult;
$result->addListener(new SimpleTestListener);
// Run the test.
$suite->run($result);
?>
Statement：
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Previous article：Common PHP symbols and functions that you must know when playing PHP_PHP TutorialNext article：Common PHP symbols and functions that you must know when playing PHP_PHP Tutorial