Follow bbv
Recent Comments
- Carl Cubillas on Prism vs. Caliburn.Micro
- Katia on The Chance that 42 is the Meaning of Life
- Urs Enzler on The next 2 steps on bbv’s Agile journey
- Thomas Weingartner on The next 2 steps on bbv’s Agile journey
- Marco Amendola on Caliburn.Micro – Introduction
Category Archives: Test Driven Development
In my current project, we do a lot of refactoring to keep the source code as simple and understandable as possible. This involves a lot of renaming of classes and moving classes between namespaces to structure the code in a … Continue reading
Posted in .NET, Clean Code, Test Driven Development
Tagged Clean Code, NDepend, Unit-Test
Leave a comment
This is the presentation I gave at the .Net System Event by bbv Software Services AG in Lucerne in June 2012:
Die Fähigkeit, qualitativ hochstehende Software zu entwickeln und dabei stetig auf sich ändernde Anforderungen reagieren zu können, zeichnet ein gutes Software-Entwicklungsteam aus. Agile Methoden wie Scrum oder Test Driven Development haben genau dies zum Ziel. Continuous Integration ist ein Teil … Continue reading
Posted in Agile, Announcement, Marketing, Test Driven Development
Leave a comment
If you are familiar with hamcrest and JUnit the time will come when you have the need to create your own matchers. Creating your own matcher can be as simple as useful. One reason for creating your own matcher could … Continue reading
Posted in Java, Test Driven Development, Testing
Tagged hamcrest, java, junit, matcher, TDD
Leave a comment
When software projects grow both in age and size the developers often struggle with the structure of the code. It gets more and more difficult to find the class you have to change for a new requirement. In this post, … Continue reading
Posted in .NET, Agile, Architecture, Clean Code, Test Driven Development
Tagged Architecture, Clean Code, TDD
Leave a comment
In the last two years I gave over a dozen courses and presentations about test driven development (TDD). One question, I get asked almost every time, is how to refactor code while keeping up the TDD rules: write only production … Continue reading
