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.

Sign up for GitHub

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

Jump to bottom

Guidance for Testing #11

Open
tomkirbygreen opened this issue Jan 5, 2022 · 0 comments
Open

Guidance for Testing #11

tomkirbygreen opened this issue Jan 5, 2022 · 0 comments
Labels
SDK Relates to the Ably SDK Team and our ways of working in open source.

Comments

@tomkirbygreen
Copy link
Contributor

tomkirbygreen commented Jan 5, 2022 •
edited by ably-sync-bot
Loading

I think there should be some coverage of the acceptable minimum for new code (or old code that has to be touched).

Perhaps some frank discussion around the risks / rewards involved in betting large on the Sandbox environment. In particular I think we could benefit from a clear definition of what we specifically mean by 'unit test' and 'integration test'.
@tomkirbygreen tomkirbygreen added the SDK Relates to the Ably SDK Team and our ways of working in open source. label Jan 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
SDK Relates to the Ably SDK Team and our ways of working in open source.
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomkirbygreen