Mock a config file

Question

I'm writing tests for an app that refers to a hardcoded filename "classpath:config.properties". It isn't possible to change this name. Is there any way to test this app with different configs? i.e. different tests supply different configs at runtime?

This is an odd requirement, but I'd deeply appreciate any inputs

Can you write your tests to change the config file before your application needs to read it? — Jeffrey, Jan 23 '14 at 15:57

score 1 · Accepted Answer · edited May 23 '17 at 12:28

1

Here is another question that might help you:

Dynamically loading properties file using Spring

Or you can always overwrite the properties file using the Java IO libraries.

edited May 23 '17 at 12:28

Community

1
1

answered Jan 23 '14 at 16:02

pfernandom

929
10
22

score 0 · Answer 2 · answered Jan 23 '14 at 16:13

It's all about classpath - what jars are in classpath and how you organize your project structure.

User maven so that resources from 'src/test/resources' are loaded before 'src/main/resources'. But generally the best way is to separate application-specific config resources from application code.

Alternatively, you can split the project with config resources into 3 or 4 projects:

project with code
project with config resources, added to app classpath, but not to test classpath
project with test resources, added to test classpath, but not to the app classpath
optionally, you can move JUnit test code to separate project

score 0 · Answer 3 · answered Jan 23 '14 at 16:15

0

If you load your configuration from classpath:config.properties then these properties reside in src/main/resources folder.

When you run tests you can put your mock configuration in src/test/resources and it will "override" main configuration.

answered Jan 23 '14 at 16:15

hoaz

9,883
4
42
53

Mock a config file

3 Answers3