This tweaks the suffix added to test names when using variants to be slightly more specific ( (variant: foo) instead of just (foo):

This is to help editors that have access only to the test name that want to support running tests easily from the editor, but without leaving the regex passed to flutter test --name open-ended, which might match other tests than the one the user expected to run (if they have their own suffix in parens).

Right now, VS Code uses a regex like:

flutter test --name "^Counter increments smoke test$" test/widget_test.dart

But this fails for tests with variants. The goal is to change this regex to something like:

flutter test --name "^Counter increments smoke test( \(variant: .*\))?$" test/widget_test.dart

This will still avoid matching other tests with a suffix in parens, but allow the variants to run, fixing #86659.

IntelliJ doesn't currently use the same restrictive regex, but that leads to behaviour that could be considered a bug and is likely to be updated with flutter/flutter-intellij#5650.

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 and followed the Flutter Style Guide, including Features we expect every widget to implement.
• 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 feature I am adding, or Hixie said the 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.

@gspencergoog @jonahwilliams I'm assuming nobody outside of this repo is relying on the exact format of this suffix, but if you think that might not be correct, please let me know!