test: run mobile integration tests in Release and Debug modes #4666
+85
−68
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR extends the recently added mobile integration tests by adding
Debugconfiguration alongside the existingReleaseconfiguration, to get a better understanding of the impact of:Notes:
{{SENTRY_DSN}}inMauiProgram.cs. With an increasing number of test functions and variations, the integration test becomes slower and slower. Thus, I changed the integration test app to simply default tohttp://127.0.0.1:8000, which is the default in the test server anyway. This way, we only need to build the Android app once withReleaseandDebugconfigurations, instead of 2x4=8 times.