-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Johluo/targeting pack tests #23045
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Johluo/targeting pack tests #23045
Conversation
Add test for assembly versions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good other than the 1 question
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nits. Separately, the new tests check against calculated expectations. Do we check the expected assemblies against a hard-coded list anywhere to make sure e.g. _TargetingPackDependencies
was calculated correctly?
I checked our tests in the shared framework and the targeting pack and it seems we never use any hardcoded values for expected assemblies. Is that something we want to add? |
I think it would be good to have a hardcoded baseline that we test against so that we notice when something is added/removed from the targeting pack. |
* Add test for assembly versions * Add test for framework list * Add some hardcoded lists for sharedfx and targeting pack content
* Add sharedfx and targeting pack tests (#23045) * Add test for assembly versions * Add test for framework list * Add some hardcoded lists for sharedfx and targeting pack content * Fix failing tests * Fix targeting pack tests * Feedback
Addresses #19151 and #14832. Note that I'm making the changes to 5.0 first. I'll port to 3.1 when it's done.