CPLAT-6557: Add release flag and config option to test task

[corwinsheahan-wf]

Overview:

Sometimes, consumers want to run tests on dart2js compiled code in Dart 2. This technically can be done via an args separator, but this doesn't provide help info through the test task, and it also doesn't allow for a config option to be set.

This adds a top level flag to the test task, and a config option, for running tests in release mode.

Testing:

• publink into any package consuming dart_dev
• Verify that ddev test runs normally on Dart 1 and Dart 2.
• Verify that ddev test -r and ddev test --release run a build via dart2js in Dart 2, and has no effect on Dart 1.
• Verify that adding a test config option in dev.dart to release = true runs tests in release mode by default.
• Verify that the command line flag takes precedent over the config option.

[aviary3-wk]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.

[aaronstgeorge-wf]

What does negatable mean?

[robbecker-wf]

that you can also do --no-release to turn the flag false

[todbachman-wf]

QA +1

Testing Performed:

• publink into wdesk_sdk
• Verify that ddev test runs normally on Dart 1 and Dart 2.
• Verify that ddev test -r and ddev test --release run a build via dart2js in Dart 2, and has no effect on Dart 1.
• Verify that adding a test config option in dev.dart to release = true runs tests in release mode by default.
• Verify that the command line flag takes precedent over the config option.

[todbachman-wf]

@Workiva/release-management-pp