Explore Abinit and around
- ABINIT Coding
- Doc for new developers
- Organizing events
The use of the test suite, from the users point of view, has been introduced in the installation notes (see section 3 and 5). The following information complements the installation notes for the developer's point of view.
In order to introduce a test, one needs to :
The scripts tests/Scripts/fldiff.pl and tests/Scripts/reportdiff.pl analyze the output.
If this procedure fails, contact the code maintainers in order adjust the test case. This might mean modifying the tolerances files. Unless you are really expert, let the maintainer do the final adjustment.
Please, try to keep preferably the total time per test case to less than 10 seconds. 30 seconds is a maximum for most test cases. Going being this needs exceptional reasons.
Supposing now that you have introduced a new test case. It can be used, with the other tests of the ABINIT test suite, through different channels :
Additional note : The code uses a Pickle database (test_suite.cpkl) to store the set of objects representing the tests of the test suite. Remember to regenerate the database after any change to the TEST_INFO section or any modification of the configuration parameters of the test suite (init.py files). runtests.py provides the handy option -r (regenerate) to automatically regenerate the database before running the tests.