-
Notifications
You must be signed in to change notification settings - Fork 57
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
new clarinet sdk guides #754
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
made a few grammar tweaks
Made some grammar tweaks
capitalization tweak
capitalization tweak
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Adding my Slack note here for posterity:
One question that these guides bring to mind for me is that both are guides that walk through a specific example, but what both guides lack is any guidance around best practices for tests outside of that specific use case.
Would that be valuable to other devs?
Framed another way, when I finished reading that, I was like "ok I have some idea of how that test was done, but I'm not sure if I have the knowledge/framework to apply those tests to my own project"
What does this PR do?
Add two testing guides for the Clarinet SDK: