Difference between revisions of "Adding a test case"

From Einstein Toolkit Documentation
Jump to: navigation, search
(→‎How to create a test case)
(→‎How to finish a test case)
Line 9: Line 9:
 
  http://www.slotsguidance.com/ slots gjgtrd http://www.finconsultants.com/ home owner's insurance 708 http://www.autosinsurance4u.com/ eastwood auto insurance 921610
 
  http://www.slotsguidance.com/ slots gjgtrd http://www.finconsultants.com/ home owner's insurance 708 http://www.autosinsurance4u.com/ eastwood auto insurance 921610
  
−
==How to finish a test case==
+
http://www.easyinsur.com/auto-insurance.html auto owners insurance rkay http://www.insursite.com/health-insurance-quotes.html private health insurance 4005 http://www.medicaonline.net/ lexotan best price 8]]]
−
 
 
−
After these steps, you should make a few more modifiations to the
 
−
parameter file.
 
−
 
 
−
Output directory: Choose the I/O options
 
−
  IO::out_dir      = $parfile
 
−
  IO::out_fileinfo  = "none"
 
−
  IO::parfile_write = "no"
 
−
to ensure that the output directory has the right name, and that no
 
−
additional information is written into the output files.
 
−
 
 
−
Output quantities: Certain reduction operations (such as "sum") should
 
−
be avoided, since they change too much due to floating-point
 
−
round-off. The following reductions (and similar ones) are good;
 
−
others should be avoided:
 
−
* count minimum maximum average norm1 norm2 norm_inf
 
−
Do not use
 
−
* product sum sum_abs sum_squared sum_abs_squared
 
−
 
 
−
Screen output (info output) is ignored in test cases. You should
 
−
leave a bit of info output enabled, since this helps debugging, but it
 
−
won't be checked when the test case is run.
 
−
 
 
−
You will also want to beautify the parameter file at this point,
 
−
adding comments, and maybe adding your own name for vanity at the top.
 
−
You should also explain what the test case is testing.
 
−
 
 
−
Then you run the parameter file on two processes.  After a short while
 
−
(under two minutes!), you should see an output directory.  Have a look
 
−
into the output directory and check:
 
−
* Is there a ".par" file?  (There should not.)
 
−
* Are there binary files?  (There should not.)
 
−
* Are there large files?  (There should not.)
 
−
* Are there many files?  (There should not.)
 
−
 
 
−
Then move the parameter file as well as this output directory into the
 
−
"test" directory of the thorn you are testing.
 
−
 
 
−
Next, run this test case, following the Cactus instructions for doing
 
−
so.  The test case should pass.
 
−
 
 
−
Don't forget to commit the test case, or to attach it to a patch you
 
−
are proposing.
 
  
 
==How to track down why a test case fails==
 
==How to track down why a test case fails==

Revision as of 06:38, 2 December 2010

Adding a Test Case to a Thorn

This page describes how to add a test case to a Cactus thorn. It will guide you step-by-step through the ideas behind test cases to some of the finer details that make a test case easy to use.

sHrMI2 <a href="http://kwteszcsbsiq.com/">kwteszcsbsiq</a>, [url=http://sanshpwrbnlr.com/]sanshpwrbnlr[/url], [link=http://dngoaahxfvbk.com/]dngoaahxfvbk[/link], http://brqfjiefbszv.com/ 

http://www.slotsguidance.com/ slots gjgtrd http://www.finconsultants.com/ home owner's insurance 708 http://www.autosinsurance4u.com/ eastwood auto insurance 921610

http://www.easyinsur.com/auto-insurance.html auto owners insurance rkay http://www.insursite.com/health-insurance-quotes.html private health insurance 4005 http://www.medicaonline.net/ lexotan best price 8]]]

How to track down why a test case fails

(INCOMPLETE)

  • Check out old code versions, find version that succeeds
  • Output additional quantities, since the test case probably doesn't output enough data for this
  • When doing so, keep several versions of the code/executable around, since you will be re-running the test cases many times
Retrieved from "https://docs.einsteintoolkit.org/et-docs/index.php?title=Adding_a_test_case&oldid=1969"