TIP - Starting And Stopping Selenium Server Automatically

Found a nice article which explains how to start/stop your selenium server automatically using FixtureSetUp and FixtureTearDown of AssemblyFixture.

http://igorbrejc.net/development/cruisecontrolnet/gallio-starting-and-stopping-selenium-server-automatically-during-testing-using-assemblyfixture

Some notes on Slim (getting started)

To use Slim instead of Fit, you need to define Slim as the test system

• !define TEST_SYSTEM {slim}

Symbols

• $name= sets the symbol
• $name uses the symbol
• $name= also in script tables as first cell$

Decision Tables (aka Slim Column fixture)

• Check/Check not – value test pass/fail
• Ensure/Reject - bool test pass/fail
• Note - comment
• Show – display result
• Start – sets up a different system under test
• Optional constructor arguments after class name
  

Debugging FitNesse Fixtures within Visual Studio

I came across a great article from Jim Holmes on his blog "Frazzleddad".
In his post, he explains how to debug FitNesse fixtures within VisualStudio - which is great, because if a FitNesse test fails for unknown reasons, it can be painful to get to the root cause of the problem - and I currently write unit tests to test the fixture code independently of the tables. By introducing Fixture debugging, I can run my FitNesse tests directly from VisualStudio, and use breakpoints to find out what is happening inside the fixture code.

Setting this up is very simple. Folow these steps:-

1. Open the Project Property page for the fixture.
2. Select the Debug tab.
3. Select the "Start external program" radio button, and enter the path to TestRunner.exe in it's field.
4. In the "command line argumants" field, enter the host, port and page which relate to your FitNesse test (e.g. localhost 8081 EmailSystemTests.TestSendMail)
5. Set the fixture project as the startup project.
6. Add breakpoints and click Run(F5)

* First time I tried, VisualStudio complained about the TestRunner.exe.config file. I just renamed the file, and everything worked as expected.

Here is a screenshot of the VisualStudio Project Properties dialog (stolen from frazzleddad)


Original post - http://frazzleddad.blogspot.com/2008/01/debugging-fitnesse-tests.html

How to expect a non-matching result in FitNesse.Net

Using FitNesse.Net, it is simple to create a test which specifies what the expected result of a test should not be. For example:-

One plus One should not equal Three.

To do this, you simply put fail[{result}] in the result cell. For example:-