CP2K Open Source Molecular Dynamics

User Tools

Site Tools

Trace:
dev:regtesting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
dev:regtesting [2015/11/18 09:37] – Add a note about -j in make test rivanvxdev:regtesting [2018/10/08 19:59] – oschuett
Line 1: Line 1:
 ====== CP2K Regression Testing ====== ====== CP2K Regression Testing ======
  
-CP2K comes with over 2500 test input files (located in [[src>cp2k/tests]]) which serve as both examples on how to use the many features in CP2K and also as a method for developers to test modifications and extensions to CP2K. In order to reduce the chance of bugs being introduced into the code, and ensure that all parts of the code are working, we recommend that :+CP2K comes with over 2500 test input files (located in [[src>tests]]) which serve as both examples on how to use the many features in CP2K and also as a method for developers to test modifications and extensions to CP2K. In order to reduce the chance of bugs being introduced into the code, and ensure that all parts of the code are working, we recommend that :
   * all developers complete a regression test before committing any changes to SVN.   * all developers complete a regression test before committing any changes to SVN.
   * all users complete a test before using a self-compiled binary for their projects   * all users complete a test before using a self-compiled binary for their projects
Line 13: Line 13:
 ===== How does it work? ===== ===== How does it work? =====
  
-The regression test suite is run using the [[src>cp2k/tools/regtesting/do_regtest | do_regtest]] script. +The regression test suite is run using the [[src>tools/regtesting/do_regtest | do_regtest]] script. 
 It performs the following tasks: It performs the following tasks:
    * update to the current SVN version (including new tests)    * update to the current SVN version (including new tests)
Line 27: Line 27:
  
   * If you are able to build and run cp2k on the local machine the easiest way is to start the regtesting by running ''make ARCH=... VERSION=... test''   * If you are able to build and run cp2k on the local machine the easiest way is to start the regtesting by running ''make ARCH=... VERSION=... test''
-  * Be careful about the value of ''-j'' parameter you will use; running too many tests in parallel can make tests fail due to lack of system or GPU memory.+  * Be careful about the value of ''-j'' parameter you will use; running too many tests in parallel can cause tests to fail due to lack of system and/or GPU memory.
   * If this fails (e.g. on batch systems), continue with Step 1 else go to interpretation.   * If this fails (e.g. on batch systems), continue with Step 1 else go to interpretation.
  
Line 37: Line 37:
 ==== Step 2: Running ==== ==== Step 2: Running ====
 <code> <code>
-$ cp2k/tools/regtesting/do_regtest --help+$ tools/regtesting/do_regtest --help
 Usage: do_regtest [OPTION] Usage: do_regtest [OPTION]
 Run the CP2K regression test suite Run the CP2K regression test suite
Line 98: Line 98:
  
 ===== Adding and Resetting Tests===== ===== Adding and Resetting Tests=====
-The test-suite is fully controlled by the following files in the [[src>cp2k/tests]] directories+The test-suite is fully controlled by the following files in the [[src>tests]] directories
  
 ^ File Name            ^ Content   | ^ File Name            ^ Content   |
dev/regtesting.txt · Last modified: 2023/10/19 14:03 by krack