Added standalone configuration instructions to testing documentation #51
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
dmccoystephenson
requested review from
payneBrandon,
drewjj,
Michael7371 and
mwodahl
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.
Problem
The standalone testing documentation lacks instructions for project configuration. As a result, users are left to determine on their own what the DOCKER_SHARED_VOLUME environment variable should point to and what the contents of that directory should be.
Solution
The testing documentation has been updated to include clear configuration instructions for standalone testing. Developers should now have a clear understanding of how to set up the project to run locally for standalone testing.
USDOT PR
This addresses a comment on usdot-jpo-ode#41