Dev and Test, Sitting in a Tree: K-I-S-S-I-N-G

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

When I was a kid cars didn’t have seat belts in the back seat. We used to fly to and fro all over whenever the car took a turn. These days my kids shriek with horror if we forget to buckle them up and the car starts moving. That’s the mindset.

Some time ago I led a code retreat event. In the first session, I asked the teams to try and build a simulation of Conways’ Game of Life. Immediately they started coding the simulation.

That was odd.

You see, I usually don’t write any code before I have a test ready to run it. What’s the point? I like it when one key press runs all the tests. It makes me feel safe. It’s the same as when I’m getting into my car I wear the seat belt.

When the people at the session were done with coding, they wanted to see if it works. So they wrote a short main and started debugging.

“They wanted to see if it works.” I’m familiar with this. I also used to write code and then just wanted to make sure it works. These days I have a concrete objective in front of me: a test that should pass.

When I started TDDing (Test Driven Dedign/Development) it was strange. I wanted to write code and I felt messing around with the tests was a waste of time. But as I did more and more of it something changed. It made me feel safe.

On the second session of the aforementioned Code Retreat I asked the people to do the same exercise, but this time the test first. They didn’t understand. So I showed them: I take a blank project and write a test. I start with the assert statement. I use in the assert a Class that I still don’t have and also probably a Method that I don’t have. Then I write the code in the test that comes before it. Then I use the IDE to generate the missing classes and methods. Enlightenment!

In the same way that you don’t build a house without scaffolding, you don’t write code without tests. When you start with the tests, you write code that is more testable. When you build a car, you build it so you could have a proper place to anchor the seat belt. It comes together.

(And it works as well with Legacy code. Read Michael Feather’s Working Effectively with Legacy Code. We will also write about it here.)

It is true for a single developer doing unit tests and it is true for QA people running System Tests: Testing and Development comes together.

Dev and Test
sitting in a tree,
K-I-S-S-I-N-G.
First comes learning,
then comes practice
then comes software in a baby carriage… 
:-O

Categories:

Tags:

POPM
LeSS
Scrum Master
Manage Budget Creation
Daily Scrum
Self-organization
Nexus and Kanban
Engineering Practices
lean agile change management
Nexus and SAFe
Effective Agile Retrospectives
Agile Testing Practices
speed @ scale
Development Value Streams
SPC
Agile in the Enterprise
Kaizen
Quality Assurance
Systems Thinking
Amdocs
Large Scale Scrum
Program Increment
speed at scale
Risk-aware Product Development
ATDD vs. BDD
Lean Agile Leadership
Software Development
Introduction to ATDD
Nexus
Lean and Agile Principles and Practices
Lean Agile
Limiting Work in Progress
Built-In Quality
Agile Development
Managing Projects
Achieve Business Agility
Scrum Primer
Agile Marketing
Kanban Kickstart Example
RTE Role
Lean Agile Basics
Acceptance Test-Driven Development
Webinar
Agile Contracts Best Practices
Agile
Software Development Estimation
Jira Cloud
Continuous Deployment
Release Train Engineer
Lean Risk Management
Agile Program
GanttBan
Reading List
Agile Games
WIP
Advanced Roadmaps
Scrum.org
Elastic Leadership
Professional Scrum with Kanban
SAFe
Sprint Iteration
Product Management
Kanban 101
Applying Agile Methodology
Operational Value Stream
Business Agility
IT Operations
Games and Exercises
Jira Plans
Test Driven Development
Lean Software Development
Scrum Guide
Artificial Intelligence
Product Ownership
Scrum Master Role
The Agile Coach
TDD
AI Artificial Intelligence
Pomodoro Technique
What Is Kanban
Lean Budgeting
Value Streams
Story Slicing
Risk Management in Kanban
Professional Scrum Product Owner
PI Objectives
ARTs
Agile Assembly Architecture
Legacy Code
Nexus Integration Team
Atlaassian
Planning
Presentation
Video
Agile Project Management
Jira
Agile Mindset
Agile Risk Management
Releases Using Lean
Code
Kanban Game
Scaled Agile Framework
DevOps
ROI
NIT
Lean Agile Organization
Agile and DevOps Journey
SAFe DevOps
The Kanban Method
Hybrid Work
QA
Scrum
System Archetypes
Enterprise DevOps
ATDD
Scrum With Kanban
Agile Exercises
Scrum and XP
Professional Scrum Master
Sprint Retrospectives
Kanban
Rapid RTC
Implementation of Lean and Agile
Agile for Embedded Systems
RSA
Scrum Values
Slides
Continuous Planning
Entrepreneurial Operating System®
PI Planning
System Integration Environments
Agile Product Ownership
Perfection Game
Coaching Agile Teams
Agile Project
Frameworks
A Kanban System for Software Engineering
EOS®
Principles of Lean-Agile Leadership
Legacy Enterprise
Agile Product Development
Lean-Agile Budgeting
Agile India
Managing Risk on Agile Projects
Change Management
Agile Community
LAB
Spotify
Agile Release Planning
Agile Games and Exercises
Introduction to Test Driven Development
Accelerate Value Delivery At Scale
Process Improvement
Agile Techniques
Agility
Certified SAFe
Nexus vs SAFe
BDD
AgileSparks
Continuous Integration
Lean-Agile Software Development
Covid19
System Team
Agile Outsourcing
Risk Management on Agile Projects
Kanban Basics
Iterative Incremental Development
Continuous Delivery
An Appreciative Retrospective
ScrumMaster Tales
Agile Release Management
Agile Delivery
Lean Agile Management
SAFe Release Planning
Portfolio for Jira
Agile Basics
ALM Tools
Lean Startup
Kaizen Workshop
Agile Israel Events
Sprint Planning
Tips
Lean and Agile Techniques
Continuous Improvement
AgileSparks
Logo
Enable registration in settings - general

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

academy@agilesparks.com

WELCOME

to our new website

WELCOME

to our new website

This website uses Cookies to provide a better experience
Shopping cart