From 574a32c70d214798b82a3a3cdc64765733d4f46b Mon Sep 17 00:00:00 2001 From: Jonathan Barratt Date: Mon, 14 Sep 2015 17:19:36 +0700 Subject: [PATCH] Update writing-a-locustfile.rst, testing-other-systems.rst fix typo in explanation of nested tasksets example fix tiny typo in Grouping requests ... section fix use of "it's" (contraction of it is) where "its" (possessive pronoun) was intended --- docs/testing-other-systems.rst | 4 ++-- docs/writing-a-locustfile.rst | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/testing-other-systems.rst b/docs/testing-other-systems.rst index d601d5e15a..30eec9dd27 100644 --- a/docs/testing-other-systems.rst +++ b/docs/testing-other-systems.rst @@ -2,7 +2,7 @@ Testing other systems using custom clients =========================================== -Locust was built with HTTP as it's main target. However, it can easily be extended to load test +Locust was built with HTTP as its main target. However, it can easily be extended to load test any request/response based system, by writing a custom client that triggers :py:attr:`request_success ` and :py:attr:`request_failure ` events. @@ -16,7 +16,7 @@ Here is an example of a Locust class, **XmlRpcLocust**, which provides an XML-RP .. literalinclude:: ../examples/custom_xmlrpc_client/xmlrpc_locustfile.py If you've written Locust tests before, you'll recognize the class called *ApiUser* which is a normal -Locust class that has a *TaskSet* class with *tasks* in it's *task_set* attribute. However, the *ApiUser* +Locust class that has a *TaskSet* class with *tasks* in its *task_set* attribute. However, the *ApiUser* inherits from *XmlRpcLocust* that you can see right above ApiUser. The *XmlRpcLocust* class provides an instance of XmlRpcClient under the *client* attribute. The *XmlRpcClient* is a wrapper around the standard library's :py:class:`xmlrpclib.ServerProxy`. It basically just proxies the function calls, but with the diff --git a/docs/writing-a-locustfile.rst b/docs/writing-a-locustfile.rst index 5cd7bed5f3..b3200e2d18 100644 --- a/docs/writing-a-locustfile.rst +++ b/docs/writing-a-locustfile.rst @@ -212,7 +212,7 @@ instead of referring to a python function, you point it to another TaskSet:: pass So in above example, if the ForumPage would get selected for execution when the UserBehaviour -TaskSet is executing, is. that the ForumPage TaskSet would start executing. The ForumPage TaskSet +TaskSet is executing, then the ForumPage TaskSet would start executing. The ForumPage TaskSet would then pick one of its own tasks, execute it, then wait, and so on. There is one important thing to note about the above example, and that is the call to @@ -357,7 +357,7 @@ Grouping requests to URLs with dynamic parameters It's very common for websites to have pages whose URLs contain some kind of dynamic parameter(s). Often it makes sense to group these URL's together in Locust's statistics. This can be done by passing a *name* argument to the :py:class:`HttpSession's ` -different reqeust methods. +different request methods. Example::