Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit
From Version 10.0.0-prerelease.24466.1 -> To Version 10.0.0-prerelease.24467.4
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
* Changes to improve keyboard scrolling with editors, contentInsets, and different keyboards
* picker6 screenshot
* Add entry7 screenshot test
* reset test state
* fix the distance between keyboard and cursor and remove null forgiving
* bottomBoundary should have the TextDistanceFromBottom when the bottom is not the keyboard
* FireAndForget
* new entry7 screenshot
* add back the distance from bottom in the insets
* Allow partial scrolling one direction and then moving the next scrollview the opposite direction
* Adjust insets on UITextView and other scrollviews
* we dont need more inset if no keyboard intersection
* add edge case where we have small editor
Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit
From Version 10.0.0-prerelease.24459.1 -> To Version 10.0.0-prerelease.24466.1
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
* Fixed - 22452 - ios Shell
* Added Test case
* Modified test case file
* Modified test case
* Added images for test case
* Modified test case file
* Modified test cases
* Modified test case
* Modified test case
* Added image for test case
* Committed the changes of the issue
* properly fixed the Object disposed exception
* Added the proper name of test case
* Removing the unneccesary space
* fix-15196-Removed the Dispose method.
* fix-15196-Modified and removed the changes in test case and sample.
---------
Co-authored-by: AhamedAliNishad <ahamedalinishad.j@syncfusion.com>
Context: 7efca8efb3
Context: https://github.com/xamarin/Xamarin.Forms/pull/7407
For Debug builds, .NET MAUI runs XamlC in a "ValidateOnly" mode, which
avoids writing `.dll` files at the end. This way, we get faster
builds, but still emit the same errors and warnings that would be
emitted in `Release` mode.
Right now, the `ValidateOnly` flag is only checked at the end of the
process to skip writing files. I looked for some places taking time,
such as:
36.30ms (1.1%) microsoft.maui.controls.build.tasks!Microsoft.Maui.Controls.Build.Tasks.NodeILExtensions+<PushServiceProvider>d__12.MoveNext()
20.20ms (0.6%) microsoft.maui.controls.build.tasks!Microsoft.Maui.Controls.Build.Tasks.NodeILExtensions+<PushParentObjectsArray>d__9.MoveNext()
1.21ms (0.0%) microsoft.maui.controls.build.tasks!Microsoft.Maui.Controls.Build.Tasks.NodeILExtensions.PushXmlLineInfo(class Microsoft.Maui.Controls.Xaml.INode,class Microsoft.Maui.Controls.Build.Tasks.ILContext)
And added checks to just return early in these methods.
With this change in-place, an incremental build of a `dotnet new maui`
project template:
Before:
1704 ms XamlCTask 4 calls
After:
1402 ms XamlCTask 4 calls
This probably saves a little less than 100ms per call, but in this
example it is running once per platform. This improvement probably
will help even more for larger projects with many XAML files.
* Split off DatePicker.HandlerDoesNotLeak into its own UI test.
* Changed RunMemoryTest to take in INavigation instead of NavigationPage, renamed Issue24147 to MemoryTests and changed it to take in Text from Entry to determine which Handler to use, Removed Issue22072 as that's now in MemoryTests
* Renamed Issue24147 in Tests.Shared to MemoryTests, added methods to check DatePicker and WebView. Added automationids in HostApp MemoryTests
### Description of Change
Fixes an issue where scrolling of SwipeView's parent is disabled during
swipe but not reenabled when the swipe is cancelled by manually moving
the touch below the threshold.
### Issues Fixed
Fixes#23441Fixes#16856
Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit
From Version 9.0.0-prerelease.24420.3 -> To Version 10.0.0-prerelease.24459.1
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
* Fix layout when MinimumWidth/HeightRequest is removed on Windows
* Request smaller sizes to see if it fixes tests
* Use AssertionExtensions.AssertEventually to test layout values
* Fix border lagging and unwanted animations on iOS
* Update src/Core/src/Platform/iOS/StrokeExtensions.cs
Co-authored-by: MartyIX <203266+MartyIX@users.noreply.github.com>
* Add some control on the test case
* Ensure every CALayer used by MAUI does not use animations.
---------
Co-authored-by: MartyIX <203266+MartyIX@users.noreply.github.com>
* Improve performance and stability of `BindableLayout`
Fixes#23135Fixes#10918
* Remove `IDispatcher` from `BindableLayout` enhancements
* Fix empty view not removed when adding an item on an empty observable collection
* Adjust MemoryTests to account for the improved `BindableLayout` behavior
* Improve Android device type check to use screen size
For Android visual tests, they should be run with the right
device image (currently a Nexus 5X API 30). However,
there's no easy way to check the device type for Appium.
The check that was there before works on CI
since the DEVICE_SKIN environment variable is set there
(set by the android.cake script). And it can work locally if
folks run android.cake then launch VS from that console
session to get the env variable - but it doesn't work if VS
is run separately (normal case).
So update this with a different check. Getting the actual
Android device type requires using adb. We might eventually
do that, but for now just use a screen size check as a proxy
for the device type. Also update the failure message to give
good instructions.
* Add a "uitest-prepare" target to android.cake
uitest-prepare will build the test app, launch
the emulator, and deploy the test app. But
it won't actually run any tests.
* Validate that JAVA_HOME is set
Also display the Android image name
* Check Android device capabilties for a match
* Add uitest-prepare target for ios.cake to match android
* Added note to ignore device tests
* Update note for new devs, Added section on VerifyScreenshots, Explanation about AutomationId
* Removed Fixture Setup/Teardown
* Moved paragraphs around and added new subheadings to make it easier to read. Used correct formatting for class names. Removed GalleryPage content. Removed some redundant content.
* Added note about FailsOn attribute, elaborated on DeviceTests note
* Fixed spelling errors
* Alternate word
* Added back the bit about GalleryPage
* Fixed incorrect link for DeviceTests, added bit about Issue text
* Redid intro
* Added screenshots to the VerifyScreenshots section
* Removed section
* Added info about logging
* Fixed screenshot tags
* One more tag fix
* Fixed spelling, added some syntax formatting
* Addressed comments
* Changed links to permalinks
* Added pic of failed test screenshot
Stephane Delcroix
dotnet-maestro[bot]
Alberto Aldegheri
Jakub Florkowski
Shane Neuville
TJ Lambert
Rui Marinho
NirmalKumarYuvaraj
Tamilarasan Paranthaman
BagavathiPerumal
Matthew Leibowitz
Jonathan Peppers
SuthiYuvaraj
dustin-wojciechowski
Jonathan Dick
Eric
Oleksandr Dobrynin
Peter Spada
Bret Johnson
Nicholas Bauer