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

Use @API annotation for marking supported and unsupported features #27

Closed
Crumby opened this issue Dec 1, 2017 · 1 comment
Closed

Comments

@Crumby
Copy link
Contributor

Crumby commented Dec 1, 2017

In order to be able to distinguish between supported and unsupported features we should use @API annotation on test classes. This way we would be able to say which features can user expect to be supported with backward compatibility support, which are experimental or which are internal and not meant to be use by other parties then within project itself.

See http://junit.org/junit5/docs/current/user-guide/#api-evolution for example.

@Crumby
Copy link
Contributor Author

Crumby commented Oct 2, 2019

Closing as out of date.

@Crumby Crumby closed this as completed Oct 2, 2019
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