Parens around test name prevents CodeLens links from working

@nilsreichardt

Noted at #1458 (comment) by @nilsreichardt.

test('foo', () {});

No tests match regular expression "^('foo')( (variant: .*))?$".

Opening this as a placeholder/reminder to ensure that once #4021 is implemented that it covers this case (which might mean that we just don't pass any test name with the line/col).

I thought this might be easy to fix without the line numbers, but it turns out the server returns the same names for these tests:

test(("test 6"), () => expect(1, equals(1)));
test('("test 6")', () => expect(1, equals(1)));

"name": "test(\"(\"test 6\")\")",
"name": "test(\"(\"test 6\")\")",

So we'll have to wait for line numbers.

Add tests for several issues requiring running tests by line

In the next release (and the pre-release version just pushed today - v3.63.20240419), you can choose to have tests executed using their line numbers rather than their names. This fixes a number of issues including this one, caused by not always being able to statically compute the exact name of a test.

Please let me know if you find any issues with this functionality!

Navigation Menu

Repository navigation

Parens around test name prevents CodeLens links from working #4168

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Parens around test name prevents CodeLens links from working #4168

Description

Activity

DanTup commented on Mar 23, 2023

DanTup commented on Apr 19, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions