forked from akitaonrails/merb-book
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
4-testing-your-application/1-why.markdown
- Loading branch information
Showing
1 changed file
with
17 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,21 @@ | ||
#Why test | ||
There are many parts of the application which you can test to ensure that you minimize the chances of regression. | ||
#¿Por qué hacer tests? | ||
|
||
## Parts | ||
* Esto será una tabla de contenidos (este texto será pegado). | ||
{:toc} | ||
|
||
### Models | ||
Es importante testear o probar tus aplicaciones para asegurarte que minimizas las posibilidades | ||
de introducir errores [regression][]. | ||
El framework de pruebas predeterminado de Merb utiliza el framework de pruebas [RSpec][] y una combinación de | ||
especificaciones de modelos (model specs), de peticiones (request specs) y de integración (integration specs). | ||
|
||
### Request | ||
## Tipos de pruebas (tests) | ||
|
||
### Integration tests | ||
### Modelos | ||
|
||
### Peticiones (Requests) | ||
|
||
### Integración | ||
|
||
|
||
[regression]: http://en.wikipedia.org/wiki/Software_regression | ||
[RSpec]: http://rspec.info/ |