LCPQ/dft_tools
3
0
Fork 0
mirror of https://github.com/triqs/dft_tools synced 2024-11-14 01:53:48 +01:00
Code Issues Releases Wiki Activity
f86038a7fd
dft_tools/test/plovasp/plotools/test_consistency.py

40 lines
1.3 KiB
Python
Raw Normal View History

Restructed test directory The names of the test suites have been prefixed with an underscore to avoid name conflicts with corresponding modules. Also an attempt to make a scan of all tests has been made by creating a 'test_all.py' script that is supposed to discover all test cases and run them. Unfortunately, this does not work as expected because many tests use input files assumed to be found in the current directory, which is not true if the tests are run from a different (parent) directory. This can be fixed by either forcing the change of directory (but it seems that 'unittest' does not have this functionality) or prepending input file names with the current module directory.
2015-08-10 11:32:08 +02:00
Fixed tests to make them runnable with build pytriqs All imports inside the test cases refer now to paths relative to TRIQS python library path. For example, `import vaspio` is replaced with `import applications.dft.converters.plovasp.vasio` In this way all tests can be executed wtih `build_pytriqs` provided that the package is installed (the same practice as with other 'dft_tools' tests). Also, the underscore can now be removed from subdirectory names because there is no more conflict with module names.
2016-03-10 12:24:05 +01:00
import applications.dft.converters.plovasp.vaspio
from applications.dft.converters.plovasp.inpconf import ConfigParameters
from applications.dft.converters.plovasp.plotools import check_data_consistency
from applications.dft.converters.plovasp.elstruct import ElectronicStructure
Restructed test directory The names of the test suites have been prefixed with an underscore to avoid name conflicts with corresponding modules. Also an attempt to make a scan of all tests has been made by creating a 'test_all.py' script that is supposed to discover all test cases and run them. Unfortunately, this does not work as expected because many tests use input files assumed to be found in the current directory, which is not true if the tests are run from a different (parent) directory. This can be fixed by either forcing the change of directory (but it seems that 'unittest' does not have this functionality) or prepending input file names with the current module directory.
2015-08-10 11:32:08 +02:00
import mytest
################################################################################
#
# TestDataConsistency
#
################################################################################
class TestDataConsistency(mytest.MyTestCase):
"""
Function:
Added consistency check for projected shells Added a check to 'check_data_consistency()' that verifies that each shell contains only one sort of ions. Also added a non-functioning test (implementation is commented) for the function. It requires a full set of VASP files for an example with multiple atom sorts.
2015-09-16 11:40:01 +02:00
def check_data_consistency(pars, el_struct)
Restructed test directory The names of the test suites have been prefixed with an underscore to avoid name conflicts with corresponding modules. Also an attempt to make a scan of all tests has been made by creating a 'test_all.py' script that is supposed to discover all test cases and run them. Unfortunately, this does not work as expected because many tests use input files assumed to be found in the current directory, which is not true if the tests are run from a different (parent) directory. This can be fixed by either forcing the change of directory (but it seems that 'unittest' does not have this functionality) or prepending input file names with the current module directory.
2015-08-10 11:32:08 +02:00
Scenarios:
Added consistency check for projected shells Added a check to 'check_data_consistency()' that verifies that each shell contains only one sort of ions. Also added a non-functioning test (implementation is commented) for the function. It requires a full set of VASP files for an example with multiple atom sorts.
2015-09-16 11:40:01 +02:00
- **if** a shell contains ions of different types **raise** AssertionError
Restructed test directory The names of the test suites have been prefixed with an underscore to avoid name conflicts with corresponding modules. Also an attempt to make a scan of all tests has been made by creating a 'test_all.py' script that is supposed to discover all test cases and run them. Unfortunately, this does not work as expected because many tests use input files assumed to be found in the current directory, which is not true if the tests are run from a different (parent) directory. This can be fixed by either forcing the change of directory (but it seems that 'unittest' does not have this functionality) or prepending input file names with the current module directory.
2015-08-10 11:32:08 +02:00
"""
# Scenario 1
Added consistency check for projected shells Added a check to 'check_data_consistency()' that verifies that each shell contains only one sort of ions. Also added a non-functioning test (implementation is commented) for the function. It requires a full set of VASP files for an example with multiple atom sorts.
2015-09-16 11:40:01 +02:00
def test_shell_ion_types(self):
pass
# conf_file = 'wrong_shell.cfg'
# pars = ConfigParameters(conf_file)
# pars.parse_input()
# vasp_data = vaspio.VaspData('./', read_all=False)
# vasp_data.poscar.from_file('./', poscar_filename='POSCAR.complex')
# el_strct = ElectronicStructure(vasp_data)
#
# print pars.shells
# print vasp_data.poscar.type_of_ion
#
# err_mess = "Each projected shell must"
# with self.assertRaisesRegexp(Exception, err_mess):
# check_data_consistency(pars, el_struct)
Restructed test directory The names of the test suites have been prefixed with an underscore to avoid name conflicts with corresponding modules. Also an attempt to make a scan of all tests has been made by creating a 'test_all.py' script that is supposed to discover all test cases and run them. Unfortunately, this does not work as expected because many tests use input files assumed to be found in the current directory, which is not true if the tests are run from a different (parent) directory. This can be fixed by either forcing the change of directory (but it seems that 'unittest' does not have this functionality) or prepending input file names with the current module directory.
2015-08-10 11:32:08 +02:00
Reference in New Issue Copy Permalink