-
Notifications
You must be signed in to change notification settings - Fork 30.1k
Closed as not planned
Closed as not planned
Copy link
Labels
P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projecta: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our testsc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.team-infraOwned by Infrastructure teamOwned by Infrastructure teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.triaged-infraTriaged by Infrastructure teamTriaged by Infrastructure team
Description
I'm thinking of a design roughly like:
- within test.dart, run the dart test runner with
--reporter=json - parse the JSON output
- print useful data to STDOUT
- at the end of the dart test runner invocation, print a JSON blob with a digest:
a. all test files that were run
b. all individual tests that were run, including the result - from recipe, POST these results back to Cocoon
- if we are in a pre-submit context, comment the failures to the PR
- if we are in a post-submit context, write the results to datastore
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projecta: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our testsc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.team-infraOwned by Infrastructure teamOwned by Infrastructure teamtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.triaged-infraTriaged by Infrastructure teamTriaged by Infrastructure team