Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
What First - CI or Unit Testing?

Here's a conversation I just had with another developer who is struggling to get his team to adopt some agile practices:

developer: if you were starting from scratch, which would you think is more important to setup first? CI or a unit testing process?
me: unit testing
developer: wow
developer:  ok
me: why is that surprising?
developer: i look at the mess i'm in everyday and i'd think getting a good build system in place would be first...
me: I think unit testing provides more value in that it allows you to add features knowing you haven't broken other features
developer: testing above a development process?
me: yes
me: testing provides more customer value

Let me be clear in stating that I think both are great value and a necessity, however the challenge was to choose one, presumably the most important.  I chose unit testing because one of the reasons I enjoy writing software that meets someone's needs.  As a developer one of the most nervous moments is when your code is released into the wild.  Will it work?  Will users they use it how you intended?  As a developer one of the most satisfying experiences is watching a user fire up a program you've written and it works flawlessly.  I think most customers would agree with that as well.  Having code that works is what they want.  Having code that works builds their confidence in you and reassures them that know what you're doing.  Testing provides this for me.  In advance I can test different scenarios and program that in and put my program through it's paces.

Now let me speak a bit about CI.  While I believe that testing is a component of CI, the developer in this instance meant a build server that kicks off automated builds.  While an automated build is nice, it doesn't nearly provide the value that unit testing does.  It's the things your build server does that increases it's value.  One of those things in our build system is running automated tests.  If you remove automated tests from a build server all you have is a dummy machine that compiles code.  That provides some benefit, but minimally.  You can replicate the behavior simply by updating your code often and doing a compile on your own machine.

As an agile developer I seek deliver value to stakeholders.  When viewed through that lens, I think unit testing clearly wins.

What about you?  Would you test before build server?  Or would you choose the build server?  Why?


Posted 08-19-2008 2:14 PM by Tim Barcz
Filed under: ,

[Advertisement]

Comments

Derik Whittaker wrote re: What First - CI or Unit Testing?
on 08-19-2008 3:47 PM

I would tend to agree that tests are better to start with.  However, if the developers on the team are new to testing then adding CI would be a faster win.

Jeremy Jarrell wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:02 PM

I agree that unit testing is more important, but to piggyback on Derik's point, the developers may be more accepting to a 'controversial' practice after seeing an easy win provided another agile practice like CI.

Also, in my experience, one of the greatest barriers to getting a team to adopt unit testing is not only getting them to write them but also getting them to actually run them regularly and keep them up to date.  Having a CI server in place that could automate this process forces the devs to pay attention to broken tests and respond to them immediately when they fail, instead of every few days or whenever they remember them.

Nice post,

Jeremy

Tim Barcz wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:04 PM

@Derik,

Can you go a bit deeper in your thoughts on this and why CI would be a faster win?  Also does faster = more value?

dave.t wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:07 PM

I would tend to pick CI, because it's (near) instant gratification, which is helpful when trying to sell new methods.  UT is ALWAYS hard to convince people to do, but a continuous build (with a couple UT) is a nice warm fuzzy for managers.  Also, it doesn't take much time or energy to get it up and running, and then you can start building your UT portfolio, which just looks even better in the CI environment.

Kyle Baley wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:10 PM

If I had to choose 'twixt the two, then yes, I'd go with unit testing. But when setting up an environment, I'd add an automated build and CI to the mix first.

It's the first step in creating a sense of collective code ownership. And it is key in breaking developers of the habit of checking in coding just because it "works on my machine".

That said, adding unit testing to the build is the first check-in I do after CI is set up.

JH wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:11 PM

CI gives you visual feedback to testing efforts. That can often be used to apply social or political pressure to ensure that testing gets done. Sure, it's not the ideal way but if you can lead a horse to water and he doesn't want to drink, you have to try ulterior methods to encourage the behavior.

Tim Barcz wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:12 PM

@Jeremy and @Dave

It's interesting that you both are pointing to providing proof to other developers.  While that may be correct in showing a quick win to other developers.  Do you feel CI provides value to customers just the same?

Interestingly enough at my last job we had CI before we had unit testing and I will admit that it was nice and it was a quick win for us, but ultimately we still had broken stuff all the time.

Ben Scheirman wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:13 PM

I agree that tests are of more value, I'd say only marginally.  Getting multiple developers to work seamlessly without breaking each others changes is difficult.  Having a continuous build is highly valuable even if no tests are in place.

If you're in a shop that doesn't yet practice unit testing, CI is definitely the first step.  Once you have it the value of having unit tests increases and becomes too large to ignore (to the rest of the team).

Mike wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:15 PM

Testing might be more important, but CI is probably an easier battle to win.  You can get it in place relatively quickly and you get an immediate payoff.  In my situation it was a great momentum builder to start getting other changes made.  Unit tests require more work, more setup and the benefits are not usually as immediate.  Plus, as was mentioned, having the CI server in place allows tests to be added in gradually and run automatically.

Also integrating unit testing into an existing project assumes that the existing code is either in a testable state already or that refactoring for testability would not be way too disruptive.

dave.t wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:18 PM

I think everyone here is saying what I was trying to say.  

I think CI adds value indirectly because build process and unit testing is more visible to developers, and it puts those ideas in their heads.  which in the end, will add more value to the customer than independent developers possibly writing UT on their own.

maybe?  :)

Tim Barcz wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:20 PM

@Ben

I think you have good point as do others.  The relative simplicity of a build server and what it does provides a low-cost entry point whereas unit-testing can be frustrating for newbies.

I've still got to stick with my original assessment and say I'd pick unit testing if I only get one to pick.  Not saying that it'd be easier or faster or any of those types of things.  There'd be pain in "adopting" unit-testing but I think that pain provides a greater value to customer in that they get working code.

The Inquisitive Coder - Davy Brion’s Blog » Blog Archive » The CI Build should be a given wrote The Inquisitive Coder - Davy Brion’s Blog » Blog Archive » The CI Build should be a given
on 08-19-2008 4:24 PM

Pingback from  The Inquisitive Coder - Davy Brion’s Blog  » Blog Archive   » The CI Build should be a given

Mike wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:26 PM

Which one first and which one period are two different questions.  I'd agree that unit testing is more critical if you can only have one.  But, as previously mentioned, they are very complimentary and the goal should be to get both into place.

KG2V wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:29 PM

Good question.  I think it depends on the size of the team, the LENGTH of the build, and assuming we are talking "brownfield" development, how fast you think  you can get things under test.

Assuming it's brownfield, with a LONG build, I'd go "CI", just on the "it's going to save the team N hours/week, right a way", and we can use those N hours to get testing started...

Jimmy Bogard wrote re: What First - CI or Unit Testing?
on 08-19-2008 4:59 PM

CI first. Always. Never tests first.

Why? Unit tests are pointless if they aren't part of a CI process.  I've seen at least 2 teams with a whole mess of failing tests, but nobody knows because they aren't being run.  Tests have no value unless they are executed.  Unit tests not part of an automated process will eventually stop being executed because it is too much friction otherwise.

Automated build is such a low hanging fruit, we always do that first when coaching.  It's a great introduction into the Agile values such as feedback.  CI is a team enabler, and opens the door to other practices.

JH wrote re: What First - CI or Unit Testing?
on 08-19-2008 5:49 PM

@Jimmy Good point!

mendicant wrote re: What First - CI or Unit Testing?
on 08-19-2008 6:07 PM

When this person is coming from what sounds like a fairly mature project (or set of projects) I would say CI first, without a doubt. What use are tests if you can't even provide a build to the customer. Tests provide customer value, yes. But even having full test coverage doesn't have any customer value if you can't even provide a build for them to use (in a timely fashion).

Personally, I'd make sure that I had a build process in place where I could, on demand, provide a deployable instance of the application, and then start adding the tests. If you can't deliver, you don't have any value.

jdn wrote re: What First - CI or Unit Testing?
on 08-19-2008 7:16 PM

Without a doubt, CI.

CI provides benefits to the entire team immediately (Well, once you get it running anyway).  Even if you have lazy bastards on the team who won't try to fix the build when I break it (you looking at me?), you know the state of the build at all times.

Unit testing requires conscious effort and buy in from the team.  

This isn't to say CI provides more value in the long run than unit tests (glad you didn't tie it to TDD, makes it easier), but you did ask which is better to have first.

I've worked on teams that had really weak unit testing but had CI.  CI's value was strong.

Did I mention I think CI is more important to have first?

jdn wrote re: What First - CI or Unit Testing?
on 08-19-2008 7:22 PM

"If you remove automated tests from a build server all you have is a dummy machine that compiles code."

Oh, absolutely not.  Imagine a VS solution that has over 100 projects, and is being worked on by a team of over 75 people.  Knowing that you can compile the individual changes in the central build, and know it as soon as possible is of *immense* value.

jdn wrote re: What First - CI or Unit Testing?
on 08-19-2008 7:22 PM

"If you remove automated tests from a build server all you have is a dummy machine that compiles code."

Oh, absolutely not.  Imagine a VS solution that has over 100 projects, and is being worked on by a team of over 75 people.  Knowing that you can compile the individual changes in the central build, and know it as soon as possible is of *immense* value.

Dale Smith wrote re: What First - CI or Unit Testing?
on 08-19-2008 8:38 PM

I agree with Jimmy - CI is the first step.  I'm in a large-ish shop where we're trying to introduce responsible design and implementation practices.  In my experience there, unit tests in a code base being worked on my more than one developer are absolutely worthless - without enforcement as a failable build step, their value will quickly erode.

One of the first things I did when I started at this job was to write the following article arguing for CI.

creedcultcode.blogspot.com/.../continuous-integration-and-you.html

Matt Youngblut wrote re: What First - CI or Unit Testing?
on 08-19-2008 9:34 PM

I want to agree with Tim, b/c I am at his previous place of employment, and we did have a lot of broken stuff, but...

Since shops generally don't have just one project that could use CI, you only have to set up the CI server once (with config for each project), and you get that benefit across the organization.  

With different projects, you might be setting up unit tests for each.  Granted, you could set up libraries to use, but then that just means that it would take longer to have your unit tests up and running.

Jak Charlton wrote re: What First - CI or Unit Testing?
on 08-20-2008 3:11 AM

CI

It is fast to setup, provides instant visibility to all, provides a sense of ownership ... and without it, you will never know if your tests are working or not anyway without direct developer interaction

That and it takes less than an hour to get CI fully up and running from having a blank Windows Server to a fully building and deploying project

Tim Barcz wrote re: What First - CI or Unit Testing?
on 08-20-2008 6:39 AM

I would caution that CI does not in fact take an hour to set up.  It does...only if you've done it before.  In this particular case the developer in question has never set up a build server before.  A simple CI implementation means the developer has to set up CruiseControl, learn the CruiseControl syntax for gettting his build to work the way he wants.  He now has to have a Nant file and if this is the first time he's ever set up CI.  Now he's got to go figure out Nant, which is another thing to learn.

I would challenge the idea that a newbie can get CI up and running in an hour.

I think a lot of you are taking for granted the very first time you set up CI and some of the hurdles you faced and all the varied technologies you must put together to get CI to work.

Joshua Flanagan wrote re: What First - CI or Unit Testing?
on 08-20-2008 8:28 AM

Tim - It really doesn't HAVE to be that hard. You do not need NAnt to run a continuous integration build. If using Cruise Control, you can simply have it run MSBuild on your .sln file.

Or you can use CI Factory.

Or, if you have TFS, you click through a build wizard and check a box to trigger builds on checkins.

Even if it does take more than an hour, it is still going to be a faster by orders of magnitude compared with training a team to write automated unit tests (and testable code).

Dew Drop - August 20, 2008 | Alvin Ashcraft's Morning Dew wrote Dew Drop - August 20, 2008 | Alvin Ashcraft's Morning Dew
on 08-20-2008 8:33 AM

Pingback from  Dew Drop - August 20, 2008 | Alvin Ashcraft's Morning Dew

Sidar Ok wrote re: What First - CI or Unit Testing?
on 08-20-2008 9:07 AM

Unit testing shouldn't even be open to discussion. When you are doing TDD, you can not have any code without having tests in place.

As a second side, for a true CI you will need to run unit tests as part of your built anyway.

So I concur with you that unit tests are more important even if there is a resistance about it in the team.

Jak Charlton wrote re: What First - CI or Unit Testing?
on 08-21-2008 3:15 AM

CI takes less than an hour ... if it doesn't then:

1) Stop using CC.NET, use TeamCity

2) Don't start with complex build files or NAnt, use the Build Solution task from MSBuild, or even use a batch file for that matter.

Yes I agree CC.Net could well take a few hours... writing complex NAnt scipts can add a few hours ... but even then, half a day spent will pay off within the first week.

That isn't to say don't do unit tests, but if you think CI is hard to get setup and accepted ... unit tests are another world of pain to get people up to speed with.

Jak Charlton wrote re: What First - CI or Unit Testing?
on 08-21-2008 3:22 AM

@Sidar

>>As a second side, for a true CI you will need to run unit tests as part of your built anyway.<<

Totally incorrect ...

CI does not require unit tests, but unit tests almost certainly do require CI

A build process that merges my changes with all other developers, checks the latest version out of source control, ensures it compiles, and deploys it to a UAT server has massive value, regardless of whether you have unit tests.

A unit test suite that is comprehensive cannot be shown, nor proven, to be unless it directly follows the above process. So you are going to waste huge amounts of time every check in by repeating pull updates from SCM, build, manually run all tests, check in - when it could all be done for you ...  and even if you do it manually, where is the visibility to management that your test are running, where is the history of their runs, where are the coverage reports being generated? Where is your guarantee on consistency that all developers will follow the above process?

Tim Barcz wrote re: What First - CI or Unit Testing?
on 08-21-2008 10:00 AM

@Casey,

I think you're being a bit dogmatic here.

"but unit tests almost certainly do require CI".  That is absolutely not true.  On projects I work on at home I don't use a build server and I most certainly DO write unit tests.

It wasn't discussed in the original post but team size matters.  A couple have posted about larger teams and some have presumed small teams.

I think you have to first evaluate your goals/problems.  If you're having integration problems and you work on a large team I might choose CI.  If you work on a small team with a lot of one-off project, of which you might be the only eveloper and you're deploying lots of bugs, then I'd go with unit-tests.

Jak Charlton wrote re: What First - CI or Unit Testing?
on 08-21-2008 10:49 AM

>> If you work on a small team with a lot of one-off project, of which you might be the only eveloper and you're deploying lots of bugs, then I'd go with unit-tests<<<

You said you spoke to another developer - hence your project has 2 people - hence you should have CI ... if you are writing code at home, sure forget CI, you don't ever merge code anyway so no loss.

The rest of us work in teams where we annoyingly screw up other people's code all the time .... hence CI is the important part - it is also the only part the customer sees.

Unit tests are for the developer - CI is for the business to see what the developers are doing.

But regardless, as it takes an hour (or half a day) to setup - just do it - you spent longer justifying to the developer why tests were more important than to show him how to setup CI ...

Sidar Ok wrote re: What First - CI or Unit Testing?
on 08-21-2008 10:57 AM

@Casey

Read the sentence with "true" in the beginning again. CI does not have to have unit tests, but do you call it a good CI in place then ?

How do you ensure your certain unit is working properly without unit tests ? If you don't ensure, don't you break "make your builds auto validate themselves" rule of CI ?

Casey wrote re: What First - CI or Unit Testing?
on 08-21-2008 12:12 PM

CI is about integration, building, and deployment for testing ... It has value in a project where no unit tests are present... Adding tests to the build adds more value, but there is no "true" version of CI that must have tests ...

Currently I am busy recovering a project gone wrong ... The first thing was to put in a build server.

From that alone we now have developers encouragedto check in frequently, to make sure they always have a working build, to be able to verify their changes on the automatically deployed UAT server, and we have the business users now checking the project progress every morning, or whenever we say "hey check the site now, we made that change you wanted", and we have the manager and PM able to see changes and progress live as it happens.

We have no unit tests at all.

One gives massive value, is zero cost, and has increased confidence of everyone on the team ... If I had started with unit testing and TDD we still wouldn't have delivered any functionality, as unit testing WELL is something that takes months to return on time invested... TDD takes even longer.

In the long term unit tests pay off, as does training people on how to write them ... In the short term they do not if you have an inexperienced team

CI pays off from hour one

Travel Jakarta Bandung wrote re: What First - CI or Unit Testing?
on 08-13-2010 3:39 AM

I think you have to first evaluate your goals/problems.  If you're having integration problems and you work on a large team I might choose CI.  If you work on a small team with a lot of one-off project

Moncler Coats wrote re: What First - CI or Unit Testing?
on 09-08-2010 11:31 PM

Unit Testing is available, the problem is how to merge into a whole Unit Testing project

Kalie wrote re: What First - CI or Unit Testing?
on 05-31-2011 11:28 PM

AFAICT you've covered all the bases with this anwesr!

devlicio.us wrote re: What First - CI or Unit Testing?
on 06-25-2011 5:18 AM

What first ci or unit testing.. Corking :)

3mj4 free sex plh6 wrote re: What First - CI or Unit Testing?
on 07-02-2011 11:04 PM

What first ci or unit testing.. WTF? :)

Khalil wrote re: What First - CI or Unit Testing?
on 02-21-2012 2:33 PM

Interesting   I'll take a look. Currently, I'm atlevicy beta-testing  for the Mac   the OmniGroup applications are wonderful MacOSX apps and I have bought licenses for nearly all their stuff in the past.

Michelle wrote re: What First - CI or Unit Testing?
on 02-24-2012 12:06 AM

What about tiqenecuhs? The average joe user may be able to read some bar and pie charts. But are they equiped with the knowledge to design test and experiment?

social bookmarking sites submission wrote re: What First - CI or Unit Testing?
on 01-18-2013 10:32 AM

SMqxcP Im thankful for the blog.Really thank you! Really Cool.

buy generic cialis wrote re: What First - CI or Unit Testing?
on 01-27-2013 10:57 AM

p9Nrog Say, you got a nice blog article. Fantastic.

lose weight pills wrote re: What First - CI or Unit Testing?
on 02-01-2013 9:36 AM

6Tj3MT Im grateful for the blog post.Much thanks again. Awesome.

http://bestmedicineonline.info wrote re: What First - CI or Unit Testing?
on 02-14-2013 11:06 PM

HfO6Ef Thank you for your blog article.Much thanks again. Cool.

buy stendra online wrote re: What First - CI or Unit Testing?
on 02-23-2013 1:50 PM

V78VBC Awesome post.Much thanks again.

clomiphene 25 mg wrote re: What First - CI or Unit Testing?
on 02-28-2013 8:47 AM

oxdATj Im grateful for the article.Really thank you! Want more.

buy discount viagra wrote re: What First - CI or Unit Testing?
on 03-03-2013 10:05 AM

KR38EP Im thankful for the blog post. Great.

bookmarks wrote re: What First - CI or Unit Testing?
on 03-13-2013 8:27 PM

X8U2yD Wow, great article post.Really looking forward to read more.

bookmarks wrote re: What First - CI or Unit Testing?
on 03-15-2013 1:48 AM

RchPNX I loved your post.Thanks Again. Keep writing.

social bookmarking service wrote re: What First - CI or Unit Testing?
on 03-22-2013 2:56 PM

fIjm9b Major thankies for the blog post. Really Cool.

Social bookmarks wrote re: What First - CI or Unit Testing?
on 03-24-2013 11:03 PM

SF9HMr Very neat article post.Thanks Again. Will read on...

comedy shirts wrote re: What First - CI or Unit Testing?
on 04-06-2013 1:46 PM

Looking forward to reading more. Great blog.Really thank you! Really Great.

Social bookmarks wrote re: What First - CI or Unit Testing?
on 04-23-2013 9:35 PM

Q9qB67 Thanks for sharing, this is a fantastic article post. Awesome.

slr lenses wrote re: What First - CI or Unit Testing?
on 05-14-2013 8:51 AM

rcXI5W Great, thanks for sharing this article.Thanks Again. Really Great.

social bookmarking service wrote re: What First - CI or Unit Testing?
on 06-06-2013 11:41 PM

hibV2p I think this is a real great blog post.Really looking forward to read more. Awesome.

social bookmarks wrote re: What First - CI or Unit Testing?
on 06-19-2013 1:38 PM

FHDNlg Hey, thanks for the blog.Really thank you! Cool.

social bookmarks wrote re: What First - CI or Unit Testing?
on 06-21-2013 2:17 PM

J11a6G Major thanks for the article post.Much thanks again. Great.

great service wrote re: What First - CI or Unit Testing?
on 07-04-2013 9:09 AM

ulELli Thank you for your article post. Really Great.

cool news wrote re: What First - CI or Unit Testing?
on 07-09-2013 4:53 PM

Aaa5Kz Im thankful for the blog post.Much thanks again. Fantastic.

super news wrote re: What First - CI or Unit Testing?
on 07-13-2013 4:00 AM

mjV8af I value the blog post.Thanks Again.

buy viagra online cheap wrote re: What First - CI or Unit Testing?
on 07-23-2013 2:33 PM

I appreciate you sharing this blog article.Really thank you! Keep writing.

buy cialis online cheap wrote re: What First - CI or Unit Testing?
on 07-24-2013 4:06 PM

Im thankful for the blog.Really looking forward to read more. Much obliged.

best news on earth wrote re: What First - CI or Unit Testing?
on 07-26-2013 3:04 AM

4lHaO9 A big thank you for your blog post.Thanks Again. Really Cool.

replica rolex wrote re: What First - CI or Unit Testing?
on 07-28-2013 3:42 AM

You must allow kids to make their own mistakes. Not doing so is the worst kind of patenting.

news wrote re: What First - CI or Unit Testing?
on 08-03-2013 6:37 AM

Great, thanks for sharing this blog.Much thanks again. Keep writing.

awesome moldavian news wrote re: What First - CI or Unit Testing?
on 08-04-2013 11:18 PM

vcuP3U I am so grateful for your blog post.Thanks Again. Want more.

awesome links for you wrote re: What First - CI or Unit Testing?
on 08-19-2013 11:48 AM

tXIpme Thank you for your blog.Thanks Again. Great.

great link buildng wrote re: What First - CI or Unit Testing?
on 08-20-2013 12:49 AM

x8SZzk I truly appreciate this post.Thanks Again. Fantastic.

great link buildng wrote re: What First - CI or Unit Testing?
on 08-22-2013 10:24 PM

BXFbUo This is one awesome blog article.Much thanks again. Will read on...

great seo service wrote re: What First - CI or Unit Testing?
on 09-04-2013 2:19 AM

aj5r20 Thanks so much for the blog post.Really thank you! Awesome.

link building wrote re: What First - CI or Unit Testing?
on 09-06-2013 1:49 AM

IuC4QK Thanks so much for the blog.Much thanks again. Much obliged.

online business wrote re: What First - CI or Unit Testing?
on 09-11-2013 6:59 PM

m8GHfZ Very neat blog article. Cool.

only for 5 dollars wrote re: What First - CI or Unit Testing?
on 09-12-2013 7:41 PM

bIbzGw Thank you for your blog.Really looking forward to read more. Really Great.

cheap seo work wrote re: What First - CI or Unit Testing?
on 09-29-2013 4:53 PM

h0XcQ7 Thanks for sharing, this is a fantastic article.Really looking forward to read more. Much obliged.

awesome linkbuilding site wrote re: What First - CI or Unit Testing?
on 09-30-2013 8:28 PM

IQPks6 wow, awesome article.

check out these guys! wrote re: What First - CI or Unit Testing?
on 10-15-2013 11:27 AM

7Z5XT0 Thank you for your article post. Cool.

uggs outlet wrote re: What First - CI or Unit Testing?
on 10-22-2013 5:52 AM

Alabama Piano is Alabama's premier piano retailer. I would highely recommend a go to.

smashing top seo wrote re: What First - CI or Unit Testing?
on 10-25-2013 3:32 PM

60GNMj I really like and appreciate your blog article.Really thank you! Want more.

link building wrote re: What First - CI or Unit Testing?
on 11-01-2013 6:51 PM

OZttYS Thanks a lot for the blog post.Really thank you! Cool.

link building wrote re: What First - CI or Unit Testing?
on 07-18-2014 11:02 AM

Qpazvz A big thank you for your post.

matt wrote re: What First - CI or Unit Testing?
on 07-19-2014 3:04 PM
matzcrorkz wrote re: What First - CI or Unit Testing?
on 08-06-2014 9:19 AM

RAtbaN Really informative blog post.Really looking forward to read more. Will read on...

matt wrote re: What First - CI or Unit Testing?
on 10-15-2014 7:42 AM
john wrote re: What First - CI or Unit Testing?
on 10-15-2014 7:49 AM
crorkz jremy wrote re: What First - CI or Unit Testing?
on 11-23-2014 10:23 AM

f8FU6n I was recommended this web site by my cousin. I'm not sure whether this post is written by him as nobody else know such detailed about my problem. You're incredible! Thanks!

crorkz wrote re: What First - CI or Unit Testing?
on 12-17-2014 9:30 AM

s30Dix Thanks so much for the article post.Really looking forward to read more. Want more.

Add a Comment

(required)  
(optional)
(required)  
Remember Me?

About The CodeBetter.Com Blog Network
CodeBetter.Com FAQ

Our Mission

Advertisers should contact Brendan

Subscribe
Google Reader or Homepage

del.icio.us CodeBetter.com Latest Items
Add to My Yahoo!
Subscribe with Bloglines
Subscribe in NewsGator Online
Subscribe with myFeedster
Add to My AOL
Furl CodeBetter.com Latest Items
Subscribe in Rojo

Member Projects
DimeCasts.Net - Derik Whittaker

Friends of Devlicio.us
Red-Gate Tools For SQL and .NET

NDepend

SlickEdit
 
SmartInspect .NET Logging
NGEDIT: ViEmu and Codekana
LiteAccounting.Com
DevExpress
Fixx
NHibernate Profiler
Unfuddle
Balsamiq Mockups
Scrumy
JetBrains - ReSharper
Umbraco
NServiceBus
RavenDb
Web Sequence Diagrams
Ducksboard<-- NEW Friend!

 



Site Copyright © 2007 CodeBetter.Com
Content Copyright Individual Bloggers

 

Community Server (Commercial Edition)