flutter / flutter/devtools

Comprehensive integration tests for new inspector

Open
#8,482 0 comments 0 reactions 0 assignees View on GitHub
P2 screen: inspector testing
Dominant language
Dart
Stars
1.7k
Forks
404
Avg merge
6d 17h
Merged PRs (30d)
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.

Contributor guide

Open the contributing guide

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
dart
Domain
testing, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.