This document provides information about FitNesse, a software collaboration and testing tool. It discusses acceptance testing and different types. It then describes what FitNesse is, how it works as a wiki and with different programming languages. The document outlines FitNesse's architecture using wiki pages, a testing engine, test fixtures, and the system under test. It also discusses the FIT and Slim testing engines and how fixtures interface between FitNesse tables and the system being tested.

1. FitNesse
Achini Jayasena
Chalana Kahadawala

2. Acceptance Testing
Performed to determine whether or not the software system
has met the requirement specifications.
The main purpose is to evaluate the system's compliance with
the business requirements and verify if it is has met the
required criteria for delivery to end users.
 There are various forms of acceptance testing:
- User acceptance Testing
- Business acceptance Testing
- Alpha Testing
- Beta Testing

3. Fitnesse
 What is it?
 Software collaboration tool
 Communication tool
 Software testing tool
 Wiki
 Work with java, C#, python and smalltalk
 Use
 Automated Functional testing
 Integration testing

4. Fit/Fitnesse
 Framework for Integrated Testing
 FitNesse is wiki using FIT.

5. Comparison
 Tests are written before the code, so this approach
supports TDD i.e Test Driven Development
 Open source
 Execution of the tests can be automated.
 Test are deterministic.
 Increase the business value.

6. Architecture
 Testing within the FitNesse system involves four components
per test
 The wiki page which expresses the test as a decision
table.
 A testing engine, which interprets the wiki page.
 A test fixture, which is invoked by the testing engine and in
turn invokes the system under test.
 The system under test, which is being tested

7. Testing engines
 FIT- Framework for Integrated Testing
 An engine that processes each table using the Fixture
Code
 FitNesse is the tool that display the result of the Fit test
 Fit test may not be run on all platforms
 SLIM - Simple Invocation method
 All tables are processes in FitNesse
 The slim Executor to break down the test into simple
instructions and the Slim Runner then uses the fixtures to
call the system
 Test can work on all platforms

8. Fit inside the FitNesse

9. Slim inside the FitNesse

10. Fixture, What?
Fit(Nesse) and Fixtures
 Fit need hooks to the software under test; these hooks are
called Fixtures
 Think of a fixture as sort of a view/controller or user interface.
 Fixture translates the text in a table to function calls in the
software.

12. How does it work
• Download fitnesse.jar and fitNesselibrary.jar
http://fitnesse.org/FitNesseDownload
 Configuration
Java –jar fitnesse.jar –p 8080

13. Thank you