Mix test --no-start #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By preventing the application tree starting automatically we're able to start the worker as we need, however this does mean each test will need to start the processes it needs. This could be a contenious issue. One downside of this approach is that we're now forced to set Mox into "global" mode because we don't have a pid to pass to `Mox.allow/2` and we need to call `Mox.expect/2` before calling `Worker.start_link/0` AND we need the newly created `Worker` process to be able to "see" the mocked `foo/0` function. Basically it's a chicken and egg situation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
By preventing the application tree starting automatically we're able to
start the worker as we need, however this does mean each test will need
to start the processes it needs. This could be a contenious issue.
One downside of this approach is that we're now forced to set Mox into
"global" mode because we don't have a pid to pass to
Mox.allow/2andwe need to call
Mox.expect/2before callingWorker.start_link/0ANDwe need the newly created
Workerprocess to be able to "see" themocked
foo/0function. Basically it's a chicken and egg situation.