openstack/horizon
Code Issues Proposed changes

Corrected misspelled method in horizon documentation

Browse Source 
In the page:  http://docs.openstack.org/developer/horizon/topics/testing.html had two misspelled assertion method.

asertNoMessages() changed by assertNoMessages(), twice.

Change-Id: Icde7d230e57701eb93ed4f0e705b7737260d7ecf
Fixes: without launchpad bug number.
This commit is contained in:
Floren Llanos 2013-08-22 20:31:29 +02:00
parent c4ac732aa9
commit 88969d6787
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/topics/testing.rst
View File

@ -172,7 +172,7 @@ necessary.
To that end, Horizon includes several custom assertions to make these tasks
easier. :meth:`~horizon.test.helpers.TestCase.assertNoFormErrors`,
:meth:`~horizon.test.helpers.TestCase.assertMessageCount`, and
:meth:`~horizon.test.helpers.TestCase.asertNoMessages` all exist for exactly
:meth:`~horizon.test.helpers.TestCase.assertNoMessages` all exist for exactly
these purposes. Moreover, they provide useful output when things go wrong so
you're not left scratching your head wondering why your view test didn't
redirect as expected when you posted a form.
@ -191,7 +191,7 @@ Tips and tricks
tell you what the error was.
#. Use :meth:`~horizon.test.helpers.TestCase.assertMessageCount` and
:meth:`~horizon.test.helpers.TestCase.asertNoMessages` when a piece of code
:meth:`~horizon.test.helpers.TestCase.assertNoMessages` when a piece of code
is failing inexplicably. Since the core error handlers attach user-facing
error messages (and since the core logging is silenced during test runs)
these methods give you the dual benefit of verifying the output you expect