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

define and document a policy when to add a new test executable #2193

Open
bashbaug opened this issue Dec 16, 2024 · 0 comments
Open

define and document a policy when to add a new test executable #2193

bashbaug opened this issue Dec 16, 2024 · 0 comments

Comments

@bashbaug
Copy link
Contributor

When adding tests for "unified SVM" Ewan asked whether the new tests should be added in their own suite and in a new test executable:

#2174 (review)

We also have tests being added for the "buffer device address" extension, currently in their own test suite:

#2192

Plus, we have tests for existing extensions, sometimes in their own test suite, and sometimes not.

We should define and document a policy when an extension should be added as a new test suite in a new test executable and when tests for an extension should be incorporated into an existing test suite.

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