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

custom test harness #2

Open
6 tasks
epage opened this issue Feb 7, 2024 · 0 comments
Open
6 tasks

custom test harness #2

epage opened this issue Feb 7, 2024 · 0 comments
Labels
C-tracking-issue Category: A tracking issue for something unstable. S-needs-team-input Status: Needs input from team on whether/how to proceed.

Comments

@epage
Copy link

epage commented Feb 7, 2024

Summary of discussion with T-libs-api about providing a richer API in test:

The biggest concern was with the compatibility surface that would have to be maintained and instead we went the opposite direction. Our aim is to make custom test harnesses first-class and shift the focus towards them rather than extending libtest. Hopefully, we can consolidate down on just a couple of frameworks with libtest providing us with the baseline API, reducing the chance that test writing between projects is too disjoint. I also hope we can share code between these projects to improve consistency and make it easier to conform to expectations.

See https://epage.github.io/blog/2023/06/iterating-on-test/

Tasks

@epage epage added C-tracking-issue Category: A tracking issue for something unstable. S-needs-team-input Status: Needs input from team on whether/how to proceed. labels Feb 7, 2024
@epage epage added this to the custom test harness milestone Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-tracking-issue Category: A tracking issue for something unstable. S-needs-team-input Status: Needs input from team on whether/how to proceed.
Projects
None yet
Development

No branches or pull requests

1 participant