Comments for Web Mozarts

Comment on Why sfContext::getInstance() Is Bad by Utiliser l’objet user dans un formuaire symfony » Fisti

Utiliser l’objet user dans un formuaire symfony » Fisti — Mon, 30 Aug 2010 03:06:26 +0000

[...] en contre-exemple, car j’ai pu souvent la trouver sur certains blogs ou forums, à tort (ici un très bon article, en anglais, qui explique [...]

Comment on Why Not To Want 100% Code Coverage by • Wie hoch sollte die Testabdeckung meines Codes sein? | test.ical.ly

• Wie hoch sollte die Testabdeckung meines Codes sein? | test.ical.ly — Mon, 22 Mar 2010 05:00:48 +0000

[...] ein paar Tagen hat Bernhard in seinem Blog einen weiteren sehr anschaulichen Artikel zum Thema Testabdeckung geschrieben. Er liefert darin eine schlüssige Begründung warum eine hundertprozentige [...]

Comment on Why Not To Want 100% Code Coverage by Christian

Christian — Mon, 15 Mar 2010 19:43:04 +0000

Very interesting read! Thanks a lot for elaborating on this topic.

Comment on Why Not To Want 100% Code Coverage by Jordi Boggiano

Jordi Boggiano — Mon, 15 Mar 2010 16:30:39 +0000

One thing I like as a guideline is to always test for the working expected scenario, and also try to test for the error condition, and ensure the code breaks properly. The definition of properly is obviously context dependent. Sometimes an exception is good, sometimes returning null is better.

It’s important to test for potential failures, because eventually a non-expected input will get through and that day you’d rather have your code fail gracefully than explode in the user’s face or worse cause a security breach.

Comment on Why Not To Want 100% Code Coverage by uberVU - social comments

uberVU - social comments — Mon, 15 Mar 2010 14:29:38 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by stephenmelrose: RT @webmozart: New blog post: Why Not To Want 100% Code Coverage http://bit.ly/cL40SS #symfony #testing…

Comment on Writing Efficient Tests by Karopapier, symfony und der ganze Rest » Blog Archive » Starting to get addicted to unit testing…

Mon, 15 Mar 2010 09:59:33 +0000

[...] paying more attention to unit testing and writing tests in my symfony apps. But not until this awesome post from Bernhard Schussek, I really understood how you can make your testing life easier and get tests done better, faster [...]

Comment on Writing Efficient Tests by Romain

Romain — Fri, 12 Mar 2010 14:17:34 +0000

This is an excellent article. Developers knowing what is a unit test is rare nowadays…

Comment on Writing Efficient Tests by uberVU - social comments

uberVU - social comments — Thu, 11 Mar 2010 21:53:18 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by webmozart: New blog post published. http://bit.ly/c4cxdE #efficient #testing #symfony…

Comment on Writing Efficient Tests by Matthieu

Matthieu — Thu, 11 Mar 2010 21:19:35 +0000

@NiKo Apart from the initial part (Filling the database with all the test data from YAML files) that I do just once (or each time I change my fixtures), it doesn’t seem to me that using transactions is slow.
Anyway I guess it is faster than reloading the test data.

Comment on Writing Efficient Tests by Christian

Christian — Thu, 11 Mar 2010 21:12:28 +0000

Very interesting article! I think I can use a lot of this even when I’m testing with PHPUnit.

But I wonder about Lime2. So far it has been mentioned that Symfony 2 is going to use PHPUnit, symfony 1.4 is not supposed to switch base technologies, Lime2 development became low priority, ..
What is the purpose and goal of Lime2? I mean I do think your ideas so far have been inspiring, but what will be the outcome?
Shouldn’t there be a Lime2 website finally?