The keystone unit tests set most of this stuff up in keystone/tests/unit/core.py, where it defines the location for various testing files [0] [1]. There are static methods available for accessing testing files as well [2]. The test_policy.py module in keystone has examples on how to access the policy file for testing in case you haven't used that as a reference yet [3].
Do you have a patch up for review we could look at? Let me know if this helps clear things up.
Hi Julian,
The keystone unit tests set most of this stuff up in keystone/ tests/unit/ core.py, where it defines the location for various testing files [0] [1]. There are static methods available for accessing testing files as well [2]. The test_policy.py module in keystone has examples on how to access the policy file for testing in case you haven't used that as a reference yet [3].
Do you have a patch up for review we could look at? Let me know if this helps clear things up.
[0] https:/ /github. com/openstack/ keystone/ blob/8dd27d3368 ce0aa396386010f 6aec5ed6304d687 /keystone/ tests/unit/ core.py# L64-L70 /github. com/openstack/ keystone/ blob/8dd27d3368 ce0aa396386010f 6aec5ed6304d687 /keystone/ tests/unit/ core.py# L95-L114 /github. com/openstack/ keystone/ blob/8dd27d3368 ce0aa396386010f 6aec5ed6304d687 /keystone/ tests/unit/ core.py# L154 /github. com/openstack/ keystone/ blob/8dd27d3368 ce0aa396386010f 6aec5ed6304d687 /keystone/ tests/unit/ test_policy. py#L199
[1] https:/
[2] https:/
[3] https:/