is a community that was established to collect and organize valuable web information. Our technical staff have selected and indexed information and courses that they feel will help you stay current on best practices across the SDLC.

125 Articles match "Unit Testing"

  • The Best from DevelopMentor

    125 Results found
    Showing page 1 of 13   Next >

  • Significant Advances in Unit Testing Windows Workflow
    This post describes a unit testing library for testing Windows Workflow Foundations. Rather it's a library that can be used in conjunction with any of these testing frameworks. Download the library with sample test project here: (216 KB). First a Little History: Last September I posted this teaser entitled Unit Testing Coming to a Workflow Near You. In that previous post, I highlighted what I could determine to be the current state-of-the-art with regard to unit testing workflows, circa September 2008.
    Michael C. Kennedy's Weblog - Sunday, January 18, 2009
  • Article: Avoiding 5 Common Pitfalls in Unit Testing
    Llewellyn Falco and I recently wrote an article for DevelopMentor's Developments newsletter entitled Avoiding 5 Common Pitfalls in Unit Testing. Avoiding 5 Common Pitfalls in Unit Testing. When I started out with unit tests, I was enthralled with the promise of ease and security that they would bring to my projects. In practice, however, the theory of sustainable software through unit tests started to break down. Unit Tests have become more trouble than they are worth.". When tests would stop working, we just ignored them.
    Michael C. Kennedy's Weblog - Thursday, August 6, 2009
  • Unit Testing Coming to a Workflow Near You
    [Update: See the follow up post "Significant Advances in Unit Testing Windows Workflow" ]. However you won't find very much support for Test Driven Development (TDD) or unit testing in general. In fact the architecture that makes Windows Workflow powerful (strict separation of workflow, activities, and the host for example) really gets in the way of unit tests. There has been some work done on unit testing Windows Workflows. Here's some links: Unit Testing Activities with Windows Workflow Foundation by Ron Jacobs.
    Michael C. Kennedy's Weblog - Tuesday, September 30, 2008
  • TDD Invades Space Invaders
    As a follow-up to our " Avoiding 5 Common Pitfalls in Unit Testing " article we did a webcast where we took a problem from the audience and solved it live and unrehearsed on stage. The thing to remember is that all of this was done for the sole purpose of creating a recipe for a scenario we could test. Create a new test project. We made it to step 4 during our presentation (download code below) and estimate another 15 minutes would have had the whole scenario done, tested, and well-factored. Tags: DevelopMentor Screencasts Talks Unit Testing
    Michael C. Kennedy's Weblog - Wednesday, October 28, 2009
  • Unit testing a ASP.NET WebAPI 2 controller
    'Earlier this year I wrote a blog post about how to unit test ASP.NET WebAPI controllers. It turned out that in order to do a good job of testing the public ApiController methods you would need to quite a bit of setup. One of the goals of the ASP.NET WebAPI 2 was to make testing of controllers easier. So how does this change the unit testing story? So how about testing them? Testing the Get() method. The Get() method as real easy to test before as we where just returning an IEnumerable. Testing the Get(id) method. 13: {.
    The Problem Solver - Wednesday, November 13, 2013
  • Test Driven Development, Approval Testing, and a Song – Oh Boy!
    So my buddies Dan Gilkerson and Llewellyn Falco have been doing some brilliant, ground breaking work on advancing the state of unit testing and TDD with a concept they call Approval Testing. To highlight the transition from unit testing -> … Continue reading → Agile Video.NET unit testing
    Michael C. Kennedy's Weblog - Wednesday, January 7, 2009
  • Test-Driven Cameras
    wish people had this same reaction to the idea of writing code without first writing tests (TDD). Tests give you the chance: To see what you are going to write, BEFORE you write it. If you haven’t already, here’s a great place to start learning to Test-Driven Development ? If you are already writing tests, here’s a free library to make test even easier to write? Unit Testing TDDI am getting old. The other day I was hanging around with my friend, Ike Ellis. He told me a story about his kids. The first question they asked was “Where is the picture?”
    DevelopMentor Courses - Wednesday, September 7, 2011
  • Unit testing a ASP.NET WebAPI controller
    Testing a simple ApiController that gets data Suppose we have the following ASP.NET WebAPI Controller with two Get methods, the first returns the complete list of books and the second returns the book with the requested ID. Testing the Get() method. The Get() method that returns all books is easy enough to test. Testing the Get(id) method. Testing for getting with an invalid ID is equally simple: 1: [TestMethod]. Testing an HTTP PUT operation. Testing an update using an HTTP put is just as simple as a testing a get action. 8: 9: }. 11: {.
    The Problem Solver - Sunday, May 12, 2013
  • Unity, Multiple Constructors and Configuration
    However to make Unit Testing simple I’ll add another constructor to MyService so I can pass a specific timeout. Tags: NET;IoC;Unit Testing I’ve been working with the Unity IoC container from Microsoft Patterns and Practices recently. Its mostly straightforward as IoC containers go but one thing had me puzzled for a while as its not really documented or blogged as far as I can see; so I decided to blog it so hopefully others looking will stumble across this article. 1: public interface IService. 3: void DoWork(); 4: }. 1: public interface IRepository. and MyService.
    .NET Meanderings - Monday, June 7, 2010
  • Unit testing the AngularJS code in the RAW Stack
    However we didn't actually start writing any tests yet so lets create a few tests. The AngularJS controller under test Just as a quick reminder the AngularJS controller in our previous code was as follows 1: ( function () {. What do we want to test. The first thing we need to think about what to test. There isn't really a lot of application logic here so there is not much to test on that front. With JavaScript there is no compiler to validate this so it makes sense to create small unit tests that check our public interface. Try it.
    The Problem Solver - Saturday, February 22, 2014
<< 1 2 3 ... 12 13 >>