Installing the framework, creating your first test, making assertions.
Articles about Fixie
Describing the project and its motivations and goals.
Mitigating technical risks by tackling the hard work first.
Setting up an open-source project, making it easy to use and contribute to.
Using Fixie to test Fixie.
Keeping a project healthy by pouncing on leaky abstractions before they spread.
Learning about runtime directory management by having it go wrong.
Diagnosing and fixing that runtime directory problem.
Improving accuracy by cutting scope, and gaining deeper insight on async methods.
Managing your process as an army of one.
Learning humility at the hands of IDisposable.
Letting your testing philosophy evolve as the codebase evolves.
Discovering tests by convention.
Customizing test execution.
Exploring lifecycle customization by mimicking xUnit's style.
Improving upon NUnit's lifecycle.
Leveraging IoC in your test classes.
Contrasting NUnit's before/after hooks with Fixie's wrap hooks.
Improving design one feature at a time.
Customizing test execution with command-line arguments.
Introducing Fixie to the Los Techies readership.
Fixing a bug that resulted from a subtle DRY violation.
One bad decision spreads through the whole system.
Safely fixing the bad decision from the previous article.
Honor your contracts to avoid surprises.
Shuffling tests to detect brittle assumptions.
Parameterized tests, with help from a versatile and sharp delegate type.
Misleading names can harm your ability to reason about code.
Customizing Fixie to work with AutoFixture reveals a more general pattern: single-call parameterized methods.
An example convention for parameterized methods that are called multiple times.
Fail loudly to catch problems early.
Using concrete feature requirements to evolve your design.
A trio of improvements to Fixie, motivated by the implementation of TeamCity integration.