tests: pass config to constructor instead of configuring after #281
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.
Our tests previously was written in a way what created a blank authenticator object, and then configured it one config at the time. I want to transition away from that, as it makes traitlets verification of config error if any of the incremental configuration steps after the authenticator object is initialized are invalid - even though the final configuration won't be.
By this change, we align better with how users are going to use their authentication class which is typically initialized by jupyterhub itself based on config provided, rather than initialized without provided config and then updated.