[tests]`DartServerQuickFixTest#testCreateMethodInAnotherFile` fails on a `dev` SDK

[pq]

com.jetbrains.dart.analysisServer.DartServerQuickFixTest#testCreateMethodInAnotherFile fails locally for me consistently on mac OS w/ a 3.12.0 dev build.

☁  sdk [main] ⚡  dart --version
Dart SDK version: 3.12.0-edge.3554a67118791a0727ba1d18f77da7ad06ad9f37 (main) (Mon Feb 2 16:42:26 2026 -0800) on "macos_x64"

It's passing on the bots which notably are on stable (3.10.9 ? --- https://dart.dev/get-dart/archive).

This may indicate an issue when stable rolls to 3.12 or it may just be flakiness. Something to watch.

[pq]

/fyi @helin24: something to consider is whether we want to broaden our testing matrix to add dev to stable (in case this is an failure impending w/ dart 3.12).

[helin24]

something to consider is whether we want to broaden our testing matrix to add dev to stable

It looks like they can be run in 6 minutes currently; adding dev sounds reasonable to me.

[pq]

On a lark, I created a PR that bumps us to dev and confirmed that the test breaks there:

http://github.com/flutter/dart-intellij-third-party/actions/runs/21769744179/job/62814559777?pr=241

/fyi @bwilkerson

[pq]

Test source:

dart-intellij-third-party/third_party/src/test/java/com/jetbrains/dart/analysisServer/DartServerQuickFixTest.java

Lines 67 to 70 in 1b81aad

	public void testCreateMethodInAnotherFile() {
	final VirtualFile partFile = myFixture.copyFileToProject(getTestName(false) + "_part.dart");
	doQuickFixTest("Create method 'doSomething'", partFile);
	}

[pq]

Some more context. Here's where the quick fix is invoked:

library foo;

part 'CreateMethodInAnotherFile_part.dart';

main() {
  Iterable b = new Bar().<caret>doSomething(2+2==4, 1+1, 2*2.0, "", [1], {1:2}, #*, null);
}

Here's the part before:

part of foo;

class Bar {
}

and here's the expected after:

part of foo;

class Bar {
  Iterable<dynamic><caret> doSomething(bool bool, int i, double d, String s, List<int> list, Map<int, int> map, Symbol symbol, param7) {}
}

[pq]

Oh wait, and here's what we're producing:

part of foo;

class Bar {
  Iterable<dynamic><caret> doSomething(bool bool, int i, double d, String s, List<int> list, Map<int, int> map, Symbol symbol, Object? object) {}
}

This actually looks better to me. Object? object vs. param7.

So maybe not a bug after all?

The change is interesting though.