Skip to content

Represent non-encodable test argument values in Test.Case.ID #995

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
stmontgomery opened this issue Mar 4, 2025 · 0 comments · Fixed by #1000
Closed

Represent non-encodable test argument values in Test.Case.ID #995

stmontgomery opened this issue Mar 4, 2025 · 0 comments · Fixed by #1000
Assignees
Labels
enhancement New feature or request parameterized-testing Related to parameterized testing functionality
Milestone

Comments

@stmontgomery
Copy link
Contributor

Description

Currently Test.Case.ID only attempts to provide an identifier for arguments (or combinations of arguments, when there are multiple parameters) which are encodable, using one of the heuristics described in Run selected test cases. It does not attempt to model or represent arguments which don't conform to one of those protocols, and this is limiting because it means there's no way to distinguish those arguments in reporting.

Even though arguments which don't conform to one of those protocols are not considered stable, and thus cannot be selectively re-run, it's nevertheless helpful to have a way to uniquely identify and refer to such test cases within the scope of a single run. This issue tracks expanding Test.Case.ID and its associated types to model this, including providing a way to distinguish stable vs. non-stable arguments.

This is a prerequisite to #671.

Tracked by rdar://119522099

Additional information

No response

@stmontgomery stmontgomery self-assigned this Mar 4, 2025
@stmontgomery stmontgomery added the enhancement New feature or request label Mar 4, 2025
@stmontgomery stmontgomery added this to the Swift 6.x milestone Mar 4, 2025
@stmontgomery stmontgomery added the parameterized-testing Related to parameterized testing functionality label Mar 4, 2025
stmontgomery added a commit to stmontgomery/swift-testing that referenced this issue Mar 6, 2025
stmontgomery added a commit to stmontgomery/swift-testing that referenced this issue Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request parameterized-testing Related to parameterized testing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant