-
Notifications
You must be signed in to change notification settings - Fork 144
SCAN4NET-1003 Add CSharp.SDK.9 IT #2922
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
Conversation
26251cc to
a757b9c
Compare
a48de46 to
a7e4c3e
Compare
| @@ -0,0 +1,8 @@ | |||
| namespace CSharp.SDKs | |||
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.
The files in
- its/projects/CSharp.SDK.8
- its/projects/CSharp.SDK.9
- its/projects/CSharp.SDK.Latest
are completely identical with these exceptions
- global.json
- TargetFramework in the csprojs
- PackageReferences in the UT projects
I would use only a single project (propably its/projects/CSharp.SDK.Latest) and
- Create a global.json with the SDK (or no global.json) inside the UT
- Run the build with a
/p:TargetFramework={0}argument inside the UT - Use the PackageReferences as defined in CSharp.SDK.Latest
- Make the sdk8(), sdk9(), sdkLatest() a single parameterized test
What do you think?
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.
sounds good to me!
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.
We cant use global.json as we use specific versions of msbuild to build these projects.
We cant use File linking, as when the test is copied across to a temp directory it doesn't bring the other files with it. 😭
a7e4c3e to
567fde8
Compare
a7d060e to
c307c03
Compare
c307c03 to
f462ed4
Compare
SonarQube reviewer guideSummary: Adds C# .NET 9.0 SDK project for integration testing with SonarQube analysis. Review Focus: Verify the test project structure matches existing SDK patterns and contains appropriate SonarQube rule violations for testing. Check that the Java test correctly validates the new SDK 9 project. Start review at:
|
martin-strecker-sonarsource
left a comment
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.
LGTM



SCAN4NET-1003
Part of SCAN4NET-1000