-
Notifications
You must be signed in to change notification settings - Fork 69
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 spin test documentation #1274
Conversation
Signed-off-by: tpmccallum <[email protected]>
content/spin/v2/testing-apps.md
Outdated
running 1 test | ||
test cache-hit ... ok | ||
|
||
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.46s |
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.
I'd actually really like to see a failure so I know how to read it.
This seems to be the post that I wrote. I had originally meant that as a blog post and not as documentation. I'm more than happy to let this live as documentation (since that's generally longer lived anyway), but then I'm not quite sure if we want to also have a blog post, and if so what that blog post should say. |
Signed-off-by: tpmccallum [email protected] Co-authored-by: itowlson <[email protected]> Signed-off-by: Timothy McCallum <[email protected]>
Signed-off-by: tpmccallum [email protected] Co-authored-by: itowlson <[email protected]> Signed-off-by: Timothy McCallum <[email protected]>
Signed-off-by: tpmccallum [email protected] Co-authored-by: itowlson <[email protected]> Signed-off-by: Timothy McCallum <[email protected]>
Signed-off-by: tpmccallum [email protected] Co-authored-by: itowlson <[email protected]> Signed-off-by: Timothy McCallum <[email protected]>
Signed-off-by: tpmccallum <[email protected]>
Signed-off-by: tpmccallum <[email protected]>
Signed-off-by: tpmccallum <[email protected]>
Signed-off-by: tpmccallum <[email protected]>
Signed-off-by: tpmccallum <[email protected]>
Signed-off-by: tpmccallum <[email protected]>
|
||
--- | ||
|
||
The `spin-test` plugin allows you to run tests, written in WebAssembly, against a Spin application (where all Spin and WASI APIs are configurable mocks). |
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.
suggest throughout:
The `spin-test` plugin allows you to run tests, written in WebAssembly, against a Spin application (where all Spin and WASI APIs are configurable mocks). | |
The `spin test` plugin allows you to run tests, written in WebAssembly, against a Spin application (where all Spin and WASI APIs are configurable mocks). |
because spin-test
exists only as a repo name, not as an actual command, and using this form seems to have caused a bit of confusion in the repo docs!
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.
As discussed, let's get this in so the blog link works, and we can keep iterating on it!
Content must go through a pre-merge checklist.
Pre-Merge Content Checklist
This documentation has been checked to ensure that:
title
,template
, anddate
are all settemplates/*.hbs
files) that points to a document.md
that is set to publish in the future? If so please only publish the.md
and.hbs
changes in real-time (otherwise there will be a menu item pointing to a.md
file that does not exist)cat -ve <filename> | grep '^M' | wc -l
and expect 0 as a result)bart check
PREVIEW_MODE=1
and runnpm run styles
to update styling)npm run test
and resolved all errors