File | Date | Author | Commit |
---|---|---|---|
Fixtures | 2018-10-15 | Jac. @rabojac.local | [f3164d] Introduction of BasicTruncate |
config | 2018-06-11 | Jac. @rabojac.local | [0ea244] Initial commit |
gradle | 2018-06-11 | Jac. @rabojac.local | [0ea244] Initial commit |
linuxscripts | 2018-06-11 | Jac. @rabojac.local | [0ea244] Initial commit |
.gitattributes | 2018-06-11 | Jac. @rabojac.local | [0ea244] Initial commit |
.gitignore | 2018-08-08 | Jac. @rabojac.local | [d3dc53] insertData testpages |
CODE_OF_CONDUCT.md | 2018-06-11 | Jac. @rabojac.local | [0ea244] Initial commit |
LICENSE | 2018-06-11 | Jac. @rabojac.local | [0ea244] Initial commit |
README.md | 2018-10-15 | Jac. @rabojac.local | [9c1875] removed invalid web links |
The FitNesse Fixtures are created as part of an overall solution for automating the test cycle.
The readme for Linux can be found in the directory 'linuxscripts', here on github: https://github.com/consag/fitnessefixtures/tree/master/linuxscripts
You can download the jar with all compiled fixtures from the release tab.
Check the properties files, Properties files on gist, here on github with examples for the fixture.properties, application.properties and other important properties files.
Fixtures rely on various parameters that need to be set up in properties files. Not all fixtures use all properties files.
Check our wiki for more information.
If you're wondering what you need to put in the properties files, check out our examples on GitHub Gist.