forked from dotnet/android
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Xamarin.Android.Build.Tests] Import regression tests from job 1 (dot…
…net#5030) Context: https://github.com/xamarin/QualityAssurance/pull/3639 This is an initial effort to migrate non duplicated and relevant tests from QualityAssurance into xamarin-android. The majority of test categories that ran in the first regression test job have been audited, and a few tests have been imported while the rest have been removed. The remaining regression test categories that were ran as part of the first and second regression test jobs have been merged, and the third job has been removed. Device tests that searched for `.__override__` directory content after a Release build have been updated to have a stricter assert. These tests will also now set `android:debuggable="true"` to allow usage of the run-as command, which is required when attempting to list the content of the potential `/data/data/*` location. The DeviceTest base class has been updated to ensure logcat output is captured on failure by escaping the destination path, and a duplicate `AddTestAttachment` call has been removed.
- Loading branch information
Showing
11 changed files
with
213 additions
and
165 deletions.
There are no files selected for viewing
This file contains 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 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 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 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 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,22 @@ | ||
using System; | ||
using System.Text; | ||
|
||
using NUnit.Framework; | ||
|
||
namespace Xamarin.Android.RuntimeTests | ||
{ | ||
[TestFixture] | ||
public class EncodingTests | ||
{ | ||
EncodingInfo[] EncodingTestData = Encoding.GetEncodings (); | ||
|
||
[Test, TestCaseSource (nameof (EncodingTestData))] | ||
public void GetAllAvailableEncodings (EncodingInfo info) | ||
{ | ||
// Requires <MandroidI18n>All</MandroidI18n> or can throw: | ||
// System.NotSupportedException : Encoding 37 data could not be found. Make sure you have correct international codeset assembly installed and enabled. | ||
Encoding enc = info.GetEncoding (); | ||
Assert.IsNotNull (enc.EncodingName, $"Failed to get Encoding from '{info.DisplayName}'."); | ||
} | ||
} | ||
} |
This file contains 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 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 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
Oops, something went wrong.