Add links to testing libraries on testing.md (#912)

* [Fix #909]Added links to testing libraries on testing.md, fixed typo

* Fixed height for READ POST button

* Ammended commit that was due for another pull request
This commit is contained in:
Albert Alises 2018-10-15 18:26:30 +02:00 committed by Mac Siri
parent de695821a0
commit 7022f222c9

View file

@ -2,18 +2,18 @@
We use the following testing tools:
* **RSpec** for testing the backend
* **Capybara** with **selenium-webdriver** for view testing
* **chromedriver-helper** for standard JS testing
* **guard-rspec** for automated testing
* [Jest](https://facebook.github.io/jest) for testing in the front-end
* [SimpleCov](link-to-simplecov-repo) for tracking overall test coverage
* [**RSpec**](http://rspec.info/) for testing the backend
* [**Capybara**](https://github.com/teamcapybara/capybara) with [**selenium-webdriver**](https://github.com/SeleniumHQ/selenium/tree/master/javascript/node/selenium-webdriver) for view testing
* [**chromedriver-helper**](https://github.com/flavorjones/chromedriver-helper) for standard JS testing
* [**guard-rspec**](https://github.com/guard/guard-rspec) for automated testing
* [**Jest**](https://facebook.github.io/jest) for testing in the front-end
* [**SimpleCov**](https://github.com/colszowka/simplecov) for tracking overall test coverage
Each pull request should come with tests related to the newly written feature or bug fix. Ideally, we should test both the front end and back end.
If you'd like to help us improve our test coverage, we recommend checking out our total coverage and writing tests for selected files based on SimpleCov's (more below) test coverage results.
If you're new to writing tests in general or with Rails, we recommend reading about testing with Rails, RSpec, and Capybara first. For Webpack and
If you're new to writing tests in general or with Rails, we recommend reading about testing with Rails, RSpec, and Capybara first.
## How to Use SimpleCov