android / android/android-test

Espresso: [BUG]: Espresso Doesn't Match SVG Drawable When Many Characters

Open
#229 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
1.2k
Forks
342
Avg merge
11h 29m
Merged PRs (30d)
2

Description

See: https://issuetracker.google.com/119052092

Hi there,

I'm using AS and Espresso to match a Vector drawable against the drawable on my imageView and after many attempts to solve an issue I'm inclined to believe there may be an issue with AS or Espresso itself instead. It seems some paths for the generated SVG don't work, usually the ones with more characters. When I comment those out then my code works fine.

I'm sending attached the image of the lines I need to comment to match the drawable. That's the SO link for the issue:

https://stackoverflow.com/questions/52968631/espresso-doesnt-match-some-vector-drawables

And this is one of my sample Vector Drawable:





























These being the lines I need to comment out:

















Thank you very much.

Build: 3.2.1, AI-181.5540.7.32.5056338, 201810090144,

AI-181.5540.7.32.5056338, JRE 1.8.0_152-release-1136-b06x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1920x1080

Android Gradle Plugin: 3.2.1
Gradle: 4.6
NDK: from local.properties: (not specified); latest from SDK: (not found);
LLDB: pinned revision 3.1 not found; latest from SDK: (package not found);
CMake: from local.properties: (not specified); latest from SDK: (not found); from PATH: (not found);

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the sample Vector Drawable with Espresso, comparing the rendering and matching behavior with the three commented path elements enabled and disabled. The issue provides no repository file or test entry point; done would mean identifying why these paths prevent the drawable match and adding a reproducible regression test or documented resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
mobile-dev, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.