Skip to content
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

enhancement: ability to exclude gRPC impls in a test case pattern #886

Open
jhump opened this issue Jun 14, 2024 · 0 comments
Open

enhancement: ability to exclude gRPC impls in a test case pattern #886

jhump opened this issue Jun 14, 2024 · 0 comments

Comments

@jhump
Copy link
Member

jhump commented Jun 14, 2024

When tests are run against the gRPC client or server implementation (vs. against the standard reference client or server), the test case permutation name gets an extra (grpc client impl) or (grpc server impl) element in the name. For test case permutations run against the standard reference implementation, there is no extra element. This makes it a challenge to create a wildcard pattern that includes only the reference implementation permutations (i.e. all names that do not contain (grpc client impl) or (grpc server impl), which can't currently be expressed with wildcard syntax).

One way to address this would be to always include an element in the permutation name and have it vary between impl:grpc and impl:reference. That way **/impl:reference/** is an easy way to include only the reference implementation permutations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant