-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add tests #14
Comments
A note on this. It could be worth having a |
This sounds like a really awesome idea, would allow users to build software without having to make a Rehive account. |
Indeed. That would be a pretty cool use case. The primary just being a great way to save a lot of grunt work in the future. It does mean we have a whole lot more to maintain in the SDK though. Since the stubbed calls would need to be kept up to date(but they will need to be updated on every service that has tests anyway). We could consider writing something that automates making a company and then runs through all endpoints getting the response and saving the diff. This could be useful for docs as well. |
Could this perhaps work by using the Swagger schema to generate stubs in some way? 🤔 |
We should ideally have tests that we can run before compiling and releasing a new version into the wild.
EDIT (by @OdinsPlasmaRifle ) The goal of this issue is to add a basic unit testing framework for the SDK.
The text was updated successfully, but these errors were encountered: