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

process.env.HARAKA_TEST_DIR #27

Merged
merged 4 commits into from
Sep 20, 2017
Merged

Conversation

msimerson
Copy link
Member

@msimerson msimerson commented Sep 19, 2017

  • add process.env.HARAKA_TEST_DIR support (synced from haraka/Haraka/config.js)
  • lint updates for tests
  • add __dirname/../../config to config_dir_candidates (for haraka/Haraka/*.js)

@codecov
Copy link

codecov bot commented Sep 19, 2017

Codecov Report

Merging #27 into master will decrease coverage by 0.19%.
The diff coverage is 57.14%.

Impacted file tree graph

@@            Coverage Diff            @@
##           master      #27     +/-   ##
=========================================
- Coverage   79.46%   79.26%   -0.2%     
=========================================
  Files           7        7             
  Lines         409      410      +1     
  Branches      114      115      +1     
=========================================
  Hits          325      325             
- Misses         84       85      +1
Impacted Files Coverage Δ
config.js 89.04% <50%> (-2.51%) ⬇️
configfile.js 67.48% <66.66%> (+0.33%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 320406e...69c309c. Read the comment docs.

@msimerson msimerson changed the title WIP: process.env.HARAKA_TEST_DIR process.env.HARAKA_TEST_DIR Sep 19, 2017
@msimerson
Copy link
Member Author

The only reason I'm requesting a review is due to this change. The rest of the changes are all pedestrian.

Thus far, the only time haraka-config/configfile.js was run is when a npm packaged plugin loaded it via it's test suite. This change permits haraka/Haraka/* scripts to also find the correct path to /config/ when they are running outside Haraka (primarily: their test suites). I can't think of any cases where this would fail but another set of eyes would be appreciated.

Copy link

@smfreegard smfreegard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@msimerson msimerson merged commit 1d17634 into master Sep 20, 2017
@msimerson msimerson deleted the process.env.HARAKA_TEST_DIR branch September 20, 2017 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants