Add patrol tests

[piotruela]

This PR add testing 2 packages that are part of the Patrol testing tool:

• patrol_cli
• patrol
• patrol_finders

They relies on multiple dependencies pinned by the Flutter SDK, most heavily on the flutter_test API.

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read the Flutter Style Guide recently, and have followed its advice.
• I signed the CLA.
• I listed at least one issue that this PR fixes in the description above.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

[kevmoo]

Uh... @devoncarew ? @natebosch ?

[devoncarew]

I'm curious - how much of package:test_api is used? I believe that's currently very lightly used, and mostly by flutter test. Adding a test here for a package that uses it might effect our ability to evolve that api.

[natebosch]

It seems like this is primarily a version-change detection test for the test_api package? I don't think we have made, nor should yet make, any promises about not bumping to a new major version of test_api.

I do think that as we iterate further on the extensibility of the test runner, package:test_api will likely become a dependency in more places.

[piotruela]

@devoncarew @natebosch I get your point. I removed from the tests the package that directly depends on test_api and updated PR description.

[Piinks]

@piotruela it looks like this fell through our review cracks, sorry about that. Would you like to continue with his change and rebase this PR?

[piotruela]

@Piinks Sorry for the late reply. Yes, I'll rebase it asap.

[Piinks]

This LGTM thank you! A change in flutter/flutter will be needed to update the pinned version of flutter/tests after this lands (so flutter/flutter will actually run these tests!)

[chunhtai]

LGTM

[auto-submit]

autosubmit label was removed for flutter/tests/420, because - The status or check suite windows_tests (shard 5 of 5, 4) has failed. Please fix the issues identified (or deflake) before re-applying this label.

• The status or check suite windows_tests (shard 4 of 5, 3) has failed. Please fix the issues identified (or deflake) before re-applying this label.
• The status or check suite linux_tests (shard 3 of 3, 2) has failed. Please fix the issues identified (or deflake) before re-applying this label.
• The status or check suite linux_tests (shard 2 of 3, 1) has failed. Please fix the issues identified (or deflake) before re-applying this label.
• The status or check suite windows_tests (shard 2 of 5, 1) has failed. Please fix the issues identified (or deflake) before re-applying this label.
• The status or check suite linux_tests (shard 1 of 3, 0) has failed. Please fix the issues identified (or deflake) before re-applying this label.
• The status or check suite windows_tests (shard 1 of 5, 0) has failed. Please fix the issues identified (or deflake) before re-applying this label.

[Piinks]

Hmm, it looks like this is failing some checks. @piotruela can you try rebasing with the tip of tree here to see if it resolves the issues?

[piotruela]

@Piinks I've rebased the PR and also updated the script file to work on multiple platforms.

[Piinks]

This LGTM, thanks for updating

[chunhtai]

LGTM

[bartekpacia]

wow this is awesome:)