-
Notifications
You must be signed in to change notification settings - Fork 37
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
Evaluate benefits of marble testing #112
Labels
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Apologies if the issue could not be resolved. FeathersJS ecosystem modules are community maintained so there may be a chance that there isn't anybody available to address the issue at the moment. For other ways to get help see here. |
Oops... forgot to add the label to keep this open. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See https://github.com/ReactiveX/rxjs/blob/master/doc/marble-testing.md
The current tests are hard to reason about and some use hacky
setTimeout
s just to make it work.This could possibly be improved by using marbles.
The text was updated successfully, but these errors were encountered: