Menu
We are trying to use Fitnesse for our Functional test. Should i be mocking dependencies or should it be testing against the database?
What are the Pros/Cons of either of the approach?
The whole issue of testing against the DB is setting up data which is huge dependency. If we mock then is it real functional test?
Thanks
670
FitNesse is a web server, a wiki and an automated testing tool for software. It is based on Ward Cunningham's Framework for Integrated Test and is designed to support acceptance testing rather than unit testing in that it facilitates detailed readable description of system function.
Script table is a series of actions and checks that are similar to Do Fixture. The first row of script table starts with word “Script” followed by the name of the fixture (known as the “actor”) and it's constructor arguments that will be used by the rest of the table.
'' variable defined: PagePATH=''! -PagePath-! ''
We have a full set of end to end functional tests that run in fitnesse in two modes: "InMemory" and "Database", Depending on which configuration to run the tests in dictates which repositories the tests use. This has several advantages:
1) It keeps the developers from building a lot of functionality into the database and keeps in in the code.
2) When "In-Memory" the fitnesse tests run very very fast. Allowing the tests to fail very very fast...and thus speed up development and agility. When they run in db mode only they do take some time.
188
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
