mars 04
I just published a long article (in french) on about continuous integration in the Microsoft.NET world. You will find here the table of content of this article :
- Quick introduction to continuous integration
- Quick presentation of the tools needed for Continuous Integration (in the Microsoft.NET world)
- Unit Test : Writing unit tests with MsTest
- Unit Test : Executing tests with MsTest
- Unit Test : Configuring tests
- Unit Test : Managing the tests
- Unit Test : Additional attributes
- Static Code Analysis : Presentation
- Static Code Analysis : Correcting the errors
- Static Code Analysis : Limitations

I will soon publish a second article that will focus that time on MsBuild and TfsBuild. You will see also a first insight on the table of content of this second article. [Plus]
oct. 20
I'm just back from the CITCON 2008 that took place in Amsterdam, Netherlands. I went there with my agile co-speaker Norman Deschauwer and a friend Thierry Thoua.
We had many very interesting session there and you will find my notes about these sessions:
- The role of funnctional tester with Sai Patel, Eric Jimmink, Freddy Mallet, Cirilo Wortel and Paul Julius
- Data used for development and testing with Douglas Squirrel and Alexander Snaps
- Code quality and metrics facilitated by myself and Freddy Mallet
- Functional Testing, more precisely using FIT
- Who cares about Javascript facilitated by Matt Wynne

We spoke about many tools (Team City, FIT, FITnesse, Watir, Firewatir, SafariWatir, selnium, celerity, HtmlUnit, JsUnit, JQuery, YUI, ...).
You will also find some photos about the event. [Plus]
sept. 15
CITCON (Continuous Integration & Testing Conference) comes to Amsterdam in October 3rd & 4th (friday evening and saturday).
Join me there ! [Plus]
nov. 23
If you, like me, are used to run your tests outside of Visual Studio directly in command line via MsTest, you may encounter some stange and unexpected behavior while migrating to Visual Studio 2008 : a message telling me that there is "No test to run".

You are also getting this message and want to know more about this ? Read this post ! [Plus]
nov. 07
When you run tests from command line, directly with the MsTest tool, you can include the reason of the failure (which is called the TestOutcome).
This value is coming from an enum TestOutcome declared in Microsoft.VisualStudio.QualityTools.Common.
Check in this post the different possible values and how you can retrieve it in the TRX file. [Plus]