This repository was archived by the owner on Jul 24, 2020. It is now read-only.
[1411] Running tests with USE_LDAP enabled outside of Yale breaks things #1618
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #1411
The
UsersController
test failure is fixed in #1595 by stubbingUser.search_ldap
.Importing users with LDAP is currently untested, so defaulting
USE_LDAP
tonil
allows those tests to run even if the variable is set in.env
. Setting this default would be a lot nicer if #1422 was merged, because we could have a.env.test
file withUSE_LDAP=0
rather than deletingUSE_LDAP
from theENV
hash before running the test suite (my current solution).I don't think there are any other tests that hit LDAP; the model method isn't tested.