You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to verify that the NativeAOT compiler is behaving correctly, we have opted for reusing the dotnet/linker unit testing infrastructure in NativeAOT. Relevant changes are that dotnet/linker testing infrastructure is written in NUnit while dotnet/runtime repository uses XUnit. Also, dotnet/linker invested heavily in having some commonality with analyzer warning display, these could make some tests fail just for differences in the way the origin/message is represented. Therefore changes in the NativeAOT product might be necessary.
They are two large sets of changes that will account for testing integration with NativeAOT, one is the part of the infrastructure that verifies warning generation, and the second part is the one that verifies that members are kept.
The following is a list of things that need to be done to complete the NativeAOT testing integration
Port the Mono.Linker.Tests* files into NativeAOT, account for the translation NUnit->XUnit and special use of .editorconfig file to be able to port the files without significant changes. This enables the warning verification portion. Add basic testing infrastructure in NativeAOT (port from dotnet/linker) #70408
In order to verify that the NativeAOT compiler is behaving correctly, we have opted for reusing the dotnet/linker unit testing infrastructure in NativeAOT. Relevant changes are that dotnet/linker testing infrastructure is written in NUnit while dotnet/runtime repository uses XUnit. Also, dotnet/linker invested heavily in having some commonality with analyzer warning display, these could make some tests fail just for differences in the way the origin/message is represented. Therefore changes in the NativeAOT product might be necessary.
They are two large sets of changes that will account for testing integration with NativeAOT, one is the part of the infrastructure that verifies warning generation, and the second part is the one that verifies that members are kept.
The following is a list of things that need to be done to complete the NativeAOT testing integration
List of issues for NativeAOT related to testing integration:
The text was updated successfully, but these errors were encountered: