42289f25c6
The purpose of the changes is to clean all markdown to match a single pedantic style.
* To ensure all changes in style are properly separated.
* To ensure all styled content aligns to nearest 4-character-tab.
* To ensure all code blocks use the Angular `<code-example>` or `<code-tab>` elements.
* To ensure all markdown exists outside of html tags.
* To ensure all images use the Angular style for `<img>` elements.
* To ensure that all smart punctuation is replaced or removed.
```text
’, ’, “, ”, –, —, …
```
* To ensure all content does not conflict with the following reserved characters.
```text
@, $, *, &, #, |, <, >,
```
* To ensure all content displays using html entities.
The following changes were made to files in the following directory.
```text
aio/content
```
The target files were markdown files.
The list of excluded files:
```text
.browserslistrc, .css, .conf, .editorconfig, .gitignore, .html, .js, .json, .sh, .svg, .ts, .txt, .xlf,
```
PR Close #45325
1.7 KiB
Testing Pipes
You can test pipes without the Angular testing utilities.
If you'd like to experiment with the application that this guide describes, run it in your browser or download and run it locally.
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.
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:
@reviewed 2022-02-28