mite 2.4.4__tar.gz → 2.4.6__tar.gz

{mite-2.4.4 → mite-2.4.6}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.2
 Name: mite
-Version: 2.4.4
+Version: 2.4.6
 Summary: A Python Performance Testing Framework
 Home-page: https://github.com/sky-uk/mite/
 Classifier: License :: OSI Approved :: MIT License

{mite-2.4.4 → mite-2.4.6}/dev-requirements.txt

@@ -1,7 +1,7 @@
-twine~=1.13.0
+twine~=6.1.0
 keyring~=19.0.2
 tox~=3.14.2
 pre-commit~=2.20.0
 flake8~=3.7.8
-black~=22.4.2
+black~=24.3.0
 coverage~=5.1

{mite-2.4.4 → mite-2.4.6}/docs/journeys.rst

@@ -26,7 +26,7 @@ accomplished by **data creation scenarios**.
 Firstly, when running a data creation scenario, we need to activate
 miteʼs :ref:`recorder component <recorder-component>`.  This will
 write the data as it is created to a series of `msgpack`_-format files
-in a directory called ``recorder-data``.  These files will become the
+in a directory called ``recorder_data``.  These files will become the
 input for a datapool for the load test journeys (see below).
 
 .. _msgpack: https://msgpack.org/index.html
@@ -40,7 +40,7 @@ HTTP APIs to create data.  An example might be as follows:
    from mite_http import mite_http
 
    @mite_http
-   async def create_user(context):
+   async def create_user(ctx):
        username = uuid.uuid4().hex
        async with ctx.transaction("Create user"):
            await ctx.http.post(ctx.config.get("app_url") + "/users/create",
@@ -54,7 +54,7 @@ We then send a message with the type ``data_created`` and the name
 ``users``.  This will be read by the recorder process, which listens
 to messages with type ``data_created``.  It will read the ``name`` of
 all such messages.  For each message, the ``data`` is written as a
-msgpack dictionary into the file ``recorder-data/{name}.msgpack``.
+msgpack dictionary into the file ``recorder_data/{name}.msgpack``.
 
 We create a scenario that runs this journey for a specific amount of
 time at a specific rate, which will generate our test users.  If we have
@@ -80,11 +80,11 @@ The next step is to create a data pool for the usernames:
    from mite.datapools import RecyclableIterableDataPool
 
    usernames = []
-   with open("recorder-data", "rb") as handle:
+   with open("recorder_data/users.msgpack", "rb") as handle:
        for msg in iter(Unpacker(handle, raw=False, use_list=False)):
            usernames.append((msg["username"],))
 
-   username_datapool = RecyclableIterableDataPool(usernames)
+   usernames_datapool = RecyclableIterableDataPool(usernames)
 
 .. note::
 

{mite-2.4.4 → mite-2.4.6}/mite/volume_model.py

@@ -145,7 +145,7 @@ def oneshot_vm(when=-1, stop_scenario=False):
         if s > when and not has_run:
             has_run = True
             return 1
-        if stop_scenario:
+        if stop_scenario or has_run:
             raise StopVolumeModel
         return 0
 

{mite-2.4.4 → mite-2.4.6}/mite.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.2
 Name: mite
-Version: 2.4.4
+Version: 2.4.6
 Summary: A Python Performance Testing Framework
 Home-page: https://github.com/sky-uk/mite/
 Classifier: License :: OSI Approved :: MIT License

{mite-2.4.4 → mite-2.4.6}/test-requirements.txt

@@ -13,5 +13,5 @@ pytest-cov
 pytest-httpbin
 pytest-httpserver
 sanic
-werkzeug==3.0.6
-uvloop==0.19.0
+werkzeug==3.1.3
+uvloop~=0.19.0