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.

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

Closed
guledali opened this issue Jun 23, 2019 · 3 comments
Closed

Add testing in the docs #260

guledali opened this issue Jun 23, 2019 · 3 comments

Comments

@guledali
Copy link

https://stimulusjs.org/handbook/ Please add information regarding testing in the handbook.

@guledali
Copy link
Author

guledali commented Jul 17, 2019

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.

@nogtini
Copy link

nogtini commented Jul 19, 2019

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.

@SampsonCrowley
Copy link

SampsonCrowley commented Apr 3, 2022

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 bless function is gone, it is near impossible to efficiently test simple feature additions are working properly through jest unit tests.

not everyone needs full system tests for everything, and system tests don't properly track every feature

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants