|
# Quality
|
|
# Quality
|
|
|
|
|
|
## Recommended Practices
|
|
## Recommended Practices
|
|
|
|
|
|
|
|
### Environments
|
|
1. Have a working **dev** and **staging** environments. The staging must be as close as possible to the production env.
|
|
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.
|
|
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.
|
|
3. **Do unit tests**. Seems kinda unnecessary at first, but when you have a lot of them it starts to become really useful.
|
|
|
|
4. **Do functional testing** as much as possible. It's perhaps the most guaranteed form of automatic testing available. |
|
## Testing
|
|
\ No newline at end of file |
|
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. |
|
|
|
\ No newline at end of file |