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

SPIKE: How can we automate testing for different versions of freighter-api against different versions of Freighter extension #1802

Open
piyalbasu opened this issue Jan 17, 2025 · 0 comments

Comments

@piyalbasu
Copy link
Contributor

A tricky part of freighter-api development is that you can't always predict what version of the extension the user has. Not only does freighter-api itself need to be backwards compatible, it needs to be backwards compatible with the extension. It can be a tricky thing to get right and involves a lot of manually testing different versions of the codebase. Is there a way to automate this?

  • We would need to spin up an environment with a web app that can install different versions of freighter-api from npm and run through each method
  • We would also need to install the current version of Freighter plus the next version of Freighter to make sure all methods are working with the versions of Freighter that are likely to be in the wild
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