[New Nuget Runner] Validate that we preserve line endings in Nuget dependency updates #11629
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.
What are you trying to accomplish?
This adds stronger testing around End-of-Line (EoL) preservation to the new RunWorker functionality, and adds a second-pass EoL normalization run that should correct any cases we miss in the future.
Anything you want to highlight for special attention from reviewers?
The existing tests are made into Theories that run with different line endings and validate that they're preserved across the dependency update process.
How will you know you've accomplished your goal?
This was implemented using TDD, although the tests passed before the functionality changes were done.
Checklist