Skip to content

A single-file object-oriented unit testing utility for Coarray Fortran.

License

Notifications You must be signed in to change notification settings

renatomatz/cafut

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

cafut

The point of this library is to provide a simple, object-oriented unit testing framework meant for applications using Coarray Fortran. As it is further developped, we place more importance in brevity than to features, and for that reason, this project aims at maintaining all code within a single module that can be placed with the tested scripts.

Other unit testing frameworks for Fortran (that I know of) give unorganized outputs when the program is meant to run in parallel using Coarrays. This ultimately comes down to coordinating test results amongst images such that test summaries are more organized and informative when it comes to the results of each image. Workarounds that revolve around adapting tests to immitate parallel behavior will run slower and everything else that made you want to write a parallel program in the first place.

Setup

To use cafut to its fullest, your compiler must have implemented Fortran Coarrays. In the examples shown bellow, I will be using OpenCoarrays, though there are several other options available.

If you wish to compile cafut for testing with a single image (such as using cafut for sequential programs), you can add the -fcoarray=single flag to gcc in order to compile the program.

Quick and Dirty

If you want to use cafut for some quick tests on a specific file, start by cloning cafut and generating the necessary .mod file with:

git clone https://github.com/renatomatz/cafut.git
cd cafut/src/
caf -c cafut.f90

where caf is the OpenCoarray compiler for using cafut with multiple images.

Then, just add the cafut.mod file, which should be an output from the above command, to the same directory that the program you wish to test is located. To use cafut, simply add use cafut to the test program.

Fortran Package Manager (fpm)

To use cafut for testing in your fpm project without making it a build dependency, just add the following to your package manifest file (fpm.toml) under the relevant test descriptions (which in the example bellow, we call main):

[[ test ]]
name="main"
source-dir="test/"
main="main.f90"
[test.dependencies]
cafut = { git = "https://github.com/renatomatz/cafut.git" }

You can then use the package in your testing programs with use cafut.

Examples

This framework centers around creating a linked list of unit tests. The two principal objects of the framework are the TestSuite, which is the first node of the linked list, and types extending the Test abstract type, which are the nodes of the list. In other words, the TestSuite type contains any number of Test objects, which it will execute and collect data from.

To create a new test suite, simply instanciate a TestSuite object, giving it an appropriate name.

ts = TestSuite("TEST 1")

There are two ways to add new tests to a TestSuite object. One is to create and set up a Test instance externally and then add said the instance to the test suite.

trv = TestRealVal("subtest 1.2")
trv%res = 1. + 1.
trv%tgt = 2.
call ts%add(trv)

The other is to add a test directly into the test suite by using one of the subroutines linked to the add generic procedure. To do this, just specify the new Test instance (which must be constructed with a name) as the first argument to the add procedure followed by the required arguments.

call ts%add(TestRealVal("subtest 1.1"), 1.+1., 2.)

NOTE that tests which involve arrays which are created externally must allocate the relevant attributes externally as well.

trav = TestRealArrVal("subtest 1.3")
allocate(trav%res(2), trav%tgt(2))
trav2%res = [1., 1.]
trav2%tgt = [2., 2.]
call ts%add(trav)

About

A single-file object-oriented unit testing utility for Coarray Fortran.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published