About Miško Hevery

… works as an Agile Coach at Google where he is responsible for coaching Googlers to maintain the high level of automated testing culture. This allows Google to do frequent releases of its web applications with consistent high quality. Previously he worked at Adobe, Sun Microsystems, Intel, and Xerox (to name a few), where he became an expert in building web applications in web related technologies such as Java, JavaScript, Flex and ActionScript. He is very involved in Open Source community and an author of several open source projects. Recently his interest in Test-Driven-Development turned into Testability Explorer (http://code.google.com/p/testability-explorer) and JsTestDriver (http://code.google.com/p/js-test-driver) with which he hopes to change the testing culture of the open source community.

Open-Source Projects

Talks

2009, May 7th – GeeCON, Poland, Krakow - Influencing Software Developers Towards More Testable Code Base & More Tests
2009, April 1st – Karlova Universita Praha – Test Driven Development
2009, March 27th – ThoughWorks – Looking for Red Flags [pics]
2009, February 20th – ZillionTV – Theory of testing
2008, November 11th – Loopt – Inheritance, Polymorphism, and Testing – Review
2008, November 4th – Loopt – Test Driven Development
2008, October 28 - Loopt - Perils of Global State
2008, October 23-24 – GTAC – How to think about the new operator
2008, October 21-22 – OOPSLA – Testability Explorer Demonstration (PDF)
2008, October 14 – Loopt – How to Write Testable Code
2008, June – Goerlitz University – One week seminar on Test-Driven-Design; Dependency Injection; Mocking
2008, May -Java One – Practical Application of Static Java Analysis; Using byte code analysis to gain better visibility into project and improve code quality.
2007, October – Goerlitz University – Life of an Agile Project
2007, October – Prague Charles University – Life of an Agile Project

Publications

2008, Aug – Changing Developer Behavior – Part I
2008, Sep – Changing Developer Behavior – Part II

Contact

misko at hevery dot com

NOTE: This is my personal blog. The views expressed on these pages are mine alone and not those of my employer.

29 Comments

29 responses so far ↓

Breaking the Law of Demeter is Like Looking for a Needle in the Haystack | Miško Hevery // Jul 20, 2008 at 8:51 am

[...] About Miško Hevery [...]
How to Write 3v1L, Untestable Code | Miško Hevery // Jul 24, 2008 at 2:13 pm

[...] About Miško Hevery [...]
南郭之家 » Blog Archive » Writing Testable Code // Aug 10, 2008 at 7:12 pm

[...] by Miško Hevery [...]
Where Have All the Singletons Gone? | Miško Hevery // Aug 21, 2008 at 11:50 am

[...] About Miško Hevery [...]
Where Have All the Singletons Gone? | Software Testing Blog // Aug 21, 2008 at 4:15 pm

[...] Miško HeveryIn Singletons are Pathological Liars we discussed the problems of having singletons in your code. [...]
Root Cause of Singletons | Software Testing Blog // Aug 27, 2008 at 8:12 pm

[...] Cause of Singletons by Miško HeverySince I hit gotten lots of love/hate accumulation on the Singletons are Pathological Liars and Where [...]
Writing testable code is writing high quality code / Iconara // Sep 9, 2008 at 3:24 am

[...] Google Testing Blog, mostly written by Miško Hevery, is amongst the most brilliant things I’ve read on software engineering. If you’re not [...]
Changing Developer Behaviour, Part II | Miško Hevery // Sep 10, 2008 at 8:38 am

[...] About Miško Hevery [...]
Application Wiring on Auto-Pilot | Miško Hevery // Sep 24, 2008 at 10:35 am

[...] About Miško Hevery [...]
b.l.o.g. » Blog Archive » Some ressources about Testing // Oct 1, 2008 at 8:17 am

[...] read one of the newer articles and digged deeper into the blog of its author Miško Hevery. He writes about Singletons: Singletons are Pathological Liars. Quite a rant calling Singleton an [...]
Testability Explorer: Measuring Testability | Miško Hevery // Oct 25, 2008 at 11:17 am

[...] About Miško Hevery [...]
Clean Code Talks - Unit Testing | Miško Hevery // Nov 5, 2008 at 10:15 am

[...] About Miško Hevery [...]
The Clean Code Talks « Quero ser Ágil // Nov 11, 2008 at 4:27 am

[...] 11, 2008 por Rafael Mueller Achei duas apresentações que Miško Hevery fez no google (onde ele trabalha), estão no youtube com o título The Clean Code Talks (nome [...]
Clean Code Talks - Dependency Injection | Miško Hevery // Nov 11, 2008 at 4:03 pm

[...] About Miško Hevery [...]
Clean Code Talks - Global State and Singletons | Miško Hevery // Nov 21, 2008 at 12:14 pm

[...] About Miško Hevery [...]
Guide to Writing Testable Code | Miško Hevery // Nov 26, 2008 at 11:01 am

[...] About Miško Hevery [...]
Linking to Miško’s, Russ’ and my Testability Guide at JAW Speak // Nov 29, 2008 at 3:26 pm

[...] had the great pleasure of collaborating with Miško Hevery and Russ Rufer in creating the Guide for Writing Testable Code. Please feel free to check it out, [...]
Clean Code Talks - Inheritance, Polymorphism, & Testing | Miško Hevery // Dec 8, 2008 at 11:50 am

[...] About Miško Hevery [...]
Static Methods are Death to Testability // Dec 15, 2008 at 7:44 am

[...] About Miško Hevery [...]
Juan Angel // Dec 18, 2008 at 12:54 am

Dear Misko,First of all, I congrulate you for you work in software testing.I have read you last article “Static Methods are Death to Testability”. I think that I have understood why you say static methods should not be used.However, I disagree with you.From the testing view point, static methods dependencies can be wired if the apropiate testing tool is used. In the project where I work, we use the tool Cantata++, from IPL, for unit testing and for measuring coverage. Cantata++ allows you to create mocks for every method or even functions (procedural programming). For instance, you can mock the malloc() function, if you want malloc() to return NULL.I look forward to hearing from you.Best regards, Juan Angel
misko // Dec 18, 2008 at 12:58 am

Many of you are writing that there are ways through magic of many tools to test static methods. Yes, I know that those tools exists. From my point of view these tools are bandage for bad design. The spirit of unit-testing is to test things in isolation by wiring the objects differently. There is nothing to wire with static methods. Hence they don’t lend themselves well to unit-testing. You should be able to do al of your testings with zero tools.
Happy New Year - 2009 // Jan 4, 2009 at 9:26 am

[...] About Miško Hevery [...]
Interfacing with hard-to-test third-party code // Jan 4, 2009 at 12:22 pm

[...] About Miško Hevery [...]
Testability - re-discovering what we learned and forgot about software development // Jan 13, 2009 at 4:59 pm

[...] About Miško Hevery [...]
When to use Dependency InjectionS // Jan 14, 2009 at 11:38 am

[...] About Miško Hevery [...]
Unit testing | bishop-it.ru // Feb 7, 2009 at 9:12 am

[...] видео с недавнего Google Tech Talks. Miško Hevery рассказывает про то, какие виды автоматизированного [...]
Helltime for April 3 « I Built His Cage // Apr 3, 2009 at 2:57 pm

[...] out Helltime is Misko Hevery’s expoundment of Collaborators versus Factories. Essentially, factories create all your [...]
Helltime for April 17 « I Built His Cage // Apr 18, 2009 at 7:57 pm

[...] Misko Hevery also hits on a work-related nerve of mine, stating that “there is a myth out there that creating objects is expensive.” This myth is such a fact at work that “object design”, if you can call it that, is heavily driven by the result sets of a stored procedure, the needs of a UI page, or caching opportunities. This, in turn, is due to the performance demands we place on multiple JVMs running on multiple servers. [...]
Yet Another JavaScript Testing Framework // May 22, 2009 at 3:34 pm

[...] About Miško Hevery [...]