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

[Feature]: Visual Difference Assert

Abierto
  • ¿Algo no está bien?
#568 1 comentario 0 reacciones 0 asignados Ver en GitHub

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
Estancado
Stack tecnológico
csharp
Área
computer-vision, testing-qa

Línea de trabajo

Comienza revisando el espacio de nombres de Power Fx y el punto de entrada propuesto Preview.ImageCompare descrito en el issue. Aclara cómo deben representarse los controles o locators, las imágenes de referencia, los tipos de comparación, los filtros y la tolerancia porcentual. Se considera terminado cuando la funcionalidad admite los modos de comparación enumerados y produce resultados fiables de pass/fail para pruebas visuales con varios modelos.

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

Descripción

enhancement
Is your feature request related to a problem? Please describe.

Currently, Test Engine lacks the capability to verify visual design elements of a solution comprehensively. While it is possible to test individual properties, there is a significant need for a more efficient method that allows for visual multi-model tests. This limitation hinders the ability to ensure that the visual aspects of the application meet the desired standards and expectations.

Describe the solution you'd like

Propose the introduction of a Visual Image Compare feature in the Power Apps Test Engine. This feature should include the following capabilities:

  1. Control Name or Locator: The ability to use a control name or locator to find the specific element that needs to be tested. This will streamline the process of identifying and targeting the visual elements within the application.

  2. Reference Image: The option to specify a reference image against which the visual elements can be compared. This will serve as a baseline for the visual comparison, ensuring consistency and accuracy in the visual design.

  3. Comparison Types: The feature should support various comparison types, including Pixel, Edge Detection, Color, and Structure. This flexibility will allow for comprehensive visual testing, catering to different aspects of the visual design.

  4. Tolerance for Difference: The ability to set a tolerance for differences as a percentage. This will provide a margin for acceptable variations, ensuring that minor discrepancies do not result in false negatives.

Example Usage

Here is an example of how the Visual Image Compare feature could be used within the Power Fx namespace:

Preview.ImageCompare(Tab1, "reference.png", [{Compare: "Edge"}, {Compare: "Color"}], 10);

In this example, the ImageCompare function is used to compare the visual elements of Tab1 against a reference image named "reference.png". The comparison types specified are Edge Detection and Color, with a tolerance of 10%.

Describe alternatives you've considered

No response

Additional context?

To provide a clearer understanding of the proposed feature, I have included a screenshot of the current visual design elements and a reference image for comparison. Additionally, I have attached a document outlining the detailed requirements and expected outcomes of the Visual Image Compare feature.

Related to [Feature]: Sample of Testing the Copilot Studio Kit

For example theming of chat control

Image

Filters

To help deal with differences and false positives consider the following

Edge Detection with Polygon matching modes

Image

Blur

Image

Colormap

Image

Lenguaje dominante
C#
Estrellas
150
Forks
56
Sin PR fusionados en 30 d

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 microsoft/PowerApps-TestEngine

Todos los issues de microsoft/PowerApps-TestEngine

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.