dft_tools/test/python/plovasp/vaspio/POSCAR.example.out

nq = 1
ntypes = 1
nions = [1]
el_names = ['V']
a_brav:
[[-1.4939  1.4939  1.4939]
 [ 1.4939 -1.4939  1.4939]
 [ 1.4939  1.4939 -1.4939]]
q_types:
[array([[ 0.,  0.,  0.]])]
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			`nq = 1`
			`ntypes = 1`
			`nions = [1]`
			`el_names = ['V']`
			`a_brav:`
Fix #84 updating test ref file after bugfix 974aa08 2018-02-23 10:27:10 +01:00			`[[-1.4939 1.4939 1.4939]`
			`[ 1.4939 -1.4939 1.4939]`
			`[ 1.4939 1.4939 -1.4939]]`
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			`q_types:`
			`[array([[ 0., 0., 0.]])]`