fUnit 0.0.1

data/INSTALL

@@ -0,0 +1,19 @@
+Prerequisites
+-------------
+
+ 1) A Fortran 90/95/2003 compiler.
+
+ 2) The Ruby language -- see http://www.ruby-lang.org/
+
+ 3) RubyGems package manager -- see http://rubyforge.org/projects/rubygems/
+
+
+Installation
+------------
+
+ gem install funit
+
+
+At some point, we plan to make installation easier by creating
+a single executable with Erik Veenstra's RubyScript2Exe
+<http://www.erikveen.dds.nl/rubyscript2exe/>.

data/LICENSE

@@ -0,0 +1,262 @@
+NASA OPEN SOURCE AGREEMENT VERSION 1.3
+
+THIS OPEN SOURCE AGREEMENT ("AGREEMENT") DEFINES THE RIGHTS OF USE,
+REPRODUCTION, DISTRIBUTION, MODIFICATION AND REDISTRIBUTION OF CERTAIN
+COMPUTER SOFTWARE ORIGINALLY RELEASED BY THE UNITED STATES GOVERNMENT
+AS REPRESENTED BY THE GOVERNMENT AGENCY LISTED BELOW ("GOVERNMENT
+AGENCY").  THE UNITED STATES GOVERNMENT, AS REPRESENTED BY GOVERNMENT
+AGENCY, IS AN INTENDED THIRD-PARTY BENEFICIARY OF ALL SUBSEQUENT
+DISTRIBUTIONS OR REDISTRIBUTIONS OF THE SUBJECT SOFTWARE.  ANYONE WHO
+USES, REPRODUCES, DISTRIBUTES, MODIFIES OR REDISTRIBUTES THE SUBJECT
+SOFTWARE, AS DEFINED HEREIN, OR ANY PART THEREOF, IS, BY THAT ACTION,
+ACCEPTING IN FULL THE RESPONSIBILITIES AND OBLIGATIONS CONTAINED IN
+THIS AGREEMENT.
+
+Government Agency: NASA Langley Research Center
+Government Agency Original Software Designation: LAR-17081-1
+Government Agency Original Software Title: fUnit
+User Registration Requested: please see clause 3.F.
+Government Agency Point of Contact: funit-support@rubyforge.org
+
+1. DEFINITIONS
+
+A. "Contributor" means Government Agency, as the developer of the
+   Original Software, and any entity that makes a Modification.
+
+B. "Covered Patents" mean patent claims licensable by a Contributor
+   that are necessarily infringed by the use or sale of its Modification
+   alone or when combined with the Subject Software.
+
+C. "Display" means the showing of a copy of the Subject Software,
+   either directly or by means of an image, or any other device.
+
+D. "Distribution" means conveyance or transfer of the Subject
+   Software, regardless of means, to another.
+
+E. "Larger Work" means computer software that combines Subject
+   Software, or portions thereof, with software separate from the Subject
+   Software that is not governed by the terms of this Agreement.
+
+F. "Modification" means any alteration of, including addition to or
+   deletion from, the substance or structure of either the Original
+   Software or Subject Software, and includes derivative works, as that
+   term is defined in the Copyright Statute, 17 USC 101.  However, the
+   act of including Subject Software as part of a Larger Work does not in
+   and of itself constitute a Modification.
+
+G. "Original Software" means the computer software first released
+   under this Agreement by Government Agency with Government Agency
+   designation NASA and entitled fUnit, including source code,
+   object code and accompanying documentation, if any.
+
+H. "Recipient" means anyone who acquires the Subject Software under
+   this Agreement, including all Contributors.
+
+I. "Redistribution" means Distribution of the Subject Software after a
+   Modification has been made.
+
+J. "Reproduction" means the making of a counterpart, image or copy of
+   the Subject Software.
+
+K. "Sale" means the exchange of the Subject Software for money or
+   equivalent value.
+
+L. "Subject Software" means the Original Software, Modifications, or
+   any respective parts thereof.
+
+M. "Use" means the application or employment of the Subject Software
+   for any purpose.
+
+2. GRANT OF RIGHTS
+
+A. Under Non-Patent Rights: Subject to the terms and conditions of
+this Agreement, each Contributor, with respect to its own contribution
+to the Subject Software, hereby grants to each Recipient a
+non-exclusive, world-wide, royalty-free license to engage in the
+following activities pertaining to the Subject Software:
+
+  1. Use
+  2. Distribution
+  3. Reproduction
+  4. Modification
+  5. Redistribution
+  6. Display
+
+B. Under Patent Rights: Subject to the terms and conditions of this
+Agreement, each Contributor, with respect to its own contribution to
+the Subject Software, hereby grants to each Recipient under Covered
+Patents a non-exclusive, world-wide, royalty-free license to engage in
+the following activities pertaining to the Subject Software:
+
+  1. Use
+  2. Distribution
+  3. Reproduction
+  4. Sale
+  5. Offer for Sale
+
+C. The rights granted under Paragraph B. also apply to the combination
+of a Contributor's Modification and the Subject Software if, at the
+time the Modification is added by the Contributor, the addition of
+such Modification causes the combination to be covered by the Covered
+Patents.  It does not apply to any other combinations that include a
+Modification.
+
+D. The rights granted in Paragraphs A. and B. allow the Recipient to
+sublicense those same rights.  Such sublicense must be under the same
+terms and conditions of this Agreement.
+
+3. OBLIGATIONS OF RECIPIENT
+
+A. Distribution or Redistribution of the Subject Software must be made
+under this Agreement except for additions covered under paragraph 3H.
+
+1. Whenever a Recipient distributes or redistributes the Subject
+    Software, a copy of this Agreement must be included with each copy
+    of the Subject Software; and
+
+2. If Recipient distributes or redistributes the Subject Software in
+    any form other than source code, Recipient must also make the
+    source code freely available, and must provide with each copy of
+    the Subject Software information on how to obtain the source code
+    in a reasonable manner on or through a medium customarily used for
+    software exchange.
+
+B. Each Recipient must ensure that the following copyright notice
+appears prominently in the Subject Software:
+
+  Copyright 2006 United States Government as represented by
+  NASA Langley Research Center. No copyright is claimed in
+  the United States under Title 17, U.S. Code. All Other Rights
+  Reserved.
+
+C. Each Contributor must characterize its alteration of the Subject
+Software as a Modification and must identify itself as the originator
+of its Modification in a manner that reasonably allows subsequent
+Recipients to identify the originator of the Modification.  In
+fulfillment of these requirements, Contributor must include a file
+(e.g., a change log file) that describes the alterations made and the
+date of the alterations, identifies Contributor as originator of the
+alterations, and consents to characterization of the alterations as a
+Modification, for example, by including a statement that the
+Modification is derived, directly or indirectly, from Original
+Software provided by Government Agency. Once consent is granted, it
+may not thereafter be revoked.
+
+D. A Contributor may add its own copyright notice to the Subject
+Software.  Once a copyright notice has been added to the Subject
+Software, a Recipient may not remove it without the express permission
+of the Contributor who added the notice.
+
+E. A Recipient may not make any representation in the Subject Software
+or in any promotional, advertising or other material that may be
+construed as an endorsement by Government Agency or by any prior
+Recipient of any product or service provided by Recipient, or that may
+seek to obtain commercial advantage by the fact of Government Agency's
+or a prior Recipient's participation in this Agreement.
+
+F. In an effort to track usage and maintain accurate records of the
+Subject Software, each Recipient, upon receipt of the Subject Software,
+is requested to provide Government Agency, by e-mail to the Government
+Agency Point of Contact listed in clause 5.F., the following information:
+name, institution (if applicable), postal code, and country.
+Recipient's name and personal information shall be used for statistical
+purposes only. Once a Recipient makes a Modification available, it is
+requested that the Recipient inform Government Agency, by e-mail to the
+Government Agency Point of Contact listed in clause 5.F., how to
+access the Modification.
+
+G. Each Contributor represents that that its Modification is believed
+to be Contributor's original creation and does not violate any
+existing agreements, regulations, statutes or rules, and further that
+Contributor has sufficient rights to grant the rights conveyed by this
+Agreement.
+
+H. A Recipient may choose to offer, and to charge a fee for, warranty,
+support, indemnity and/or liability obligations to one or more other
+Recipients of the Subject Software.  A Recipient may do so, however,
+only on its own behalf and not on behalf of Government Agency or any
+other Recipient.  Such a Recipient must make it absolutely clear that
+any such warranty, support, indemnity and/or liability obligation is
+offered by that Recipient alone.  Further, such Recipient agrees to
+indemnify Government Agency and every other Recipient for any
+liability incurred by them as a result of warranty, support, indemnity
+and/or liability offered by such Recipient.
+
+I. A Recipient may create a Larger Work by combining Subject Software
+with separate software not governed by the terms of this agreement and
+distribute the Larger Work as a single product. In such case, the
+Recipient must make sure Subject Software, or portions thereof,
+included in the Larger Work is subject to this Agreement.
+
+J. Notwithstanding any provisions contained herein, Recipient is
+hereby put on notice that export of any goods or technical data from
+the United States may require some form of export license from the
+U.S. Government.  Failure to obtain necessary export licenses may
+result in criminal liability under U.S. laws.  Government Agency
+neither represents that a license shall not be required nor that, if
+required, it shall be issued.  Nothing granted herein provides any
+such export license.
+
+4. DISCLAIMER OF WARRANTIES AND LIABILITIES; WAIVER AND INDEMNIFICATION
+
+A. No Warranty: THE SUBJECT SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY
+WARRANTY OF ANY KIND, EITHER EXPRESSED, IMPLIED, OR STATUTORY,
+INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY THAT THE SUBJECT SOFTWARE
+WILL CONFORM TO SPECIFICATIONS, ANY IMPLIED WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR FREEDOM FROM
+INFRINGEMENT, ANY WARRANTY THAT THE SUBJECT SOFTWARE WILL BE ERROR
+FREE, OR ANY WARRANTY THAT DOCUMENTATION, IF PROVIDED, WILL CONFORM TO
+THE SUBJECT SOFTWARE. THIS AGREEMENT DOES NOT, IN ANY MANNER,
+CONSTITUTE AN ENDORSEMENT BY GOVERNMENT AGENCY OR ANY PRIOR RECIPIENT
+OF ANY RESULTS, RESULTING DESIGNS, HARDWARE, SOFTWARE PRODUCTS OR ANY
+OTHER APPLICATIONS RESULTING FROM USE OF THE SUBJECT SOFTWARE.
+FURTHER, GOVERNMENT AGENCY DISCLAIMS ALL WARRANTIES AND LIABILITIES
+REGARDING THIRD-PARTY SOFTWARE, IF PRESENT IN THE ORIGINAL SOFTWARE,
+AND DISTRIBUTES IT "AS IS."
+
+B. Waiver and Indemnity: RECIPIENT AGREES TO WAIVE ANY AND ALL CLAIMS
+AGAINST THE UNITED STATES GOVERNMENT, ITS CONTRACTORS AND
+SUBCONTRACTORS, AS WELL AS ANY PRIOR RECIPIENT.  IF RECIPIENT'S USE OF
+THE SUBJECT SOFTWARE RESULTS IN ANY LIABILITIES, DEMANDS, DAMAGES,
+EXPENSES OR LOSSES ARISING FROM SUCH USE, INCLUDING ANY DAMAGES FROM
+PRODUCTS BASED ON, OR RESULTING FROM, RECIPIENT'S USE OF THE SUBJECT
+SOFTWARE, RECIPIENT SHALL INDEMNIFY AND HOLD HARMLESS THE UNITED
+STATES GOVERNMENT, ITS CONTRACTORS AND SUBCONTRACTORS, AS WELL AS ANY
+PRIOR RECIPIENT, TO THE EXTENT PERMITTED BY LAW.  RECIPIENT'S SOLE
+REMEDY FOR ANY SUCH MATTER SHALL BE THE IMMEDIATE, UNILATERAL
+TERMINATION OF THIS AGREEMENT.
+
+
+5. GENERAL TERMS
+
+A. Termination: This Agreement and the rights granted hereunder will
+terminate automatically if a Recipient fails to comply with these
+terms and conditions, and fails to cure such noncompliance within
+thirty (30) days of becoming aware of such noncompliance.  Upon
+termination, a Recipient agrees to immediately cease use and
+distribution of the Subject Software.  All sublicenses to the Subject
+Software properly granted by the breaching Recipient shall survive any
+such termination of this Agreement.
+
+B. Severability: If any provision of this Agreement is invalid or
+unenforceable under applicable law, it shall not affect the validity
+or enforceability of the remainder of the terms of this Agreement.
+
+C. Applicable Law: This Agreement shall be subject to United States
+federal law only for all purposes, including, but not limited to,
+determining the validity of this Agreement, the meaning of its
+provisions and the rights, obligations and remedies of the parties.
+
+D. Entire Understanding: This Agreement constitutes the entire
+understanding and agreement of the parties relating to release of the
+Subject Software and may not be superseded, modified or amended except
+by further written agreement duly executed by the parties.
+
+E. Binding Authority: By accepting and using the Subject Software
+under this Agreement, a Recipient affirms its authority to bind the
+Recipient to all terms and conditions of this Agreement and that that
+Recipient hereby agrees to all terms and conditions herein.
+
+F. Point of Contact: Any Recipient contact with Government Agency is
+to be directed to the designated representative as follows:
+funit-support@rubyforge.org.

data/README

@@ -0,0 +1,3 @@
+fUnit - a Fortran Unit Testing Framework
+
+See docs/ for more information.

data/bin/funit

@@ -0,0 +1,8 @@
+begin
+  require 'funit'
+rescue LoadError
+  require 'rubygems'
+  require 'funit'
+end
+include Funit
+Funit::runAllFtks 

data/docs/HISTORY

@@ -0,0 +1,20 @@
+$Id: HISTORY 112 2006-04-05 11:23:45Z kleb $
+
+A BRIEF HISTORY
+
+On October 4, 2001, Mike Hill of Object Mentor, Inc. visited NASA
+Langley Research Center in Hampton, Virginia and gave a test-first
+design talk at Institute for Computer and Applied Sciences and
+Engineering (ICASE).
+
+Mike spent the afternoon with Bil Kleb, Bill Wood, Karen Bibb,
+and Mike Park reasoning out how we might create a testing framework
+for Fortran 90.  By the end of the afternoon we had a working
+protoype based on the macro expansion techniques employeed in
+Mike's own cpptestkit.
+
+The basic idea is that test routines should easily be written in 
+a psuedo-Fortran style (i.e., very lightweight), processed (via
+the c preproccesor or a script) into valid Fortran90, collected, and
+invoked by a dynamically-created/compiled/ linked/run Fortran90 code
+named testrunner.

data/docs/spiel/slides.tex

@@ -0,0 +1,153 @@
+% $Id: slides.tex 112 2006-04-05 11:23:45Z kleb $
+
+% Previewing and making Postscript version:
+%  latex slides
+%  xdvi -papertype usr slides
+%  dvips -t landscape -o slides.ps slides
+%  gv -seascape slides.ps [optional]
+
+% Making and previewing a PDF version:
+%  pdflatex slides
+%  acroread slides.pdf
+
+\documentclass[landscape]{slides}
+\usepackage{url}
+\pagestyle{empty}
+\hoffset 1in
+\begin{document}
+\begin{slide}
+ \begin{center}
+  {\bf\Large F90 Testkit}\\
+  \vspace{0.5in}
+  \begin{minipage}{6.5in}
+    {\bf Goal:} to make Fortran~90 unit/\-mobility/\-developer testing
+    as painless as possible.
+  \end{minipage}
+ \end{center}
+\end{slide}
+\begin{slide}
+  \begin{center}
+    {\bf\Large Why write tests?}\\
+    \vspace{0.5in}
+    \begin{minipage}[t]{3in}
+     \begin{itemize}
+      \item Shame
+      \item Embarrassment
+      \item Speed
+      \item Confidence
+     \end{itemize}
+    \end{minipage}
+    \begin{minipage}[t]{3in}
+     \begin{itemize}
+      \item Trust
+      \item Change
+      \item Documentation
+     \end{itemize}
+    \end{minipage}
+  \end{center}
+\end{slide}
+\begin{slide}
+  \begin{center}
+    {\bf\Large Why write tests first?}\\
+    \vspace{0.5in}
+    \begin{minipage}{3in}
+    \begin{itemize}
+     \item Tests get written
+     \item Succinctness
+     \item Clarity
+     \item Closure
+    \end{itemize}
+    \end{minipage}\\
+    \vspace{1in}
+    \begin{minipage}{5.7in}\raggedright
+      ``No code should be written or changed unless there is a failing
+      test.''
+    \end{minipage}
+  \end{center}
+\end{slide}
+\begin{slide}
+  \begin{center}
+   {\bf\Large How do I add tests to legacy code?}\\
+   \vspace{0.5in}
+   \begin{minipage}{6in}
+    \begin{itemize}
+     \item Fixing Bugs
+      \begin{itemize}
+       \item write test for bug {\small (which fails)}
+       \item write code to satisfy failing test
+       \item write tests/code for similar cases
+      \end{itemize}
+      \vspace{8pt}
+     \item Adding Features
+      \begin{itemize}
+       \item write test for feature {\small (which better fail)}
+       \item write code to satisfy failing test
+      \end{itemize}
+      \vspace{8pt}
+     \item Refactoring ``Bad Smells''
+      \begin{itemize}
+       \item write tests to cover existing code
+       \item update/add tests for new structure
+       \item change code to satisfy failing tests
+      \end{itemize}
+    \end{itemize}
+   \end{minipage}
+  \end{center}
+\end{slide}
+\begin{slide}
+  \begin{center}
+    {\bf\Large Crazy enough to learn more?}\\
+    \vspace{0.5in}
+    \begin{minipage}{6in}
+     \begin{itemize}
+      \item \url{http://c2.com/cgi/wiki?UnitTests}\\[-10pt]
+      \item \url{http://xprogramming.com/software.htm}
+     \end{itemize}
+    \end{minipage}
+  \end{center}
+\end{slide}
+\begin{slide}
+  \begin{center}
+    {\bf\Large Want to try F90 testkit?}\\
+    \vspace{0.5in}
+    \begin{minipage}{9in}
+     \begin{itemize}
+      \item Have your SA install Ruby {\small(or install it yourself)}\\[5pt]
+       \hspace*{1em}\url{http://www.ruby-lang.org/}\\[5pt]
+      \item Check out the FTK repository\\[5pt]
+       \hspace*{1em}\verb+cvs -d :pserver:[username]@abnode3:/usr/local/cvsroot \+\\
+       \hspace*{1em}\verb+checkout -P FTK+\\[5pt]
+       where \verb+[username]+ is your CVS username on \verb+abnode3+
+     \end{itemize}
+    \end{minipage}
+  \end{center}
+\end{slide}
+\begin{slide}
+  \begin{center}
+    {\bf\Large Who does what?}\\
+    \vspace{0.5in}
+    {\bf You:}
+    \begin{minipage}[t]{6.5in}\raggedright
+     \begin{enumerate}
+      \item Create testsuite file, e.g., \verb+RoutineTS.ftk+
+      \item Write test in Fortran with embedded assert macros, .e.g,
+        \verb+IsTrue(x>2)+
+      \item Run testsuite {\small (it should fail)}
+      \item Write \verb+Routine.f90+ to satisfy test
+     \end{enumerate}
+     \vspace{10pt}
+     Repeat steps 2, 3, and 4 until your objective is met.
+    \end{minipage}\\
+    \vspace{0.8in}
+   {\bf It:}
+   \begin{minipage}[t]{6in}\raggedright
+   Translates, compiles, links, and runs tests.
+   \end{minipage}
+  \end{center}
+\end{slide}
+\end{document}
+
+%%% Local Variables: 
+%%% mode: latex
+%%% TeX-master: t
+%%% End: 

data/docs/why/F90testRun

@@ -0,0 +1,43 @@
+% F90test
+
+parsing GasModelTS.ftk
+parsing FluxFunctionsTS.ftk
+
+ *Warning: no asserts in test [GasModelTS.ftk:13]
+completed GasModelTS.ftk
+completed FluxFunctionsTS.ftk
+
+
+Compiling file Gammas.f90.
+Encountered 0 errors, 0 warnings in file Gammas.f90.
+Compiling file GasModel.f90.
+Encountered 0 errors, 0 warnings in file GasModel.f90.
+Compiling file FluxFunctions.f90.
+Encountered 0 errors, 0 warnings in file FluxFunctions.f90.
+Compiling file GasModelTS.f90.
+Encountered 0 errors, 0 warnings in file GasModelTS.f90.
+Compiling file FluxFunctionsTS.f90.
+Encountered 0 errors, 0 warnings in file FluxFunctionsTS.f90.
+Compiling file TestRunner.f90.
+Encountered 0 errors, 0 warnings in file TestRunner.f90.
+Linking:
+ 
+ GasModel test suite:
+ Passed 5 of 5 possible asserts comprising 3 of 3 tests.
+ 
+ FluxFunctions test suite:
+  *IsFalse failed* in test RoeAvgZero [FluxFunctionsTS.ftk:23]
+    RoeAvg(0.0,0.0).ne.1  is not false
+ 
+  *IsTrue failed* in test RoeAvgKnown [FluxFunctionsTS.ftk:28]
+    RoeAvg(leftState,rightState).lt.0  is not true
+ 
+  *IsEqualWithin failed* in test CentralFluxKnown [FluxFunctionsTS.ftk:33]
+    interfaceFlux ( 0.250000000 ) is not 0.500000000 within 1.00000005E-03
+ 
+  *IsEqual failed* in test RoeFluxExpansionShock [FluxFunctionsTS.ftk:41]
+    interfaceFlux ( 0.500000000 ) is not 0
+ 
+ Passed 6 of 12 possible asserts comprising 3 of 7 tests.
+ 
+%