-
Notifications
You must be signed in to change notification settings - Fork 951
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
Adding Unit testing docs and reference page #4603
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Co-authored-by: Grace Goheen <53586774+graciegoheen@users.noreply.github.com>
|
||
Unit tests validate your modeling logic on a small set of static inputs before you materialize your full model in production. Unit tests enable test-driven development, with benefits for developer efficiency and code reliability. | ||
|
||
To run just your unit tests: |
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.
To run just your unit tests: | |
To execute only your unit tests, use the command: |
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.
@matthewshaver My minor fixes for the reference page
Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com>
Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com>
Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com>
Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com>
Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com>
Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com>
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.
These changes look good for closed beta from docs POV. Am glad we have a follow-on issue for adding more context and explaining input and format.
Thank you @matthewshaver @runleonarun, excited to get these docs live ahead of kicking off closed beta access with a handful of folks today :) |
Co-authored-by: Grace Goheen <53586774+graciegoheen@users.noreply.github.com>
Co-authored-by: Grace Goheen <53586774+graciegoheen@users.noreply.github.com>
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.
Looks good for now, then we can tackle the fast follow work!
What are you changing in this pull request and why?
Prepping for unit testing with a reference page in the /reference/resource-properties category. This is an early iteration to give guidance to those who will test this feature.
The narrative material and more in depth details of the feature and it's execution will come at a future date.
[Internal] refer to the Notion doc for more information
Checklist
Add versioning components, as described in Versioning Docs
[] Add a note to the prerelease version Migration Guide
Review the Content style guide so my content adheres to these guidelines.
For docs versioning, review how to version a whole page and version a block of content.
Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
Adding new pages (delete if not applicable):
website/sidebars.js