unoplatform/uno

`When_InListViewWithItemClick` and `When_InListViewWithoutItemClick` are failing too often

Open

#2,739 opened on Mar 4, 2020

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C# (837 forks)batch import
area/buildarea/tests 🧪difficulty/medium 🤔good first issueno-reproproject/items 🧾

Repository metrics

Stars
 (9,789 stars)
PR merge metrics
 (Avg merge 14d 8h) (130 merged PRs in 30d)

Description

When_InListViewWithItemClick is failing randomly on android.

https://github.com/unoplatform/uno/blob/942c11ac95da59f9222fae978fc832ea8bcc7d77/src/SamplesApp/SamplesApp.UITests/Windows_UI_Xaml_Input/DoubleTappedTapped_Tests.cs#L86

Failure:

System.ArgumentOutOfRangeException : Cannot parse 'none'.

Parameter name: text

StackTrace:

at SamplesApp.UITests.Windows_UI_Xaml_Input.GestureResult.Parse (System.String text) [0x0002b] in <3d4905eaf3454605903bf7b99d18a311>:0 
  at SamplesApp.UITests.Windows_UI_Xaml_Input.GestureResult.Get (Uno.UITest.Helpers.Queries.QueryEx textBlock) [0x0000b] in <3d4905eaf3454605903bf7b99d18a311>:0 
  at SamplesApp.UITests.Windows_UI_Xaml_Input.RightTapped_Tests.When_InListViewWithoutItemClick () [0x000a5] in <3d4905eaf3454605903bf7b99d18a311>:0 
  at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke(System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0003b] in <b4d1a66727f44ba888b54966284fabb4>:0

Contributor guide

Research direction
Inspect the test to understand the expected behavior and trace the code path that sets the text block. Determine why the text block sometimes contains 'none' instead of a valid result.
Tech stack
csharpandroid
Domain
mobiletesting
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75