Unit Testing New Code vs. Existing Code

Testing the Greenfield code is far easier than testing the Brownfield code or legacy code. The main reason is that during the code of Brownfield application or legacy code we don’t consider about testability. So the class structure in the systems is often more tightly coupled than those codes that developed with tests. But it is not also true that “practicing test first development in Brownfield environment.” By following a great technique many developers find value. The technique is before fixing bug we create a test that fails. This fails test demonstrate that the bug is actually exists there. Then we fix the bug and run the test. The test passes. So our workflow becomes much simpler. Create a failing test; make the test pass. This workflow work well in Brownfield applications as it does in Greenfield application.

Md. Mojammel Haque
Currently working as Lead Team (Application Architecture) at Raven Systems Ltd.

Passion for software development especially agile practices such as TDD & BDD with in depth knowledge of OOP, DDD, CQRS, ES, GoF, SOLID and PoEAA.

Over 6 years of software development experience ASP.NET. Has the ability to understand and transform complex business requirements into software ensuring applications are delivered on time.

Also experience in non Microsoft .NET technologies such as Dapper.Net, Subversion, Structure Map & AngularJs.

309 Total Views 1 Views Today
Unit Testing
Unit Testing Frameworks

Leave a Comment

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>