-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Adds a rendering performance test #24762
Open
albyrock87
wants to merge
1
commit into
dotnet:main
Choose a base branch
from
albyrock87:adds-performance-test
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+279
−5
Conversation
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
src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/RenderingPerformance.cs
Outdated
Show resolved
Hide resolved
albyrock87
force-pushed
the
adds-performance-test
branch
8 times, most recently
from
September 14, 2024 18:57
274481a
to
9d3e259
Compare
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
tj-devel709
added
area-testing
Unit tests, device tests
area-layout
StackLayout, GridLayout, ContentView, AbsoluteLayout, FlexLayout, ContentPresenter
labels
Sep 16, 2024
albyrock87
force-pushed
the
adds-performance-test
branch
from
September 18, 2024 19:25
9d3e259
to
202e8aa
Compare
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
jonathanpeppers
previously approved these changes
Sep 19, 2024
albyrock87
force-pushed
the
adds-performance-test
branch
2 times, most recently
from
September 19, 2024 17:18
b860380
to
6df2c93
Compare
albyrock87
force-pushed
the
adds-performance-test
branch
from
September 19, 2024 17:30
6df2c93
to
a112d1b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-layout
StackLayout, GridLayout, ContentView, AbsoluteLayout, FlexLayout, ContentPresenter
area-testing
Unit tests, device tests
community ✨
Community Contribution
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.
Description of Change
This introduces a UI test to measure rendering performance.
The trick is to detect platform arrange calls which happens at the end of the layout pass.
Sample output which I hope will be visible on Azure
Issues Fixed