The test harness uses a mixture of homegrown test runners and outdated @Test style annotations. Some features of the current test harness are probably not supported by the Dart native system (such as repeating a test with different parameters?), so need to check what we need to keep.
Overall reason for replacement is that the Dart native system has a better VSCode integration (immediately jump to the failing test value on broken test) and also has better scheduling. Last but not least we can avoid maintenance of a proprietary test system.
The test harness uses a mixture of homegrown test runners and outdated
@Teststyle annotations. Some features of the current test harness are probably not supported by the Dart native system (such as repeating a test with different parameters?), so need to check what we need to keep.Overall reason for replacement is that the Dart native system has a better VSCode integration (immediately jump to the failing test value on broken test) and also has better scheduling. Last but not least we can avoid maintenance of a proprietary test system.