peterdemin: переводы

→{{refimprove|date=August 2012}}
{{ infobox software
| name = FitNesse
| developer =
| latest release version = v20130530
| latest release date = {{Start date and age|2013|05|30}}
| operating system = [[Cross-platform]]
| genre = [[Test automation]]
| license = [[Common Public License|CPL]] <ref name=licenseheader>{{cite web|last=Martin|first=Robert C.|title=License Header|url=https://github.com/unclebob/fitnesse/blob/master/licenseHeader.txt|work=FitNesse Source Repository|publisher=GitHub|accessdate=4 July 2012}}</ref>
| status = Active
| website = http://www.fitnesse.org/
}}

→[[Category:Groupware]]
[[Category:Software testing tools]]

→==External links==
* [http://www.fitnesse.org Tool website]
* [https://github.com/unclebob/fitnesse|Source Repository]
* [http://www.fitnesse.org/FrontPage.FitServers Languages supported by FitNesse]
* [http://fitnesse.info/ Alternative download site and a list of FitNesse related resources]
* [http://tech.groups.yahoo.com/group/fitnesse Discussion group dedicated to FitNesse]
* [http://www.methodsandtools.com/tools/tools.php?fitnesse FitNesse presentation]

→<references />

→==References==

→==Books==
* [http://safari.phptr.com/0321269349 Fit for Developing Software: Framework for Integrated Tests] by Rick Mugridge; Ward Cunningham (ISBN 978-0-321-26934-8) published by Prentice Hall in June 2005
* [http://www.amazon.com/dp/0955683602 Test Driven .NET Development with FitNesse] by [[Gojko adzic|Gojko Adzic]] (ISBN 978-0-9556836-0-2) published by Neuri Limited (February 28, 2008)
* Phillip A. Laplante: Requirements Engineering for Software and Systems, Auerbach Publications, Boca Raton, FL, 2009, pp. 166-167, ISBN 978-1420064674

→*[[Specification by example]]
*[[Acceptance testing]] (also referred to as functional testing)
*[[Software performance testing]]
*[[Regression testing]]
*[[Watir]]
* StoryTestIQ (STIQ) a mash-up of Selenium and the Fitness wiki (Please note: Wikipedia does not exist anymore (deleted in 2009), left here for reference only)

→==See also==
{{portal|Software Testing}}

→The SLIM engine allows for far more light-weight fixtures which are simple [[POJO]]s. These fixtures are not required to extend or use any framework classes, which simplifies their design and allows the fixture designer to concentrate on calling the system under test properly and in the simplest way possible. It also keeps the inheritance route open, allowing fixture developers to create fixture hierarchies if necessary.

→====SLIM====
SLIM (Simple List Invocation Method) is an alternative to Fit.
The SLIM engine is an implementation of the [http://fitnesse.org/FitNesse.UserGuide.SliM.SlimProtocol Slim Protocol]. Rather than combining all the elements of wiki-based testing, the SLIM engine concentrates only on invoking the fixture; it runs as a separate server which is invoked remotely by the FitNesse wiki engine. The interpretation of the wiki page and the generation of the result page is now part of the wiki engine.

→FIT is a framework that combines many responsibilities in testing rather than separating responsibilities neatly. The software developer pays a price for this fact in that fixtures for the FIT engine must inherit from FIT framework base classes. This can be inconvenient in Java, as it means that the framework claims a developers one chance at class inheritance. It also means that a fixture, by its nature, is a heavyweight construct. These considerations have prompted the FitNesse team in recent years to move to the SLIM testing engine.

→====FIT====
More than an engine, FIT is a testing framework unto itself. It combines functionality to invoke tests, interpret wiki pages and generate output pages. FitNesse was originally built around FIT as a user interface, which inspired the name of the tool.

→===Testing engines===
The actual mapping as described above (as well as the invocation of fixture methods) is done by a testing engine. FitNesse supports two of these engines: the FIT engine and the SLIM engine.

→The mapping between the wiki page and the fixture is a straightforward [[camel case|convert-to-camel case]] mapping. This mapping applies to all table headings and is used to identify the name of the fixture class as well as the methods of the fixture. A heading ending in a question mark is interpreted as a value to be read from the fixture, other headers are considered inputs to the fixture. Methods of the fixture are called in column order of the decision table, from left to right.

→public double result() {
return SystemUnderTest.divide (num, denom);
}
}</syntaxhighlight>

→public void setDenominatorValue (double denominator) {
denom = denominator;
}

→public void setNumeratorValue (double numerator) {
num = numerator;
}

→<syntaxhighlight lang="java">public class DivisionComponentTest extends ColumnFixture{
private double num;
private double denom;

→The link between the generic testing engine and the system under test is made by a piece of Java code called a fixture. In the case of the table above this code might look like this:

→{| class="wikitable"
! colspan="3" | Division component test
|-
!numerator value!!denominator value!!result?
|-
|10||2||5.0
|-
|10||5||2.0
|-
|5||2||2.5
|}