Design a framework for testing the SDKs

[Nirmal4G]

Goals

• Ability to create templated projects for testing.
• Ability to distinguish between various SDKs used.
• Ability to gather and process both text and binary logs.
• Ability to call targets and inject tasks programmatically.
• Ability to gather properties and items programmatically.
• Ability to test against multiple versions of MSBuild programmatically and through build-infra.

TBA

[jzabroski]

🔥

[jzabroski]

@Nirmal4G I have asked @rainersigwald and @Forgind to think about integration testing MSBuildLocator. I think that would be a good place to add testing , as I dont see how a SDK that invokes MSBUild task can be fully tested without a locator test.

[Nirmal4G]

I'm using MSBuild locator in one of my prototypes. I also want to test against latest 2 major versions. So, In another prototype, I'm using PackageDownload feature but the issue is the lack of support for the GeneratePathProperty attribute.

There are a whole lot of changes after this but I want to settle the API surface first before committing the work that lead into either of the solutions above. So, expect a long delay before I push some actual code.

For now, everything will be a placeholder until I flesh-out the design and layering.

[Nirmal4G]

If you have asked the team, then is there an issue/discussion for that? I would very much like to upvote it and drive it further.