Test Culture  : the 101 unit test guide for busy managers.

So you want to install a test culture in your team/department ?

Maybe you’ve already done a great deal  by appointing a Test Supervisor that checks every aspect of the finished product. That’s terrific. Congratulations.

But there are still bugs ?  Your team is telling you that this little change you asked took the all system down ? How comes ?

Unit testing rocks

Welcome to this series of article on unit testing and why it rocks.

Most of all : unit testing is greeeaaaat. Not only for the geeks in the dev team but for you too as a manager.

First : have you heard of unit testing ? I mean the real ones, not just the kind when a dev says  “Yeah, I’ve clicked the button and no exceptions happened , it works guys, let’s go  to prod ! ”

I’m talking about real Automated Unit Testing that implements the specifications and sometimes redefines them in more concrete way (whatever agile of waterfall you are).

As a manager you want to be sure that your team is not building a soft that has absolutely no link with what your client wants. And it all starts with automated unit testing. The foundation on which to build your code, and all the software.


Limited budget you fool !

I can hear some of you grumbling behind their desk :

– “Come one you clown, it’s the real world out there, and my budget is shrinking years after years ! I don’t have budget to feed extra testers !”


– “Great, my team is going to code twice : one for the tests, the other for the code. Ain’t you mad ?”


– “We already got this ! Stop bothering us. But ok :  from time to time, we find bugs as big as the Eiffel Tower. But still, we have unit tests. What more can we do?”


– “Unit testing is already part of the procedure. Of course we don’t have time to maintain them. That’s obvious. So we don’t run them any more. But they are here !”

You’ll see that all those worries will disappear when you’ll have a real view of what unit testing is.

The series

I’m not here to sell you some new  methods actually. I’m not even suggesting to test everything. And I swear your team won’t need twice as time as needed.

This series of 12 articles will show you real world examples and arguments why unit testing rocks.

Each episode has recommendations, exercises, success stories and notes for devs too.

Ask questions and debate here if you’r not convinced yet (in French or English, I’ll translate if needed).

Episodes list  :

  1. Introduction
  2. I Need Buzzwords
  3. Can You Unit Test Everything ?
  4. 336 Combinations Manualy Tested, 2 Days, 2 People. The Nightmare.
  5. Hudson We Got A Problem
  6. Good Unit Testing Is Better Than Excellent Specifications
  7. Tests Are Broken ? Can We Just Cut Them Out For Latter ?
  8. « If  You Don’t Have Unit Tests, You Are Not Refactoring, You Are Just Moving Shit Around »
  9. Covering All The Code Is Not Enough
  10. The Art Of Unit Testing Is Knowing When To Stop.
  11. The Big Question : How Much ?
  12. Conclusion – Cheat Sheet



  • Subscribe to the RSS feed, or by mail, to receive all the 12 episodes for free directly in your super-web-genious-inbox when they are released.

For the developers out there

Please, feel free to hand this to your manager and to add your own comment. I might be a little too vague sometimes, correct me if needed. The goal is to convince managers to let us code unit tests. The stacks are high. 

By the way :  if you are a dev and you ‘ve never heard of the wonderful advantages of working with JUnit, you should worry NOW !

Jean-Baptiste Rieu
Mobile/BackEnd Software Engineer & Scrum Master
Applications should be robust and extremely well designed. Whatever the domain and the medium.

I fight for that with the help of talented people. I want to help you in this mission too.

Fervent supporter of unit testing, constant refactoring, agile approach and good user experience design from scratch. I also believe in the well conceived truly RESTful APIs.

Love to learn through real projects. Invent new ones if necessary.

Also invested in business and culture comparison between France and Korea (my wife’s country).
Currently learning Korean.

저는 프랑스 소프트웨어 엔지니어이며 사업에 관심이 많습니다. 창조성과 팀워크의 개선을 항상 바라고있습니다. 영어를 능숙하게 구사하며 한국어는 배우는 중입니다.

소프트웨어(새로운 Agile 기법이나 단순 폭포수 접근법을 이용한) 개발에 대한 도움이 필요하다면 저에게 알려주세요.

제 부인의 나라인 한국을 사랑합니다. 한국 관련 사업의 기회와 문화를 접하고 싶습니다.

한국이나 프랑스로의 수출을 구상 중이시라면 저에게 알려주세요.
프랑스 문화와 비지니스에 대한 저의 사견을 제공해드릴 수도 있습니다.

* Organizational Specialties : SCRUM, Visual boards, JIRA virtual work, Serious Games and brainstorming sessions, Lean and the Toyota Way
* Dev Specialties: iOS front-end, backend API and server logic (mainly in Java)
Unit Testing, Continuous Integration. Agile Approach.
User Experience and Product Improvement (via A/B testing, analytics and user interviews)
Eclipse RCP, JFreeChart, OpenGL, Data Visualizations.
* Interested in : Startup and entrepreneurial adventures, Big Data Science/Mining, Drone development in urban environment, connected cars, augmented reality for tourism and culture, in flight entertainment, high frequency operations and highly available and scalable architectures in general.

Be Sociable, Share!

5 Responses to “Test Culture Episode 1. The 101 Unit Testing Guide For Busy Managers.”

  1. Waiting for the episodes !!! :)

  2. Hey good idea, it’ll check it out. I’m late, I know…

  3. […] ซีรีย์บทความเกี่ยวกับ Unit Test คนเขียนบทความยังเขียนไม่ครบ ณ ตอนนี้เขียนไปแล้ว 7 ตอนจาก 12 ตอน แต่ละบทความไม่ยาวมาก แล้วก็เขียนด้วยภาษาพูด ทำให้อ่านง่ายด้วย […]

  4. […] are 10 reasons why you, as a manager,  should care about unit tests. It’s a summary of this series of 12 articleson unit tests for […]

  5. […] doit considérer sérieusement les tests unitaires. C’est le dernier article d’une série de 12 sur les tests unitaires expliqués aux […]

Leave a Reply

Seo PackagesWhat is seoseo tips