flutter / flutter/devtools

Comprehensive integration tests for new inspector

Abierto
#8,482 0 comentarios 0 reacciones 0 asignados Ver en GitHub
P2 screen: inspector testing
Lenguaje dominante
Dart
Estrellas
1.7k
Forks
404
Merge medio
6 d 17 h
PR fusionados (30 d)
18

Descripción

One of the things we need to test is whether auto-refreshing of the inspector tree works as expected after editing code and performing a hot-reload. For this, we will need a live app connection, along with either a real or fake editor so that we can modify code.

Whatever solution we come up with here will also be beneficial for testing the property editor integration across Devtools, the IDEs, and the Analysis Server.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Start by locating the new inspector integration-test entry points and the code paths for the inspector tree, live app connection, hot-reload, and editor interaction. Done means verifying auto-refresh after code edits and hot-reload, with either a real or fake editor, and covering property-editor integration across DevTools, IDEs, and the Analysis Server.

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

Evaluación

Stack tecnológico
dart
Área
testing, tooling
Tipo de issue
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.