Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unit tests should typically using a config file path instead of a list of strings #50

Closed
robdennis opened this issue Apr 9, 2014 · 0 comments
Assignees

Comments

@robdennis
Copy link
Member

Revealed in #44, there turns out to be a difference in code paths between initializing a configobj with a string path to file, vs a list of strings representing a config file's content.

The unit tests should be refactored to mostly using config file path instead of list of strings, because that's by far the most common case for our users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant