iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

closes #395

This commit is contained in:
Mithun Patel 2015-11-21 11:59:03 -06:00 committed by Ward Bell
parent 2843cf2d5d
commit 0ddd70a6e1
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
public/docs/ts/latest/testing/application-under-test.jade
View File

@ -35,4 +35,4 @@ figure.image-display
.l-main-section .l-main-section
:marked :marked
## What’s Next? ## What’s Next?
Now that we’re familiar with how the test app works, we’re ready to poke at it with our first application tests written in Jasmine. Now that we’re familiar with how the test app works, we’re ready to poke at it with our [first application tests](first-app-tests.html) written in Jasmine.

2
public/docs/ts/latest/testing/first-app-tests.jade
View File

@ -333,4 +333,4 @@ figure.image-display
That’s not rare but it’s not typical either. Most of our application parts make some use of the Angular framework. That’s not rare but it’s not typical either. Most of our application parts make some use of the Angular framework.
In the next chapter, we’ll test a class that does rely on Angular. In the [next chapter](testing-an-angular-pipe.html), we’ll test a class that does rely on Angular.

2
public/docs/ts/latest/testing/index.jade
View File

@ -121,4 +121,4 @@ figure.image-display
such as <code>npm</code>, <code>gulp</code>, and <code>live-server</code>. such as <code>npm</code>, <code>gulp</code>, and <code>live-server</code>.
:marked :marked
Let’s get started! [Let’s get started!](jasmine-testing-101.html)

4
public/docs/ts/latest/testing/jasmine-testing-101.jade
View File

@ -151,7 +151,7 @@ pre.prettyprint.lang-bash
We can’t tell what file produced these test results. We only have one file at the moment but soon we’ll write more. We can’t tell what file produced these test results. We only have one file at the moment but soon we’ll write more.
We should wrap this test something that identifies the file. In Jasmine that “something” is a `describe` function. Every test file should have at least one `describe` that identifies the file holding the test(s). We should wrap this test into something that identifies the file. In Jasmine that “something” is a `describe` function. Every test file should have at least one `describe` that identifies the file holding the test(s).
Here’s what our revised `1st.spec.ts` looks like when wrapped in a `describe`: Here’s what our revised `1st.spec.ts` looks like when wrapped in a `describe`:
``` ```
@ -233,4 +233,4 @@ figure.image-display
## What’s Next? ## What’s Next?
Now that we’re familiar with Jasmine on its own, we’re ready to test an application. Now that we’re familiar with Jasmine on its own, we’re ready to test an application.
What application? We introduce you to it in the next chapter. What application? We introduce you to it in the [next chapter](application-under-test.html).