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
Add testing in the docs #260
Comments
|
Im going to close this one, they mention in a different issue #34 That testing is done with Capybara and selenium here is a link https://guides.rubyonrails.org/testing.html#system-testing If you are not using rails then https://www.cypress.io/ might be a good option to tests these I think. |
|
I think a brief mention at least somewhere in the Stimulus handbook addressing that it's preferred to use system tests (and no current path for unit tests) would bode well for transparency. Even just a brief mention in something like testing support after browser support would be helpful. |
|
This is terrible for library authors. System tests are the end goal, but unit tests also have their place in making sure individual extensions work properly. Especially now that the not everyone needs full system tests for everything, and system tests don't properly track every feature |
https://stimulusjs.org/handbook/ Please add information regarding testing in the handbook.
The text was updated successfully, but these errors were encountered: