FsTest Updated with F# CTP

submitted by adminjew 3 days, 7 hours ago

codebetter.com — Back in June, I announced the creation of FsTest, a testing Domain Specific Language for F#. Since that time, the F# team has released the September 2008 CTP, which finally gives F# full citizenship within Visual Studio with real project files. I felt it was time to update FsTest, and more in particular, FsxUnit, which uses xUnit.net as the back end for doing assertions. Go ahead and pick up the latest bits here from the CodePlex site. read more...

add a comment | category: Unit Testing | Views: 1

Unit testing and PInvoking pt. 2

blog.mendeltsiebenga.com — Part two in a series of blogposts describing how to unit test code that uses PInvoke calls. read more...

add a comment | category: Unit Testing | Views: 0

Unit testing and PInvoking

blog.mendeltsiebenga.com — The first part in a series of tips, tricks and best practices on unit testing code that uses pinvoke. read more...

add a comment | category: Unit Testing | Views: 4

RhinoMocks 3.5 AAA Model

submitted by ndibek 16 days, 13 hours ago

nermins.net — A short introduction to some of the new features in RhinoMocks 3.5, by contrasting them with the tests written in old syntax... read more...

add a comment | category: Unit Testing | Views: 4

Taking a look at NUnit 2.5 Alpha 3

blog.benhall.me.uk — Detailed look at NUnit 2.5 alpha 3. read more...

add a comment | category: Unit Testing | Views: 3

Acceptance TDD Explained

methodsandtools.com — Acceptance test-driven development is what helps developers build high-quality software that fulfills the business’s needs as reliably as TDD helps ensure the software’s technical quality. read more...

add a comment | category: Unit Testing | Views: 13

Testability in .Net

submitted by adminjew 21 days, 13 hours ago

theruntime.com — Your environment can have a profound effect on how you develop software. The details of what I discuss here have zero practical meaning outside of the .Net world (though you can probably find parallels in other environments). That’s because .Net developers have access to tools that invalidate rules of software design that are fundamentally important elsewhere (before you question whether an environment can effect what is good design, consider the difference between good design in C and, say, Prolog). For .Net, the free availability of a tool like Typemock makes a major design consideration simply disappear—namely, testability. Typemock literally robs the term “testability” of meaning in .Net design considerations. That’s a freedom that should leave other developers gasping in envy. read more...

add a comment | category: Unit Testing | Views: 6

Unit Testing using Mocks - FillWithMocks, Fill all or only selected pr

smsohan.blogspot.com — I have been doing TDD for about two years now and using mock testing for interaction based unit testing in my projects. What I have learned over this time is, a unit testable design leads to introduction of interfaces and dependency injection for testing a code in isolation. And when I want to perform tests on my interactions, I need to create mock objects and inject these mock instances to my object under test. Sometimes, a unit test class needs to create quite a few of such mock objects and I feel this can be done using a simple wrapper around the usual mocking frameworks. I suggest a similar and even more powerful wrapper so that you don't need to create instances for each of the mock objects, rather do it in a single call for all your desired mocks. I have shown this method for NMock2, however, its evident that you can write your own method for your favorite mocking framework just using this code as a reference. read more...

add a comment | category: Unit Testing | Views: 4