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

Prototype ways for a test plan to work against changing upstream APIs #441

Closed
raulk opened this issue Jan 31, 2020 · 1 comment
Closed
Assignees

Comments

@raulk
Copy link
Contributor

raulk commented Jan 31, 2020

Approaches suggested so far:

  • stub objects to bridge future/past, API-incompatible versions.
  • build tags.
  • type assertions against single-method interfaces.
  • reflection.
@raulk raulk added this to the Testground v0.2 milestone Feb 11, 2020
@raulk raulk self-assigned this Feb 13, 2020
@raulk
Copy link
Contributor Author

raulk commented Feb 21, 2020

Fixed in #566.

@raulk raulk closed this as completed Feb 21, 2020
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