... | ... | @@ -7,4 +7,12 @@ |
|
|
## Testing
|
|
|
1. **Do unit tests**. Seems kinda unnecessary at first, but when you have a lot of them it starts to become really useful.
|
|
|
2. **Do functional testing** as much as possible. It's perhaps the most guaranteed form of automatic testing available.
|
|
|
3. We recommend using **Capybara** and **Cucumber** for functional tests. A lot of our projects use it, so you'll have a lot of people internally that can help to speed up the development of the tests. |
|
|
\ No newline at end of file |
|
|
3. We recommend using **Capybara** and **Cucumber** for functional tests. A lot of our projects use it, so you'll have a lot of people internally that can help to speed up the development of the tests.
|
|
|
|
|
|
## Unit Testing: Examples
|
|
|
* [Gocase Shelves Position](http://git.altum.com.br/gocase/gocase-on-rails/blob/7ab3098f474d6fe7c388d831337bd60b371c0d26/test/models/spree/shelf_test.rb)
|
|
|
* [Gocase Valid Users](http://git.altum.com.br/gocase/gocase-on-rails/blob/7ab3098f474d6fe7c388d831337bd60b371c0d26/test/models/spree/user_test.rb)
|
|
|
|
|
|
## Integration Testing: Examples
|
|
|
* [Client changing the preferred device on Gocase](http://git.altum.com.br/gocase/gocase-on-rails/blob/7ab3098f474d6fe7c388d831337bd60b371c0d26/test/integration/case_device_test.rb)
|
|
|
* [Gocase Website API Endpoint for Mockups](http://git.altum.com.br/gocase/gocase-on-rails/blob/7ab3098f474d6fe7c388d831337bd60b371c0d26/test/integration/api/mockups_test.rb) |
|
|
\ No newline at end of file |