Contents tagged with tdd
-
Testing SignalR Connections with NUnit
The SignalR GitHub site has an example wherein a SignalR PersistentConnection instance is used from a non-HTML client. The idea of being able to use SignalR connections in applications other than those that run in a web browser raises some interesting challenges. Likewise, there aren’t too many examples on how to use SignalR connections. This post will demonstrate asynchronously testing a SignalR connection in an end-to-end scenario using NUnit.
-
The Robot Factory Kata
On the drive home from my last Behavior Driven Development talk, I began thinking about the idea of Code Katas and how one might be appropriate in my future disucssions of Behavior Driven Development. Given that BDD tries to solve things in as simple and direct a path as possible, and given that BDD takes some of the lessons learned via TDD and applies them in slightly more business-centric language, a Kata would demonstrate well the effectiveness of BDD when applied to a problem domain.
-
Doing BDD with SignalR and Jasmine
SignalR is one of the latest (and sexiest) elements in the .NET stack. Expect to hear more about SignalR if you haven’t already, because it delivers on the promise of push technology without the requirement of a fat client. If you’ve not yet read much about SignalR, clone the source code from GitHub or read Scott Hanselman’s post on SignalR for an introduction. The scope and inner-workings of SignalR are somewhat out of scope here, so I’ll just assume you’ve at least heard something about SignalR and that you’re interested in it but have a few questions. I mean, if you’re into BDD/TDD, you should definitely be wondering:
-
Testing ASP.NET MVC with QUnit - Part 2
In Part 1 of this series I demonstrated how QUnit can be used to test JsonResult action methods in ASP.NET MVC applications. Part 2 will take the idea a little further by showing an example of how QUnit can be used to inspect potential user-input areas on your MVC forms and to use those values in tests that will verify the requirements have been met.
-
Testing ASP.NET MVC with QUnit - Part 1
One of the problems that face any web developer is their ability to properly test the GUI components of their sites. A few options exist, specifically Watin, with varying degrees of success. Now that I've been experimenting with the ASP.NET MVC framework I've modified a good deal of my GUI work in such a way that it minimizes form-posts and makes use of the AJAX goodies packed into jQuery. Since a lot of my work has moved to the client following my adoption of this approach I needed to investigate new options for testing. This morning I had the luck to stumble across QUnit, a jQuery testing plugin that makes life pretty easy.
-
Lightweight Process Question
I think there exists some value in a direct mapping between your software's system roles, the functions provided to each role, and the tests one writes to verify that each type of user can perform each task with the same desired outcome. Albeit a simplistic (or trite) view of the process of creating software, I think such a mapping can actually define your project's work items. Let me explain. At the end, there's question. I'm really interested in what the community thinks of this approach, welcome any outright flames, and of course encourage critical-yet-considerate dialog.
-
Excellent Noob RhinoMocks Post
Buddy, the Beginnermediate developer (I love that tagline BTW) has written an excellent blog post on Rhino Mocks. For someone like myself who understands TDD, implements it at a "B-minus" level and who thinks that mocks could help but have no idea how to get started, this post is a must-read. I can't wait to download RM now and get started. Excellent work!