#1 Failed assert prints extra garbage, tests outdated
Following the example here: http://fortranxunit.wiki.sourceforge.net/Installation+Guide specifically step 6, a number of tests fail (haven't checked the source yet to see if they should) and when they fail, or are initialized some garbage gets printed. Also, your wiki documentation is a good start but the English is poor and some of the documentation apparently does not reflect the current state of the code. Also, the tests included in v 2.6 generate a ton of spurious warnings, it appears you have changed the names of the various methods/functions (and provided backwards compatibility) but never updated them in your examples. I have attached the output from building the default target with rake (i.e. user@host$ rake ) which executes all the tests. This illustrates my point about the aut of date test source files and the spurious 'end to reallocate' messages. Also following the add fruit to your diet in 3 minutes example generates these spurious end to reallocate messages. i.e.:
Test module initialized
. : successful assert, F : failed assert
end to reallocate
F
Start of FRUIT summary:
Some tests failed!
-- Failed assertion messages:
[_not_set_]: Expected [4], Got [0]
-- end of failed assertion messages.
Total asserts : 1
Successful : 0
Failed : 1
Successful rate: 0.00%
Successful asserts / total asserts : [ 0 / 1 ]
Successful cases / total cases : [ 0 / 0 ]
-- end of FRUIT summary
Also consider adding fruit to the ruby gems package manager.
I am seriously contemplating using this tool for my unit testing framework, but it seems in its current state it is quite buggy. This is ironic for a unit testing harness which is supposed to be used for TDD. You need to sort out these bugs and documentation issues before I or anyone else will actually be able to use your software.
output from executing 'rake' without arguments to build and execute example tests.