Skip to content

Start running tests with --test-randomize-ordering-seed=random #47233

@dnfield

Description

@dnfield

We should shuffle our tests. I've encountered a number of test files that depend on state set by previous tests. This ends up hiding bugs and/or creating unnecessary breaking changes later on when we have to fix it.

Package test takes an argument --test-randomize-ordering-seed=random. For regular test runs this looks like pub run test --test-randomize-ordering-seed=random. For flutter test we'll have to create a way to pipe in the argument. In general, we'll want to update dev/bots/test.dart to use this argument by default when running tests for CI.

/cc @jonahwilliams @goderbauer @tvolkert @Hixie @yjbanov @zanderso - I would not be surprised if this surfaces various breaking changes in tool/flutter/etc.

Metadata

Metadata

Assignees

Labels

P2Important issues not at the top of the work lista: tests"flutter test", flutter_test, or one of our testsc: contributor-productivityTeam-specific productivity, code health, technical debt.frameworkflutter/packages/flutter repository. See also f: labels.toolAffects the "flutter" command-line tool. See also t: labels.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions