Skip to content

Split DDC integration tests between AMD and DDC Library Bundle module systems#2788

Open
Markzipan wants to merge 21 commits intodart-lang:mainfrom
Markzipan:ddc-test-migration
Open

Split DDC integration tests between AMD and DDC Library Bundle module systems#2788
Markzipan wants to merge 21 commits intodart-lang:mainfrom
Markzipan:ddc-test-migration

Conversation

@Markzipan
Copy link
Contributor

@Markzipan Markzipan commented Mar 3, 2026

Migrates integration tests to *_amd_test and _ddc_library_bundle_test files.

@Markzipan Markzipan changed the title Ddc test migration Migrates tests to *_amd_test and _ddc_library_bundle_test files. Mar 3, 2026
@Markzipan Markzipan changed the title Migrates tests to *_amd_test and _ddc_library_bundle_test files. Split DDC tests between AMD and DDC Library Bundle module systems Mar 3, 2026
@Markzipan Markzipan force-pushed the ddc-test-migration branch from 6b88257 to 3957ffb Compare March 3, 2026 19:07
@Markzipan Markzipan requested a review from nshahan March 5, 2026 00:46
@Markzipan Markzipan marked this pull request as ready for review March 5, 2026 05:31
@Markzipan Markzipan changed the title Split DDC tests between AMD and DDC Library Bundle module systems Split DDC integration tests between AMD and DDC Library Bundle module systems Mar 5, 2026
await service.resume(isolateId);
try {
await service.resume(isolateId);
} catch (_) {}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth logging anything here?

});

group('breakpoint', () {
late VmServiceInterface service;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: unnecessary diff


expect(bp, isNotNull);

// Remove breakpoint so it doesn't impact other tests.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the removal of all these comments?

I wonder if we should just have a remove all breakpoints call that we can use in the teardown instead of having to remember to clean them up at the end of every test case.

import 'package:dwds/expression_compiler.dart';

import 'breakpoint_common.dart';
import 'fixtures/context.dart';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The imports in many of the new files should be triggering lints when you rebase on top of the change that enabled analysis again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants