Showing posts with label TDD. Show all posts
Showing posts with label TDD. Show all posts

Wednesday, October 2, 2013

30 Days of TDD – Day Nine – Refactoring Basics

As time goes on in any software development project you'll no doubt find inefficiencies in your code that you would like to remove. Other times you'll receive new requirements that are going to necessitate large scale changes in your existing code. And you will still occasionally find code that you've written in the past that will make you ask "What was I thinking when I did that?!" When these situations arrive, it's time to look at refactoring your code.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blogtwitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.


This article is related to

Architect,Intermediate,Articles,Computer Tutorials, Telerik, TDD,Refactoring Basics

30 Days of TDD – Day Ten – More Refactoring and NUnit Features

In the last post I showed you how from time to time it is necessary to change our code to enhance readability, make maintenance easier or to optimize the codes performance. This practice is called "Refactoring." Normally making these kinds of changes can be a nerve-wracking experience for developers as they can't be certain that their changes aren't breaking something else. However, having a suite of unit tests the exercise your business code enables you to refactor your code without worry; as long as your tests pass you know that your code still satisfies your business needs. In addition to our code, sometimes our unit tests themselves need some refactoring. This post explains how to refactor your unit tests and demonstrates a few NUnit features that will help us with this endeavor.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blogtwitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.


This article is related to

Architect,Intermediate,Articles,Computer Tutorials, Telerik, NUnit, TDD

Tuesday, September 24, 2013

30 Days of TDD: Day Two – A Review of Object Oriented Principals

In today's post I'll be doing a quick review of principals of Object Oriented Programming (OOP). This post will help frame future posts in this series by ensuring that we are all on the same page in terms of our understanding of software development. Even if you are seasoned developer I recommend that you at least read the section on Polymorphism and Interfaces as these topics are widely misunderstood and are crucial to building good TDD practices.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blogtwitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.


This article is related to

Architect,Intermediate,Articles,Computer Tutorials, Telerik, TDD,OOP

30 Days of TDD: Day Three – Your First Test

In this post I will introduce you to JustCode and the NUnit testing framework. I'll also demonstrate the basic TDD workflow from introduction of the first requirement all the way through to writing your first test. At the end of this post you will have a test based on a given requirement. In the next post we will work through the rest of the workflow and make the test pass.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blogtwitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.


This article is related to

Architect,Intermediate,Articles,Computer Tutorials, Telerik, TDD

30 Days of TDD: Day Four – Making Your First Test Pass

In the previous post I discussed the tools I will be using in this series; Visual Studio 2013 Preview as my development environment, NUnit as my unit testing framework and JustCode as my test runner. I also introduced a requirement and wrote my first test to capture that basics of that requirement. In this post I'll demonstrate one of the most important concepts about TDD by writing just enough code to make the first test pass. I'll then add more tests to introduce more functionality to our library.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blogtwitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.


This article is related to

Architect,Intermediate,Articles,Computer Tutorials, Telerik, TDD

Wednesday, March 13, 2013

.NET TDD (Test Driven Development) by example - Part 1

Test First or Test Driven development is a valuable software engineering practice. It comprises of much more than this article could attempt to cover such as Acceptance Test Driven Development (ATDD) and Behaviour driven development (BDD). We will focus on a subset of TDD that encourages developer testing and aids tremendously in shipping software rather than traditionally having testing as a secondary phase or responsibility of a tester and promotes testing as a first class citizen in our everyday software development lifecycle (SDLC). How many times have you intended to write unit tests after a feature has been created and due to time constraints ended up leaving it and moving onto the next part of the application with an uncertain feeling that it would have been better to have them in place before adding more complex layers? Following a TDD approach eliminates this as the tests are the first thing to consider as part of an initial implementation.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blogtwitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.


This article is related to

</ span>.NET, TDD, Test Driven Development, .Net Tutorials, TDD Introduction

Tuesday, March 12, 2013

TDD Terminology Simplified

The core idea of Test-Driven Development (TDD) is writing tests before writing any functional code, and then writing only the least possible amount of code required to make the tests pass. It may sound strange to develop in this fashion, but it's actually quite useful, as the test base doubles as a partial specification of the main code.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blogtwitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.


This article is related to

</ span>TDD, Test Driven Development