Comments for Web Mozarts

Comment on Creating mobile symfony sites by Linkdump #49: Symfonia symfony 1.x / Symfony2. « Tomasz Kowalczyk

Linkdump #49: Symfonia symfony 1.x / Symfony2. « Tomasz Kowalczyk — Sun, 10 Jul 2011 10:30:26 +0000

[...] Creating mobile symfony sites. Tworzenie stron dla urządzeń mobilnych w symfony. [...]

Comment on Why sfContext::getInstance() Is Bad by Relaying Doctrine events to symfony « Destroy every zig!

Relaying Doctrine events to symfony « Destroy every zig! — Wed, 20 Apr 2011 07:53:33 +0000

[...] If you need to relay your Doctrine events to symfony, you might get tempted to create a dependency to sfContext in your models. As we all know (right?) this is a path straight down to hell. [...]

Comment on Why sfContext::getInstance() Is Bad by GizmoLA.com

GizmoLA.com — Tue, 18 Jan 2011 22:26:49 +0000

Load the Url symfony helper in a model or form class…

I’m doing some symfony work and needed to use the Url helper in a form class to return an error message that included a link. I would consider this one of those exceptions where you really need to be able to have markup in a class rather than in a tem…

Comment on Creating mobile symfony sites by Les liens de la semaine | Le Cri Des Geeks

Les liens de la semaine | Le Cri Des Geeks — Fri, 10 Sep 2010 13:01:27 +0000

[...] [WebDev::Symfony] Créer des sites pour mobile avec symfony, voir ça aussi [...]

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 [...]