It's absolutely not clear that the referenced issue would allow for live unit testing when finished

That's fair - the linked issue is a little vague - though dart-lang/test#112 was a little clearer and folded into that issue as a duplicate. I think there are really two parts:

package:test has some sort of watch support to re-run tests when things change (this would be some long-running process, rather than the current way which is a cold start each time you want to run tests)
The watch supports gets more clever about what tests to re-run as you make changes (I think this is much more tricky, but definitely a significantly better feature)

But if some sort of server-mode was to be implemented, there are a lot of other annoyances that may make sense to wrap up in a fix (for example resoling issues like dart-lang/test#908, dart-lang/test#837, dart-lang/test#1216, and getting a list of tests without having to first run them). It would make the job bigger, but could address a bunch of things.

Testing is something I think there's room to improve (and I have been trying to improve things incrementally - there have been quite a few improvements in the past few releases, and hopefully there will be many more if people keep filing suggestions :-)).

When for example this issue would gain a lot of upvotes, but needs functionality from another repo (e.g. language server, test package, flutter), does this has any influence on the priority of the according repo where the functionality needs to be implemented?

I'm not sure how well I can answer that. Other projects have their own priorities and I don't have much visibility of that beyond what's public (I'm not a Googler and most of my interaction with those teams is via GitHub/Gerrit although I do have some calls with some teams there). I'd imagine if there is a lot of demand for a feature (whether it's in this repo or their own) that it would be considered, though I also suspect it's usually not a case of "should we do this" but rather "of all these great ideas, which ones deliver the most value or can we acheive with the available developers".

Uh oh!

Flutter/Dart Live Unit Testing like in Visual Studio #2878

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions