From b2fd28d2b0f986b776e85a80faf4a63f4a1c897a Mon Sep 17 00:00:00 2001 From: Julio Lagos Date: Fri, 2 Oct 2020 17:46:51 +0200 Subject: [PATCH] docs(docs-infra): add testing-pipes.en.md for the english version of the translation and translate testing-pipes.md for spanish Fixes #229 --- aio/content/guide/testing-pipes.en.md | 41 +++++++++++++++++++++++++++ aio/content/guide/testing-pipes.md | 34 +++++++++++----------- 2 files changed, 57 insertions(+), 18 deletions(-) create mode 100644 aio/content/guide/testing-pipes.en.md diff --git a/aio/content/guide/testing-pipes.en.md b/aio/content/guide/testing-pipes.en.md new file mode 100644 index 0000000000..fef0776486 --- /dev/null +++ b/aio/content/guide/testing-pipes.en.md @@ -0,0 +1,41 @@ +# Testing Pipes + +You can test [pipes](guide/pipes) without the Angular testing utilities. + +
+ + For the sample app that the testing guides describe, see the sample app. + + For the tests features in the testing guides, see tests. + +
+ +## Testing the `TitleCasePipe` + +A pipe class has one method, `transform`, that manipulates the input +value into a transformed output value. +The `transform` implementation rarely interacts with the DOM. +Most pipes have no dependence on Angular other than the `@Pipe` +metadata and an interface. + +Consider a `TitleCasePipe` that capitalizes the first letter of each word. +Here's an implementation with a regular expression. + + + +Anything that uses a regular expression is worth testing thoroughly. +Use simple Jasmine to explore the expected cases and the edge cases. + + + +{@a write-tests} + +## Writing DOM tests to support a pipe test + +These are tests of the pipe _in isolation_. +They can't tell if the `TitleCasePipe` is working properly as applied in the application components. + +Consider adding component tests such as this one: + + + diff --git a/aio/content/guide/testing-pipes.md b/aio/content/guide/testing-pipes.md index fef0776486..ea56b85eec 100644 --- a/aio/content/guide/testing-pipes.md +++ b/aio/content/guide/testing-pipes.md @@ -1,41 +1,39 @@ -# Testing Pipes +# Probando los Pipes -You can test [pipes](guide/pipes) without the Angular testing utilities. +Puedes probar los [pipes](guide/pipes) sin las utilidades para pruebas de Angular.
- For the sample app that the testing guides describe, see the sample app. + Para la aplicación de muestra que indican las guías de prueba, visita la aplicación de prueba. - For the tests features in the testing guides, see tests. + Para las pruebas de funcionalidades en las guías de prueba, visita pruebas.
-## Testing the `TitleCasePipe` +## Probando el `TitleCasePipe` -A pipe class has one method, `transform`, that manipulates the input -value into a transformed output value. -The `transform` implementation rarely interacts with the DOM. -Most pipes have no dependence on Angular other than the `@Pipe` -metadata and an interface. +La clase de un pipe contiene un método, `transform`, que manipula el valor de entrada y lo transforma en un valor de salida. +La implementación del `transform` rara vez interactúa con el DOM. +La mayoría de los pipes no dependen de Angular más allá de los metadatos del `@Pipe` y una interfaz. -Consider a `TitleCasePipe` that capitalizes the first letter of each word. -Here's an implementation with a regular expression. +Considera una `TitleCasePipe` que pone en mayúscula la primera letra de cada palabra. +Aquí está una implementación con una expresión regular. -Anything that uses a regular expression is worth testing thoroughly. -Use simple Jasmine to explore the expected cases and the edge cases. +Cualquier cosa que use una expresión regular vale la pena probarla a fondo. +Simplemente usa Jasmine para explorar todos los casos esperados y todos los casos extremos. {@a write-tests} -## Writing DOM tests to support a pipe test +## Escribiendo pruebas DOM para soportar una prueba de un pipe -These are tests of the pipe _in isolation_. -They can't tell if the `TitleCasePipe` is working properly as applied in the application components. +Estas son pruebas de un pipe _en aislamiento_. +No pueden decir si el `TitleCasePipe` está funcionando correctamente tal y como se aplica en los componentes de la aplicación. -Consider adding component tests such as this one: +Considera añadir pruebas de componente como por ejemplo esta: