Fixed a markdown issue

Maybe a bug in SS markdown?

The old code generated:
<a href="(faulty-link)">assertEmailSent</a>
<code>which can simulate sending emails through the</code>Email-&gt;send()` API

Instead of the expected:
<code><a href="(good-link)">assertEmailSent</a></code>
which can simulate sending emails through the <code>Email-&gt;send()</code> API

faulty-link = http://api.silverstripe.org/search/lookup/?q=SapphireTest->assertEmailSent(&version=trunk&module=framework)

good-link: http://api.silverstripe.org/search/lookup/?q=SapphireTest->assertEmailSent()&version=trunk&module=framework
This commit is contained in:
CheeseSucker 2013-06-18 14:28:12 +02:00
parent 9a95db1998
commit b0615cdc5f

View File

@ -58,12 +58,12 @@ See [the PHPUnit manual](http://www.phpunit.de/manual/current/en/api.html#api.as
for a listing of all PHPUnit's built-in assertions. for a listing of all PHPUnit's built-in assertions.
The `[api:SapphireTest]` class comes with additional assertions which are more The `[api:SapphireTest]` class comes with additional assertions which are more
specific to the framework, e.g. `[assertEmailSent](api:SapphireTest->assertEmailSent())` specific to the framework, e.g. `[api:SapphireTest->assertEmailSent()]`
which can simulate sending emails through the `Email->send()` API without actually which can simulate sending emails through the `[api:Email->send()]` API without actually
using a mail server (see the [testing emails](email-sending)) guide. using a mail server (see the [testing emails](email-sending)) guide.
## Fixtures ## Fixtures
Often you need to test your functionality with some existing data, so called "fixtures". Often you need to test your functionality with some existing data, so called "fixtures".
These records are inserted on a fresh test database automatically. These records are inserted on a fresh test database automatically.
[Read more about fixtures](fixtures). [Read more about fixtures](fixtures).