Fixie Blog Series Moving to LosTechies.com

For the last few months, I’ve been writing a blog series here to document my progress on the Fixie test framework. Recently I joined Los Techies, and will continue the blog series there. Be sure to add Los Techies to your reading list!

By Your Command (Line)

Last week, we saw an example of Dynamic Test Discovery in Fixie, in which the test runner can be made to run a different set of tests each time, depending on context. A Fixie convention could make decisions based on how the test run was initiated. This week, I’ll demonstrate a similar feature which takes […]

Dynamic Test Discovery

Recently I received feature requests for Fixie that initially proved difficult. I was tempted to engage in a vague refactoring effort until it became more clear how to proceed. Of course, giving in to that temptation would have proven wasteful. I might have achieved some degree of subjective cleanliness while getting no closer to actually […]

When Writing C#, Use C#

Recently, Jimmy Bogard described several strategies for isolating a database in tests. Today, we’ll see how one of these strategies can be implemented. We’ll start with a common implementation under NUnit, then we’ll identify some issues with that implementation, and lastly we’ll translate it into a Fixie convention to address those issues. Today’s code samples […]

Streamlined Integration Tests

Last week, we saw how Fixie can be used to simplify NUnit’s treatment of inheritance. This week, we’ll see how to use it to streamline integration tests in systems that leverage IoC containers. Today’s code samples work against Fixie The customization API is in its infancy, and is likely to change in the coming […]

DRY Test Inheritance

Over the last two weeks, we’ve seen how Fixie can be configured to mimic NUnit and to mimic xUnit. That’s a neat little trick, but doesn’t provide much value. This week, we’ll see how Fixie’s convention API can be used to improve upon NUnit. Today’s code samples work against Fixie The customization API is […]

The Sincerest Form of Flattery

Last week, we saw how to define an NUnit-imitating convention with the Fixie test framework: when the custom Convention class was present in our test project, the default rules for finding and running tests were replaced, allowing us to write test classes with a familiar NUnit class lifecycle. This week, we’ll see how to customize […]

Fixie’s Life Bicycle

Last week, we saw how the Fixie test framework gives you control over test discovery. This week, we’ll see my first (admittedly rough) attempt at similarly giving you control over test execution. Let’s start with a quick review of last week’s test discovery feature, and then extend the example to demonstrate Fixie’s treatment of test […]

Test Discovery

Over the last few weeks, I’ve implemented some customization features in the Fixie test framework. The first of these features is now available. Today, we’ll see this feature in action. We’re going to tell Fixie what our tests look like, and Fixie will then find them and run them. Today’s code samples work against Fixie […]

Enabling Change

Unit testing is meant to enable change by giving you confidence about the current state of your project. However, one of the criticisms of unit testing is that fine-grained tests (such as having one or more tests per method), locks you into implementation details. With fine-grained tests in place, you’re not free to move responsibilities […]