We write tests and code for other people. Tests are code too, and both should be clean.

As a clean code fanatic, I see it as a personal mission to go around preaching how powerful clean code is. But unfortunately, it seems that test code is not considered "real code", and therefore is not considered "dirty".

In this session, we'll talk about concrete examples of anti-patterns in tests, and how to clean them up. We'll see how clean code principles apply directly to tests. And that's true for all tests - from unit to end-to-end, and regardless of who writes them - developers and testers. Gil Zilberfeld We'll see those in action.

"Clean code looks like it was written by someone who cares.", said Michael Feathers. Test code may even be more important to write cleanly for that reason.

Requirements: 

• Some unit testing experience.
• Basic Java, JavaScript and C# knowledge.
• It is a workshop so there are going to be exercises. Examples can be downloaded from a link that I will give out before (to be published) and during the workshop. It will be in Java, JavaScript and C#.
• The attendees will need to download the examples, and have an IDE ready.

Level: Intermediate

Timetable: 11:00 a 13:00 GMT-3

Important: if you signed up to attend and later on cannot make it, we would be grateful if you could cancel the registration to give someone in the waitlist a chance to attend.

English activity WITHOUT simultaneous translation into Spanish.