7d0aeeefe5
* Improve format and clarity of the docs [ci skip] While this change produces a lot of git noise by enacting what seems like an arbitrary linewrap on most of the files in the documentation it will result in better version control and tracking of the changes in the documentation. For example, as it currently stands, if one was to make a PR to move a comma in a sentence because each paragraph in most of the files is on a single line, that small change would look in the git history like the author had modified the entire paragraph. In reality, this author just moved a comma. This change also includes a significant number of modifications to the more article-esque docs. Many of these docs were written in a sort of stream-of-conciousness and aren't as easy to read as they could be. Hopefully this is the first of several readability changes. If we could get these docs to a more accessible reading level, we would probably see an increase in contributions. :) * Delegate markdown wrapping to Prettier * Add linewrapping explanation in the docs [ci skip]
895 B
895 B
| title |
|---|
| Acceptance Tests |
Acceptance Tests
Acceptance tests are tests from the perspective of the end-user.
It means that we are simulating what a user could do from their web browser and testing the expected behavior of the app.
Acceptance tests can be found in the directory spec/system (in Rails
terminology these are called "system tests").
You can run all acceptance tests with:
bundle exec rspec spec/system
To run an individual file you can use:
bundle exec rspec spec/system/user_views_a_reading_list_spec.rb
To run a specific test case you can use:
bundle exec rspec spec/system/user_views_a_reading_list_spec.rb:10
where 10 is the line number of the test case that you want to execute.
You can read the official guide Testing Rails Applications to learn more.