Fatal error: Internal inconsistency: No test reporter for test case argumentIDs:

[Kyle-Ye]

Description

Related issue: swiftlang/swift#76637 (comment)

Using the trick mentioned above can solve most of my needs.

But it seems I just hit another corner case in swift-tesing.

Expected behavior

No fatal error.

Actual behavior

XCTest/HarnessEventHandler.swift:282: Fatal error: Internal inconsistency: No test reporter for test case argumentIDs: Optional([Testing.Test.Case.Argument.ID(bytes: [48]), Testing.Test.Case.Argument.ID(bytes: [34, 35, 52, 102, 55, 56, 97, 50, 101, 100, 102, 54, 52, 51, 48, 101, 52, 50, 100, 55, 50, 49, 98, 53, 53, 50, 51, 102, 102, 57, 99, 102, 98, 48, 57, 100, 51, 99, 97, 57, 53, 98, 34])]) in test DemoKitTests.STests/PTypeConformance(value:expected:)/DemoKitTests.swift:5:6

Steps to reproduce

Use provided DemoKit package to reproduce it.

DemoKit.zip

swift-testing version/commit hash

None

Swift & OS version (output of swift --version ; uname -a)

Xcode 16.0.0 with Swift 5 language mode

[Kyle-Ye]

Some strange behavior: change expected to an ""/"11" or update the description implementation (return ""/"11" directly) will not trigger the fatalError crash.

[Kyle-Ye]

Close as potentially duplicated of #480

Leave to the maintainer to decide if this is a duplicated one.

[Kyle-Ye]

Temporary workaround provided by @Brett-Best

@Test(.serialized, arguments:

[grynspan]

I believe you're right and this is a duplicate, but @stmontgomery can probably confirm.

[stmontgomery]

This is effectively a dupe of #480, yes. But this manifestation of the problem is different than what was described in that issue. Here, the problem is that two arguments of a parameterized test have identical ID representations (even though their specific arguments: are different.) Either way, I do believe the fixes will be related, so we can dupe this.

Duplicate of #480