Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Image Comparison for Dynamic and Multilingual screen

Abierto
  • ¿Algo no está bien?
#2,426 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
java
Área
computer-vision, testing-qa

Línea de trabajo

Empieza revisando SimilarityMatchingOptions y la documentación vinculada del plugin Appium Images sobre el cálculo de similitud y la búsqueda de ocurrencias. Compara la exclusión de texto solicitada, el umbral, el enmascaramiento de coordenadas o elementos y las alternativas basadas en IA; después, define un alcance implementable y pruebas que demuestren el comportamiento previsto con texto multilingüe y dinámico.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Java
Estrellas
1.3k
Forks
755
Merge medio
5 d 14 h
PR fusionados (30 d)
8

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de appium/java-client

Todos los issues de appium/java-client

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.