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]
855 B
855 B
| title |
|---|
| Integration Tests |
Integration Tests
An integration test is a test that measures the interaction of multiple systems or parts of your application.
An integration test may seem similar to an acceptance test. The main difference is that an acceptance test is from the perspective of the end-user, while an integration test is from the perspective of the developer.
Integration tests can be found in the directory spec/requests.
You can run all integration tests with:
bundle exec rspec spec/requests
To run an individual file you can use:
bundle exec rspec spec/requests/stories_show_spec.rb
To run a specific test case you can use:
bundle exec rspec spec/requests/stories_show_spec.rb:10
where 10 is the line number of the test case that you want to execute.