Regression Tests

Running Regression Tests

Source code pushed to the master branch is expected to run cleanly through the regression tests, so developers should do an appropriate degree of testing ahead of time. The amount of testing needed will depend on the nature of the code changes. Small changes may require little or no testing, while larger additions may require running the full suite of regression tests in hypre. This page gives some information on how to do this.

Basics about the braid/test directory

For full instructions on regression testing, see braid/test/README.md

Essentially, you can run individual tests like

 cd braid/test/  
 ./diffusion2d.sh  

which will compile the code, run a battery of tests and report any fails in a new directory

 ./diffusion2d.dir

where the following command should return all zero sized files

 ll diffusion2D.dir/*err*

Individual Tests

Inside of the diffusion2D.dir directory, the expected output for a test is in

 diffusion2D.saved.0

while the actual output is in

 std.out.0

and the diff, i.e., error is in

 std.err.0

The raw output for a test is in

 unfiltered.std.out.0

Full Regression Tests

To run the full regression tests, do

 cd braid/test
 ./test.sh machine_mac.sh

and examine machine_mac.err and machine_mac.dir. But keep in mind that some of these have stored output to match Jacob's MacBook.