Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Image Comparison for Dynamic and Multilingual screen

Ouverte
  • Quelque chose ne va pas ?
#2,426 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Calme
Stack technique
java
Domaine
computer-vision, testing-qa

Piste de recherche

Commencez par examiner SimilarityMatchingOptions et la documentation liée du plugin Appium Images sur le calcul de similarité et la recherche d’occurrences. Comparez l’exclusion du texte demandée, le seuil, le masquage des coordonnées ou des éléments ainsi que les alternatives fondées sur l’IA, puis définissez un périmètre réalisable et des tests démontrant le comportement attendu avec du texte multilingue et dynamique.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Hi,
I am using Appium Images plugin to perform visual testing, I have found Similarity Calculation and Occurences Lookup to be particularly useful for my use case where I am comparing if a screen matches the baseline, and if a certain element screenshot is present as a subset of screen.
For multilingual apps, I have found one limitation is that it picks up the translation differences which results in reduced value of ComparisonResult. For example,
English Screen

Image

German Screen

Image

Similarity Result

Image

In case, where the baseline screenshot is the same language (English) then the similiarity score comes out to be 0.999995768070221 while when the baseline screenshot is in a different language (German) then the similarity is significantly low 0.8476240038871765 due to the different text on image.

To counter this difference, one approach would be to run tests against different locales in which baseline images stored for comparison correspond to the lanague of app under test. While this approach is helpful, it adds an overhead to run tests on multiple lanaguages and does not scale if no of supported languages is large.

This is also relevant for cases where the text is variable for example, name/address/price of an on-screen element can differ. While mocking the result to have always same values for image comparison can be done, this is not always the possibility and easier to achieve.

For such image comparison, I would like to have a feature that basically ignores any text on the screen when performing image similiarity. Would it be possible to have such an option in SimilarityMatchingOptions where this flag can be passed to either consider or ignore on-screen text together with a threshold value which decided if and how much on-screen text will be taken into account during image similarity check? Another idea is to pass element ID or screen coordinates which should be excluded from image comparison, maybe to mask/blackout them, this way we can manually pass elements which have dynamic text to be excluded for similiarity matching?

Or perhaps if this is not a possibility, would it be possible to achieve this visual testing without relying on external providers and only using Appium MCP with some sort of image comparison tooling either using Images plugin or via LLM native image models. There is a feature request I have also put up for https://github.com/appium/appium-mcp/issues/418. There is a tool available for finding elements using AI but not sure if it can be extnded to also use AI for image comparison.

If there is a rather more suitable approach that already exists, I would be also interested in trying it out. thanks

Langage dominant
Java
Étoiles
1.3k
Forks
755
Merge moyen
5 j 14 h
PR mergées (30 j)
8

Préparer son environnement

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de appium/java-client

Toutes les issues de appium/java-client

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.