From 88969d678794bc5bc4cd5cb3ab0425da61018276 Mon Sep 17 00:00:00 2001 From: Floren Llanos Date: Thu, 22 Aug 2013 20:31:29 +0200 Subject: [PATCH] Corrected misspelled method in horizon documentation 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. --- doc/source/topics/testing.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/topics/testing.rst b/doc/source/topics/testing.rst index f7279a69a0d..06f32258d9f 100644 --- a/doc/source/topics/testing.rst +++ b/doc/source/topics/testing.rst @@ -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