- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
Thanks for the reply. I read the page you linked to and I didn't really get what Iwas looking forso let me ask the question in a different way.
This is how I am approaching the issue: I've been using NUnit (http://nunit.org) and I am considering VBUnit (http://vbunit.org) and I would like to find a similar thing to use with Fortran. These are all based off the xUnit & JUnit testing frameworks.
What I would like to do is have a framework where I could make a routine that runs a function and then makes an assertion about the result. A console runner or a GUI would run through these tests sequentially in the compiled code and report upon which tests passed and which tests failed.
The tests that I want are fine-grained - I already have application functional tests that measure whole process results. The tools that you pointed to talk about issues like coverage and test quality and optomization. I am not ready for that. I just need *some* tests. Where are the tests that it refers to?
At one point there are the words
"An example of the usage model above is described in steps below using a hypothetical 32-bit Windows-based application called myApp.c:"
and thenone step is:
"Invocation of this command runs the instrumented application and generates one or more new dynamic profile information files that have an extension .dyn in the directory specified by PROF_DIR."
That looks like a test is applied to the whole application. I really have no clue what is supposed to be happening but I get the feeling that the tool then reports how much of the code is being run (and istherefore tested). I have no idea ofhow that test is constructed and maybe this is what I need to know. I want to test the smallest piece of functionality that I can manage to isolate into a routine. To me, that is the essence of Unit Testing and I want something to help me easily make the assertions in code and then run through them all and report.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- New task: Need new function
- Write only the interface to a new function
- Writeroutine(s) testing expected results from function
- Run unit test(s) BAM and see fail as expected :smileyhappy:
- Write code in new function
- Run unit test(s) BAM see most pass but maybe some fail :smileymad:
- Write better code in new function
- Run unit testsBAM see all green lights for success :smileyhappy:
- Move on to next task or refactor current work
![](/skins/images/BC9A7A3465121B56B278007F4EE8899F/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page