gchq / Palisade

A Tool for Complex and Scalable Data Access Policy Enforcement

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Stop erroneous error message about configuration environment variable firing during unit tests

ac74475 opened this issue · comments

Currently the Rest JUnit tests fail due to the PALISADE_REST_CONFIG_PATH system variable not being set.

I'm having issues reproducing this. Indications it might be a Windows specific issue?

The IT tests do produce an erroneous ERROR log stating an environment variable isn't present. This could be a separate issue, or we could fix it for this issue.

The error message is being produced in ConfigUtils.retrieveConfigurationPath() during integration tests because it expects the environment variable to have been set. This doesn't actually matter for the IT tests as they inject a test delegate anyway. We should stop this error firing during IT tests.

Add a pair defining PALISADE_REST_CONFIG_PATH to both the surefire and failsafe plugin configurations in the Palisade root pom.xml