Test files main is run even when specific launch config is selected and invoked via menu

If you have a Dart unit test file open with a main function, even if you click the “green arrow” in the Runs and Debug (as in screenshot below) to try to run a specific Flutter launch config, it will still run the tests in the tests files main() instead of the selected launch config.

[DanTup]

Yep, you should always specify a program if you don’t want us to try to infer one from the open file/project. Generally I’d only suggest a launch config without a program if you want to be able to use F5 and have the entry point inferred, but need to set some additional args/env/etc. that wouldn’t otherwise be set by default.

Let me know if anything still doesn’t seem to work as expected!

[DanTup]

Is it the case if I have some targets set with a program I shouldn’t rely on the default behaviour of lib/main.dart being used?

Do you mean for targets without a program? If you have an explicit program it should always run that. However if you don’t have one set, the default behaviour is not to run lib/main.dart, there are a set of rules. It’s something like this:

• If the open file is a test file, run that (being a test file usually means inside test or integration_test and ends with _test, although there are some settings to support tests outside of the test folders etc.)
• If the open file is in bin/ or tool/, run that
• Otherwise, locate the best project root (which may start from the open file), and then look in some default locations (bin/main.dart, lib/main.dart)

So generally, if you want to always run a specific file, you should add an explicit program. Otherwise, you’ll get our best guess at what you want to run.