PHPUnit袖珍指南 第八章 未完成测试

翻译 2006年05月25日 21:06:00

第八章 未完成测试

当开始书写新的测试用例类时,你也许想要从空的测试方法开始,譬如:

       public function testSomething( ) {

       }

我们必须跟踪书写的每个测试。空测试方法的问题是,它们被PHPUnit 框架解释作执行成功。这样产生的测试报告是没有用的。您不能区分测试实际上是成功了或是未完成。在未完成的测试方法中调用$this->fail()也不行,因为这被解释作为失败。这和未完成测试被错误解释成功一样糟糕。

如果我们认为一个成功的测试可以亮绿灯,测试失败亮红灯,那我们就需要黄灯来标记测试未完成。PHPUnit2 _ Framework_IncompleteTest是这个标志的接口,标记测试方法抛出的测试未完成或当前未完成的异常。PHPUnit2_Framework_IncompleteTestError 是这个接口的标准实现。

9显示了测试用例类SampleTest包含了一个测试方法testSomething(),通过抛出PHPUnit2 _ Framework_IncompleteTestError异常,我们将此测试标为未完成测试。

9.将测试标记为未完成

<?php

require_once 'PHPUnit2/Framework/TestCase.php';

require_once 'PHPUnit2/Framework/IncompleteTestError.php';

 

class SampleTest extends PHPUnit2_Framework_TestCase {

public function testSomething( ) {

        // Optional: Test anything here, if you want.

        $this->assertTrue(TRUE, 'This should already work.');

 

        // Stop here and mark this test as incomplete.

        // You could use any Exception which implements the

        // PHPUnit2_Framework_IncompleteTest interface.

        throw new PHPUnit2_Framework_IncompleteTestError(

     'This test has not been implemented yet.'

    );

}

}

?>

 

An incomplete test is denoted by an I in the output of the PHPUnit command-line test runner, as shown in the following example:

一个未完成的测试在PHPUnit 命令行测试器中由I 表示,如下例所示:

phpunit SampleTest

PHPUnit 2.3.0 by Sebastian Bergmann.

 

I

 

Time: 0.006657

There was 1 incomplete test case:

1) testSomething(SampleTest)

This test has not been implemented yet.

 

OK, but incomplete test cases!!!

Tests run: 1, incomplete test cases: 1.

 

--------------------------------------------------------------------------------------------------------------------

原文:

Chapter 8. Incomplete Tests

When you are working on a new test-case class, you might want to begin by writing empty test methods, such as:

 

    public function testSomething( ) {

    }

 

 

 

to keep track of the tests that you have to write. The problem with empty test methods is that they are interpreted as a success by the PHPUnit framework. This misinterpretation leads to the test reports being uselessyou cannot see whether a test is actually successful or just not yet implemented. Calling $this->fail( ) in the unimplemented test method does not help either because then the test will be interpreted as a failure. This would be just as wrong as interpreting an unimplemented test as a success.

 

If we think of a successful test as a green light, and a test failure as a red light, we need an additional yellow light to mark a test as being incomplete or not yet implemented. PHPUnit2_ Framework_IncompleteTest is a marker interface for marking an exception that is raised by a test method as the result of the test being incomplete or not currently implemented. PHPUnit2_Framework_IncompleteTestError is the standard implementation of this interface.

 

Example 9 shows a test-case class, SampleTest, that contains one test method, testSomething( ). By raising the PHPUnit2_ Framework_IncompleteTestError exception in the test method, we mark the test as being incomplete.

 

Example 9. Marking a test as incomplete

<?php

require_once 'PHPUnit2/Framework/TestCase.php';

require_once 'PHPUnit2/Framework/IncompleteTestError.php';

 

class SampleTest extends PHPUnit2_Framework_TestCase {

    public function testSomething( ) {

       // Optional: Test anything here, if you want.

       $this->assertTrue(TRUE, 'This should already work.');

 

       // Stop here and mark this test as incomplete.

       // You could use any Exception which implements the

       // PHPUnit2_Framework_IncompleteTest interface.

       throw new PHPUnit2_Framework_IncompleteTestError(

     'This test has not been implemented yet.'

    );

    }

}

?>

 

 

 

An incomplete test is denoted by an I in the output of the PHPUnit command-line test runner, as shown in the following example:

 

    phpunit SampleTest

    PHPUnit 2.3.0 by Sebastian Bergmann.

 

    I

 

    Time: 0.006657

    There was 1 incomplete test case:

    1) testSomething(SampleTest)

    This test has not been implemented yet.

 

    OK, but incomplete test cases!!!

    Tests run: 1, incomplete test cases: 1.

 

PHPUnit袖珍指南 第八章 未完成测试

第八章 未完成测试 当开始书写新的测试用例类时,你也许想要从空的测试方法开始,譬如:        public function testSomething( ) {        } 我们...

PHPUnit袖珍指南-第二章 自动测试

第二章 自动测试 最好的程序员也会犯错误。好程序员和差程序员的区别在于:好程序员能通过测试尽可能的发现错误。你越快测试错误,你就越快发现它们,发现和修正的成本就越低。这解释了为什么只在软件发布前才测...

PHPUnit袖珍指南 第十二章 测试的其他用途

一旦你开始写自动测试,你就会想要发掘更多用途。以下是一些例子。   12-1. 敏捷文档 通常来说,在采用敏捷方法作为开发流程的项目中,如极限编程,文档很难和迅速变化的项目设计和代码...

PHPUnit袖珍指南-第五章 命令行测试工具

第五章 命令行测试工具 PHPUnit命令行测试工具是通过phpunit命令调用的。如下代码显示如何通过PHPUnit命令行测试工具运行测试。 phpunit ArrayTest PHPUnit...

PHPUnit袖珍指南 第六章 装置器

第六章 装置器 编写测试最耗时的部分是边编写设置整个程序到达一个已知状态,而后在测试结束后返回到原始状态。这个已知状态叫做测试的装置器。 在例5中,装置器很简单,只是存储在变量$fixture中的...

PHPUnit袖珍指南-第一章 简介

很长时间里,我对“你什么时候会为PHPUnit写一个文档”这个问题的回答是:“你不需要PHPUnit文档,去读读JUnit文档或买一本Junit的书,试一试用PHP和PHPUnit来重写Java和Ju...

PHPUnit袖珍指南 第十章 代码覆盖率分析

第十章 代码覆盖率分析 你已经学会了怎么使用单元测试代码,但你怎么测试你的测试呢?你怎么发现没被测试的代码,换句话说,没被测试覆盖的代码?怎么衡量测试的完整性?所有这些问题的答案就是代码覆盖率分析。...

PHPUnit袖珍指南-概述

概述 聪明的Web开发人员会告诉你,越快找到代码的错误,你就能越快修正它,长期而言,项目成本越低。好了,能最有效的检测PHP代码中的错误的工具是PHPUnit,一个开发源代码的框架,它在你不在的时候...

PHPUnit袖珍指南.doc

  • 2012年04月03日 11:19
  • 869KB
  • 下载

PHPUnit袖珍指南-第四章 安装PHPUnit

第4章 安装PHPUnit PHPUnit可以通过PHP扩展和程序库(PEAE)获得。PEAR是可重用PHP组件的框架和分发系统。安装PHPUnit可以通过PEAR安装程序命令获得:   pea...
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:PHPUnit袖珍指南 第八章 未完成测试
举报原因:
原因补充:

(最多只允许输入30个字)