robotframework-schemathesislibrary 2.3.2__tar.gz → 2.4.0__tar.gz

{robotframework_schemathesislibrary-2.3.2/src/robotframework_schemathesislibrary.egg-info → robotframework_schemathesislibrary-2.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: robotframework-schemathesislibrary
-Version: 2.3.2
+Version: 2.4.0
 Summary: Robot Framework SchemathesisLibrary to automatically create test cases from API specifications.
 Author-email: Tatu Aalto <aalto.tatu@gmail.com>
 License-Expression: Apache-2.0
@@ -10,8 +10,8 @@ Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: robotframework>=7.2.2
 Requires-Dist: robotframework-datadriver>=1.11.2
-Requires-Dist: robotframework-pythonlibcore>=4.5.0
-Requires-Dist: schemathesis>=4.17.0
+Requires-Dist: robotframework-pythonlibcore>=4.6.0
+Requires-Dist: schemathesis>=4.21.10
 Dynamic: license-file
 
 # Robot Framework SchemathesisLibrary
@@ -175,3 +175,26 @@ def filter_query(ctx, query) -> bool:
     return True
 ```
 Then only two test with `PUT` request are generated.
+
+## Pabot Support
+
+[Pabot](https://pabot.org/) is a parallel executor for Robot Framework tests, and
+`SchemathesisLibrary` supports it.
+
+However, there's a crucial point to consider. Because `SchemathesisLibrary` uses
+[DataDriver](https://github.com/Snooz82/robotframework-datadriver) to generate
+tests dynamically, you cannot use Schemathesis's built-in parallel execution
+feature (`--workers` option).
+
+When using Pabot, you are responsible for organizing your test suites to avoid
+generating the same tests in multiple parallel processes. A good strategy might be to
+split your test into different suites, where each suite targets a specific scenario.
+
+For example, you could create separate suites for:
+-   A user that is not found in the system.
+-   A user that is found and has valid credentials.
+-   A user that is found but has invalid credentials.
+
+This approach ensures that each Pabot process works on a unique set of tests. Since
+every API and system is different, a universal rule for structuring suites is not
+possible, but this scenario-based division might be good starting point.

{robotframework_schemathesislibrary-2.3.2 → robotframework_schemathesislibrary-2.4.0}/README.md

@@ -159,3 +159,26 @@ def filter_query(ctx, query) -> bool:
     return True
 ```
 Then only two test with `PUT` request are generated.
+
+## Pabot Support
+
+[Pabot](https://pabot.org/) is a parallel executor for Robot Framework tests, and
+`SchemathesisLibrary` supports it.
+
+However, there's a crucial point to consider. Because `SchemathesisLibrary` uses
+[DataDriver](https://github.com/Snooz82/robotframework-datadriver) to generate
+tests dynamically, you cannot use Schemathesis's built-in parallel execution
+feature (`--workers` option).
+
+When using Pabot, you are responsible for organizing your test suites to avoid
+generating the same tests in multiple parallel processes. A good strategy might be to
+split your test into different suites, where each suite targets a specific scenario.
+
+For example, you could create separate suites for:
+-   A user that is not found in the system.
+-   A user that is found and has valid credentials.
+-   A user that is found but has invalid credentials.
+
+This approach ensures that each Pabot process works on a unique set of tests. Since
+every API and system is different, a universal rule for structuring suites is not
+possible, but this scenario-based division might be good starting point.

{robotframework_schemathesislibrary-2.3.2 → robotframework_schemathesislibrary-2.4.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "robotframework-schemathesislibrary"
-version = "2.3.2"
+version = "2.4.0"
 description = "Robot Framework SchemathesisLibrary to automatically create test cases from API specifications."
 authors = [
   { name="Tatu Aalto", email="aalto.tatu@gmail.com" },
@@ -12,22 +12,22 @@ keywords = ["Robot Framework", "Schemathesis", "API Testing", "Test Automation"]
 dependencies = [
     "robotframework>=7.2.2",
     "robotframework-datadriver>=1.11.2",
-    "robotframework-pythonlibcore>=4.5.0",
-    "schemathesis>=4.17.0",
+    "robotframework-pythonlibcore>=4.6.0",
+    "schemathesis>=4.21.10",
 ]
 
 [dependency-groups]
 dev = [
-    "coverage>=7.13.5",
-    "fastapi[standard]>=0.136.1",
+    "coverage>=7.14.1",
+    "fastapi[standard]>=0.138.0",
     "invoke>=3.0.3",
-    "mypy>=1.20.2",
-    "pytest>=9.0.3",
-    "requests>=2.33.1",
+    "mypy>=2.1.0",
+    "pytest>=9.1.1",
+    "requests>=2.34.2",
+    "robotframework-pabot>=5.2.2",
     "robotframework-requests>=0.9.7",
-    "robotframework-robocop>=8.2.7",
-    "ruff==0.15.12",
-    "types-requests>=2.33.0.20260503",
+    "robotframework-robocop>=8.3.2",
+    "ruff==0.15.18",
 ]
 
 [tool.semantic_release.settings]

{robotframework_schemathesislibrary-2.3.2 → robotframework_schemathesislibrary-2.4.0}/src/SchemathesisLibrary/__init__.py

@@ -31,7 +31,7 @@ from .schemathesisreader import Options, SchemathesisReader
 if TYPE_CHECKING:
     from pathlib import Path
 
-__version__ = "2.3.2"
+__version__ = "2.4.0"
 
 
 class SchemathesisLibrary(DynamicCore):

{robotframework_schemathesislibrary-2.3.2 → robotframework_schemathesislibrary-2.4.0/src/robotframework_schemathesislibrary.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: robotframework-schemathesislibrary
-Version: 2.3.2
+Version: 2.4.0
 Summary: Robot Framework SchemathesisLibrary to automatically create test cases from API specifications.
 Author-email: Tatu Aalto <aalto.tatu@gmail.com>
 License-Expression: Apache-2.0
@@ -10,8 +10,8 @@ Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: robotframework>=7.2.2
 Requires-Dist: robotframework-datadriver>=1.11.2
-Requires-Dist: robotframework-pythonlibcore>=4.5.0
-Requires-Dist: schemathesis>=4.17.0
+Requires-Dist: robotframework-pythonlibcore>=4.6.0
+Requires-Dist: schemathesis>=4.21.10
 Dynamic: license-file
 
 # Robot Framework SchemathesisLibrary
@@ -175,3 +175,26 @@ def filter_query(ctx, query) -> bool:
     return True
 ```
 Then only two test with `PUT` request are generated.
+
+## Pabot Support
+
+[Pabot](https://pabot.org/) is a parallel executor for Robot Framework tests, and
+`SchemathesisLibrary` supports it.
+
+However, there's a crucial point to consider. Because `SchemathesisLibrary` uses
+[DataDriver](https://github.com/Snooz82/robotframework-datadriver) to generate
+tests dynamically, you cannot use Schemathesis's built-in parallel execution
+feature (`--workers` option).
+
+When using Pabot, you are responsible for organizing your test suites to avoid
+generating the same tests in multiple parallel processes. A good strategy might be to
+split your test into different suites, where each suite targets a specific scenario.
+
+For example, you could create separate suites for:
+-   A user that is not found in the system.
+-   A user that is found and has valid credentials.
+-   A user that is found but has invalid credentials.
+
+This approach ensures that each Pabot process works on a unique set of tests. Since
+every API and system is different, a universal rule for structuring suites is not
+possible, but this scenario-based division might be good starting point.

robotframework_schemathesislibrary-2.4.0/src/robotframework_schemathesislibrary.egg-info/requires.txt

@@ -0,0 +1,4 @@
+robotframework>=7.2.2
+robotframework-datadriver>=1.11.2
+robotframework-pythonlibcore>=4.6.0
+schemathesis>=4.21.10

robotframework_schemathesislibrary-2.3.2/src/robotframework_schemathesislibrary.egg-info/requires.txt

@@ -1,4 +0,0 @@
-robotframework>=7.2.2
-robotframework-datadriver>=1.11.2
-robotframework-pythonlibcore>=4.5.0
-schemathesis>=4.17.0