qmcpack

History

Mark Dewing be70f0b6a1 Merge remote-tracking branch 'upstream/develop' into fix_labels		2018-11-01 09:36:52 -05:00
..
converter	ctest: consolidate test labeling and apply to quantum espresso tests	2018-10-23 09:03:46 -04:00
coverage	Handle the negative count coverage case.	2018-03-14 10:54:08 -05:00
estimator	Output more information for estimator failures	2017-06-09 15:01:18 -05:00
heg	add test for J2 RPA	2018-02-08 10:20:00 -05:00
io	ctest: expand labeling to all tests	2018-10-08 13:08:40 -04:00
models	Move test checking scripts to a central location	2018-05-17 14:34:19 -05:00
molecules	Correct spelling errors across entire source	2018-10-10 19:58:16 -04:00
performance	Fix typos.	2018-10-29 14:54:17 -05:00
pseudopotentials_for_tests	Add pseudopotentials_for_tests and fix broken symlinks	2018-05-04 10:59:47 -04:00
pw2qmcpack	Fix pw2qmcpack tests.	2018-03-29 09:53:26 -05:00
scripts	Print cmd line args with test_label.py error	2018-10-25 17:25:20 -05:00
solids	ctest: consolidate and fix cpu limit and coverage tests	2018-10-22 16:16:26 -04:00
test_automation	Update BGQ toolchain name.	2018-10-31 16:47:27 -05:00
CMakeLists.txt	add test for J2 RPA	2018-02-08 10:20:00 -05:00
README	Enable plane wave tests for bccH. Only uses 100 blocks vs 1000 for spline case.	2016-12-18 22:52:18 +00:00

README

These directories contain input files for the automated test
system. They are not intended to be run separately although any
QMCPACK inputs should run to completion when run from the same
directory as the input, e.g. mpirun -n 16 qmcpack vmc.in.xml

To run the automated tests, from the build directory, run

ctest -R short

for the short running tests. These take a few minutes to run on a 16
core machine. To run all tests simply run

ctest

Running all tests requires several hours due to strict statistics. You
can increase verbosity with "ctest -V".

The test definitions and configuration are in
src/tests/system/CMakeLists.txt