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 around Testing Standards #32

Open
QuintinWillison opened this issue May 4, 2022 · 0 comments
Open

Guidance around Testing Standards #32

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

Comments

@QuintinWillison
Copy link
Contributor

QuintinWillison commented May 4, 2022 •
edited by ably-sync-bot
Loading

There's a lot we would like to improve in the way that we test our SDKs.

We need to, first, write down a description of what this should look like. What does 'good' look like, for testing SDKs at Ably?

The scope of work under this issue will be to create that document in this repository and get it reviewed by the team. Once agreed we can then work on breaking it down in a way that can be progressively delivered across all SDKs.
@QuintinWillison QuintinWillison added the SDK Relates to the Ably SDK Team and our ways of working in open source. label May 4, 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
@QuintinWillison