flutter / flutter/devtools

Comprehensive integration tests for new inspector

Ouverte
#8,482 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
P2 screen: inspector testing
Langage dominant
Dart
Étoiles
1.7k
Forks
404
Merge moyen
6 j 17 h
PR mergées (30 j)
18

Description

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.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

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.

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

Évaluation

Stack technique
dart
Domaine
testing, tooling
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

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