-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Native AOT stack trace integration test #2772
Comments
@vaind are there any gaps on this issue that I can help with? I see you've already got various integration tests here. I'm not sure if that covers all the scenarios we wanted to cover though... e.g. all the TODO items in DebugStackTraceTests.verify.cs. I figured integration tests is probably the most important thing still sitting on the backlog besides what you're doing. |
It doesn't but that PR will enable us to implement these, once it's merged. |
There are some basic runtime tests for AOT in I've had a look at the places marked with TODO linking this issue & integration testing it would be quite a bit of work so I hope we could wait for dotnet/runtime#91069 |
For future investigation: I've had an idea to run the MAUI devicetest app with a NativeAOT published build. I can't try it out at the moment because we need to update device-tests to net8 first, which is blocked (#2854). |
FWIW, we will be standing up MAUI device tests with NativeAOT on iOS, which is being tracked here: dotnet/maui#19817 |
We can't unit test Native AOT implementation of
DebugStackTrace
(there's no xUnit runner to support AOT so no way to test this in unit tests. There's a tracking issue: dotnet/runtime#91069). Instead, we need to have an integration test that captures app requests.Possible solutions
More context: #2732 (comment)
TODO items have been left as markers in DebugStackTraceTests.verify, to indicate the test cases that we should try to cover. For example:
The text was updated successfully, but these errors were encountered: