| ... | ... | @@ -17,13 +17,11 @@ All the projects should have a **README.MD** file. Ideally this file should be i |
|
|
|
|
|
|
|
## Quality
|
|
|
|
|
|
|
|
### Recommended Practices
|
|
|
|
|
|
|
|
#### Environments
|
|
|
|
### Environments
|
|
|
|
1. Have a working **dev** and **staging** environments. The staging must be as close as possible to the production env.
|
|
|
|
2. **Synchronize** the production database into the staging db **frequently**. With this you can track down bugs easier and better simulate real-world scenarios before something unexpected happens on production.
|
|
|
|
|
|
|
|
#### Testing
|
|
|
|
### 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.
|
|
|
|
2.1. We recommend running tests with **Capybara** and **Cucumber**. 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.
|
| ... | ... | |
