blocks|key|1557099|text|你应该看看PHPUnit，它看起来很像nUnit。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1557100|entityMap|0|LINK|mutability|MUTABLE|url|http://www.phpunit.de/^0|5|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You should look into <a href="http://www.phpunit.de/" rel="nofollow noreferrer">PHPUnit</a>, it looks pretty much like nUnit.

blocks|key|1772414|text|PHPUnit是一个标准，但有时它也是压倒性的，所以如果你觉得它太复杂了，请查看phpt开始吧。在其中编写测试非常非常容易。对任何程序员来说都不需要动脑筋。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1772415|回答你的TDD问题--我不确定TDD是否在PHP空间中使用了widley。我可以看到快速应用程序开发和TDD有些冲突(严格地说是IMHO)。TDD要求您对构建的内容有一个完整的了解，您需要预先编写测试，然后实现代码以使测试通过。|1772416|例如，我们所做的是，当我们完成时编写大量的测试。这并不总是最好的方法，因为您有时会得到通过的虚假测试，但这些测试并不是真正有用的，但至少它是您可以扩展的东西。在内部，我们继续进行测试，基本上为我们发现的每个bug编写一个测试。这就是它变得更加坚实的原因。|1772417|entityMap|0|LINK|mutability|MUTABLE|url|http://qa.php.net/write-test.php^0|14|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

PHPUnit is a standard, but it's sometimes also overwhelming, so if you find it too complex, check out <a href="http://qa.php.net/write-test.php" rel="noreferrer">phpt</a> to get you started. It's very, very easy to write tests in it. A no brainer for any programmer.

And to answer your TDD question - I am not sure if TDD is widley used in the PHP space. I can see that rapid application development and TDD somewhat clash (strictly IMHO). TDD requires you to have the complete picture of what you build and you write your tests up front and then implement the code to make the test pass.

So for example what we do instead, is to write a lot of tests when we are done. This is not always the best approach because you sometimes end up with bogus tests that pass, but are not really useful but at least it's something you can expand on. Internally we continue on tests and basically write a test for each bug we find. This is how it becomes more solid.

blocks|key|1557297|text|我个人更喜欢SimpleTest。有一个命令行测试运行器和基于web的测试运行器，甚至还有一个Eclipse可以让您从plugin本身运行单元测试。我发现Zend+to+PHPUnit连接很难使用，特别是在使用调试器时。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1557298|我们内部使用SimpleTest的方式是使用我们自己编写的continuous+integration脚本。每次我们将一个特性签入到SVN时，我们都会包含单元测试。大约每隔一个小时，CI脚本就会运行一次，并调用一个运行所有单元测试的命令行PHP脚本。如果有中断，我会收到一封电子邮件。这是一个很好的方法来减少我们系统中的bug。|1557299|但是，您可以很容易地使用诸如Phing之类的工具来自动运行测试，无论是在cron作业上还是在SVN+check-in钩子上。|1557300|事实上，如果你想直接联系我寻求进一步的帮助，你可以通过我的个人资料来联系我。我很乐意帮你。|1557301|entityMap|0|LINK|mutability|MUTABLE|url|http://simpletest.sourceforge.net/en/extension_eclipse.html|1|http://www.martinfowler.com/articles/continuousIntegration.html|2|http://phing.info/trac/^0|1N|6|0|0|T|M|1|0|E|5|2|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|H|3|I|5|6|7|17|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]|T|$5|M|N|O|C|$P|U]]]]

I personally prefer SimpleTest. There is a command line test runner and web-based test runner, and there is even an Eclipse <a href="http://simpletest.sourceforge.net/en/extension_eclipse.html" rel="nofollow noreferrer">plugin</a> to let you run unit tests from the IDE itself. I found the Zend to PHPUnit connection much harder to get working, especially with the debugger.

The way we use SimpleTest in-house is with a <a href="http://www.martinfowler.com/articles/continuousIntegration.html" rel="nofollow noreferrer">continuous integration</a> script that we wrote ourselves. Every time we check in a feature to SVN we include the unit tests. Every hour or so, the CI script runs and calls a command line PHP script that runs all of our unit tests. If any break, I get an email. It's been a great way to reduce bugs in our systems.

However, you can just as easily use something like <a href="http://phing.info/trac/" rel="nofollow noreferrer">Phing</a> to run your tests automatically, either on a cron job or with an SVN check-in hook.

In fact, if you want to contact me directly for further help, you can get to me through my profile info on SO. I'd love to help you out.

blocks|key|1772572|text|我强烈推荐Test-Driven+Development+by+Kent+Beck+(ISBN-10:+0321146530)。它不是专门为PHP编写的，但是其中的概念已经存在，并且可以很容易地转换为PHP。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1772573|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0321146530^0|5|1M|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I highly recommend <a href="https://rads.stackoverflow.com/amzn/click/com/0321146530" rel="noreferrer" rel="nofollow noreferrer">Test-Driven Development by Kent Beck (ISBN-10: 0321146530)</a>. It wasn't written specifically for PHP, but the concepts are there and should be easily translatable to PHP.

blocks|key|1557392|text|你应该看看的另一个现代工具是Codeception。它比PHPUnit简单得多，并结合了场景驱动的方法，这对于从测试生成文档非常有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1557393|entityMap|0|LINK|mutability|MUTABLE|url|http://codeception.com/02-15-2012/unit-testing.html^0|E|B|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Another modern tool you should look it is <a href="http://codeception.com/02-15-2012/unit-testing.html" rel="nofollow">Codeception</a>. It is much simplier then PHPUnit and incorporates scenario-driven approach, which is quite useful for generating documentation from tests.

blocks|key|1557474|text|测试驱动开发是一种总是在编写代码之前编写测试的方法。你应该先学习PHPUNIT，然后才能开始TDD开发。然后，在创建函数时，您应该始终考虑函数是如何失败的，并在phpunit中编写测试用例，最后，您应该编写代码以通过测试。它将是一种新的方法，所以它在一开始会有点困难，但一旦你习惯了它，你会发现它非常有用，特别是在开发错误和编码风格之后。你可以通过这个Step+By+Step指南来理解这个概念。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1557475|永远记住，如果测试是在开发之后编写的，那么它们是无用的。因此，如果您正在考虑编写unit+tesst，那么TDD是必须的|1557476|entityMap|0|LINK|mutability|MUTABLE|url|https://phpunit.de/|1|http://vihasverma.blogspot.com/^0|W|7|0|4W|C|1|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Test driven development is an approach where tests are always written before code. 
You should learn to <a href="https://phpunit.de/" rel="nofollow noreferrer">PHPUNIT</a> first in order to start TDD Development. Then while making your function you should always think how function can fail and write test case in phpunit and in the end you should write code in order to pass your test. Its will be a new approach so it will be little difficult in the beginning but once you get use to it, you will find it very useful specially for after development bugs and coding style. You can go through this <a href="http://vihasverma.blogspot.com/" rel="nofollow noreferrer">Step By Step</a> guide for understanding this concept. 

Always Remember if test are written after development they are useless. So TDD is must if you are thinking to write unit tesst

I am a web-developer working in PHP. I have some limited experience with using Test Driven Development in C# desktop applications. In that case we used nUnit for the unit testing framework.

I would like to start using TDD in new projects but I'm really not sure where to begin. 

What recommendations do you have for a PHP-based unit testing framework and what are some good resources for someone who is pretty new to the TDD concept?

Test Driven Development in PHP

单元测试

调试器

Eclipse

我是一个网站开发人员在PHP中工作。我在C#桌面应用程序中使用测试驱动开发的经验有限。在这种情况下，我们使用nUnit作为单元测试框架。我想开始在新项目中使用TDD，但我真的不确定从哪里开始。对于基于PHP的单元测试框架，您有什么建议?对于刚刚接触TDD概念的人，有哪些好的参考资料？

问PHP中的测试驱动开发
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问PHP中的测试驱动开发EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问PHP中的测试驱动开发
EN