Integration Testing With Fitnesse

All the paths mentioned above for the DLL(s) and EXE(s) are relative to the Jar file of the Fitnesse. Here we are using fit.dll which says that by default the FIT Engine will be used and in the preceding case we haven't specified any specific test engine that by default tells Fitnesse to use the FIT engine.

See the screenshot for the settings.

Now we are done with the Fitnesse test engine configuration with the FIT, let's now look into how to create a Test Class for it.

For this open Visual Studio, create a class library project (the framework used should be the same as for which you have downloaded the FitSharp package). Add a reference of "fit.dll" to your project and add a class to it, refer to the following code for an example.

using fit;

namespace SampleLibrary
{
    public class UserTest : ColumnFixture
    {
        public string UserName { get; set; }
        public string Password { get; set; }

        public bool IsAuthenticated()
        {
            if (UserName == "Abhishek" && Password == "test")
            {
                return true;
            }
            else
            {
                return false;
            }
        }
    }
}

So here you can see that the Test class is being inherited by ColumnFixture.

SLIM

For configuring SLIM as the test engine for Fitnesse, open the Front Page of the Fitnesse as shown in the screenshot above. At the bottom of this page, you will see the option "root". Click on this link and it will open a page for you as shown below.

Click on the Edit Button and provide the following commands to configure the FIT Engine.

!define TEST_SYSTEM {slim}
!define COMMAND_PATTERN {%m -r fitSharp.Slim.Service.Runner,FitSharp\fitsharp.dll %p}
!define TEST_RUNNER {FitSharp\Runner.exe}

All the paths provided above for the DLL(s) and EXE(s) are relative to the JAR file of the Fitnesse. Here we are using fitSharp.dll and SLIM is defined as the Test Engine.

See the following screenshot for the settings.

Now we are done with the Fitnesse test engine configuration with SLIM, let's now look into how to create a Test Class for it.

For this open Visual Studio, create a class library project (the framework used should be the same as the one you downloaded for the FitSharp package). Add a class in it, refer to the following code for an example.

namespace SampleLibrary
{
    public class UserTest
    {
        public string UserName { get; set; }
        public string Password { get; set; }

        public bool IsAuthenticated()
        {
            if (UserName == "Abhishek" && Password == "test")
            {
                return true;
            }
            else
            {
                return false;
            }
        }
    }
}

With this we are done with the configuration part, now let's see how to create Test Pages in Fitnesse, for this go to the Front Page and Edit that Page. Now add the name of the Page that you want to create at the end or on the top or maybe anywhere you want the reference of your test page as shown in the screenshot.

In the preceding screenshot, you can see that I have created a new page named "UserTest". When you click on save you will see that there is something with your page name, and your page is not clickable, this shows that the page is new and now you can define your test on this page. In the example below I will show you how I will test the code in my UserTest class but before that, we should understand what the relevance of adding a page is.

A Fitnesse Page can be any of a few types, in other words, Static, Suite, or a Test. One can do the settings by opening the page and changing the properties from "Tools" -> "Properties" as in the following.

1. Test: This is the simple test page on which you will provide your script or create Decision Tables to carry out test runs.
2. Static: Static Pages are the pages on which we can't execute any test runs. So what's the use of this page, this page is useful for example in a scenario that the new library is being developed, and by the time it is developed the Testing team can provide the scripts to test the library but they don't want the test run to be executed after they have created that page (yes, the test run is done by clicking "Test" on top of that page so you must be wondering why not a create a Test Page and not click on this button, but think of a scenario in which there is an automated system that runs the test cases so that system will not know that if the test run needs to be executed on this page or not, so we can make it Static; Fitnesse will decide that the test run needs not to be executed for this page).
3. Suite: Suite is nothing but the group of Test pages, it basically is the way of keeping all the related Test Pages in one set and when we want a specific set of test cases to be executed we just run the test on the Suite instead of running test cases on each test page separately.

Now returning back to creating a new page, click on the"?" sign shown with your page name on the Front Page of Fitnesse. As soon as you will click on "?", your page will be opened. It's now time to provide some scripts on this page to run the test cases. Now we will see how to import your library that needs to be tested and how to create the Decision Table for executing the test cases. Although there are many scenarios that can exist with your test cases or your test cases need to be covered, it will not be possible to explain all of them. I will just be presenting you with a simple example and for other scenarios of yours, you can click on the link "User Guide" on the Front Page.

As soon as you open your new page it will present you with a Rich Text Editor for the configuration of the test libraries and to create Decision Tables, for doing the configuration on this page and to tell it the path of the test libraries (libraries that need to be tested, in my case it is Sample Library). So to make it easy and keep it separate from the development process, what we will do is create a folder named "Projects" (This name can be of your choice) at the same path where the Fitnesse JAR file is present. Now build your project and copy the DLL(s) of your project into this folder. This is done to keep things separate from the development process and also we can provide the relative path of this project's folder in the page configuration. (Relative paths are relative to the location of the JAR file.)

Add the following to your page to configure the path of the library and import a specific namespace in that library for which we will create the Decision Tables. This is also a Decision Table that we have created for the import, just to be very safe and to tell Fitnesse that the new Decision Table is getting started we added a "!" sign in the front of the first row of the table.

!path Projects\SampleLibrary.dll
!|import |
|SampleLibrary |

So here Path is the relative path of the DLL and the table row below the import row of the table tells the name of the namespace in that library. Now it's time to create a Decision Table for running your methods and see the expected results. See the code below for that.

| UserTest | 
| UserName  | Password | IsAuthenticated? | 
| "Abhishek" | "test" | true | 
| "Abhishek" | "Jain" | true |

So what is done in the above Decision Table is that the first row tells the name of the class, the second row specifies the sequence of the parameters or the properties of that class in the library, the order in which we provide the inputs since everything is separated by a Pipe ("|") in Fitnesse, the first parameter is Username and the second is the Password and the last one is the method that needs to be executed.

In the third row, we created the first set according to our scenarios, in which we are defining the property values and the final is the expected result. And yes we are done with the first test case, now it's time to execute it by saving this on the Test page.

Now just click on the "Test" button to run the test cases and you can see the results. Just see the sample Result Page.

Now here you can see that the result of both of my test cases is that they passed. With this I think I am done, please let me know if something is missing or if you need some more help on Fitnesse.