-
Notifications
You must be signed in to change notification settings - Fork 564
[Xamarin.Android.Build.Tests] Ignore AOT tests if compiler is not available. #855
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
[Xamarin.Android.Build.Tests] Ignore AOT tests if compiler is not ava…
…ilable. This commit makes a number of changes to the unit tests to allow us to handle different behaviour between x-a and monodroid. Firstly we can now ignore AOT based tests if the compilers or runtime is not available. This means we can share the test inputs between repos. We also split out the Debugger Attribute test inputs into a ManifestTest.OSS.cs file to we can provide different inputs in monodroid. This is because there is a difference in behaviour between the two systems. In certain cases in monodroid we DO want a debug runtime/attribute where in x-a we never do. For exmaple in x-a having DebugSymbols = 'None', EmbedAssemblies=False and Optimize = False will result in the DebugAttribute not being added. This is correct behaviour for x-a because we ALWAYS embed assemblies regardless of the user setting. In monodroid hower that is incorrect. So we need seperate test cases. This commit also moves some of the logic to do with EmbedAssemblies into the Xamarin.Android.Common.targets. This is protected bu the `$(_XASupportsFastDev)` property. Again it means the logic is all in one place rather than being split up across .targets. This should make it easier to maintain.
- Loading branch information
commit 761ee18e57a2d90a7f2be826d6817bb8e2f95aec
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
29 changes: 29 additions & 0 deletions
29
src/Xamarin.Android.Build.Tasks/Tests/Xamarin.Android.Build.Tests/ManifestTest.OSS.cs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| using System; | ||
| using System.Linq; | ||
| using NUnit.Framework; | ||
| using Xamarin.ProjectTools; | ||
| using System.IO; | ||
| using System.Xml; | ||
| using System.Xml.Linq; | ||
| using System.Xml.XPath; | ||
| using Xamarin.Tools.Zip; | ||
|
|
||
| namespace Xamarin.Android.Build.Tests | ||
| { | ||
| public partial class ManifestTest : BaseTest | ||
| { | ||
| static object [] DebuggerAttributeCases = new object [] { | ||
| // DebugType, isRelease, extpected | ||
| new object[] { "", true, false, }, | ||
| new object[] { "", false, true, }, | ||
| new object[] { "None", true, false, }, | ||
| new object[] { "None", false, false, }, | ||
| new object[] { "PdbOnly", true, false, }, | ||
| new object[] { "PdbOnly", false, true, }, | ||
| new object[] { "Full", true, false, }, | ||
| new object[] { "Full", false, true, }, | ||
| new object[] { "Portable", true, false, }, | ||
| new object[] { "Portable", false, true, }, | ||
| }; | ||
| } | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Perhaps I'm missing something, but if we
Assert.Ignore()shouldn't we also immediatelyreturnso that we don't continue execution? (Or doesAssert.Ignore()work by throwing an exception, thus exiting immediately? The documentation doesn't say.)