pytest-json-ctrf 0.1.2__tar.gz → 0.2.3__tar.gz

{pytest_json_ctrf-0.1.2 → pytest_json_ctrf-0.2.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: pytest-json-ctrf
-Version: 0.1.2
+Version: 0.2.3
 Summary: Pytest plugin to generate json report in CTRF (Common Test Report Format)
 Author: Oleksii Ostapov
 Project-URL: Infopulse, https://infopulse.com/
@@ -84,6 +84,12 @@ More info here: https://ctrf.io/docs/schema/examples
 ## Report Example
 ![Example Image](./assets/report_example.png)
 
+## Technical details
+For future me and others who are interested in the technical details of the implementation.  
+The main idea is to handle xdist plugin because without it collecting report is quite straightforward.  
+By the example of putest-json-report plugin, I have learned that different plugins can be registered for the controller and workers node.  
+The `pytest_runtest_logreport` hook in the controller node is used to collect the test results from all the nodes so other nodes can just add some details to the `TestReport` object.
+
 ## Credits
 
 - https://ctrf.io/ -> nice data format
@@ -91,3 +97,6 @@ More info here: https://ctrf.io/docs/schema/examples
 - https://github.com/testomatio/pytestomatio -> Source of inspiration for creating pytest plugins
 - https://github.com/infopulse/Playwright-course-python -> The report will be used in the demo project as +1 report option
 
+### Roadmap
+- Add screenshots handling
+- Add hooks for the report extension

{pytest_json_ctrf-0.1.2 → pytest_json_ctrf-0.2.3}/README.md

@@ -69,6 +69,12 @@ More info here: https://ctrf.io/docs/schema/examples
 ## Report Example
 ![Example Image](./assets/report_example.png)
 
+## Technical details
+For future me and others who are interested in the technical details of the implementation.  
+The main idea is to handle xdist plugin because without it collecting report is quite straightforward.  
+By the example of putest-json-report plugin, I have learned that different plugins can be registered for the controller and workers node.  
+The `pytest_runtest_logreport` hook in the controller node is used to collect the test results from all the nodes so other nodes can just add some details to the `TestReport` object.
+
 ## Credits
 
 - https://ctrf.io/ -> nice data format
@@ -76,3 +82,6 @@ More info here: https://ctrf.io/docs/schema/examples
 - https://github.com/testomatio/pytestomatio -> Source of inspiration for creating pytest plugins
 - https://github.com/infopulse/Playwright-course-python -> The report will be used in the demo project as +1 report option
 
+### Roadmap
+- Add screenshots handling
+- Add hooks for the report extension

{pytest_json_ctrf-0.1.2 → pytest_json_ctrf-0.2.3}/plugin/TestObject.py

@@ -1,7 +1,6 @@
 from enum import Enum
 from pytest import TestReport
 
-
 class TestStatus(Enum):
     PASSED = "passed"
     FAILED = "failed"
@@ -18,6 +17,7 @@ class TestObject:
     start: float = None
     stop: float = None
     retries: int = 0
+    message: str = ''
 
     worker_id: str = None
     file_path: str = None
@@ -33,13 +33,20 @@ class TestObject:
         elif report.failed:
             self.status = TestStatus.FAILED
             self.raw_status = f"{report.when}_{report.outcome}"
+            self.message = f"The test failed in the {report.when} phase"
+            if hasattr(report, 'longreprtext'):
+                if "AssertionError" in report.longreprtext:
+                    self.message += " due to an assertion error"
+                elif "Exception" in report.longreprtext:
+                    self.message += " due to an exception"
         elif report.passed:
             self.status = TestStatus.PASSED
         else:
             self.status = TestStatus.OTHER
 
     def update(self, report: TestReport, worker_id: str = None) -> None:
-        self.name = report.head_line.split('[')[0]
+        self.name = report.nodeid.split('[')[0]
+        # self.name = report.head_line.split('[')[0]
         self.set_status(report)
         self.duration += report.duration
         if report.when == "setup" and not self.start:
@@ -66,7 +73,8 @@ class TestObject:
             'file_path': self.file_path,
             'tags': self.tags,
             'browser': self.browser,
-            'trace': self.trace
+            'trace': self.trace,
+            'message': self.message
         }
         if self.worker_id:
             result['extra'] = {'worker': self.worker_id}

{pytest_json_ctrf-0.1.2 → pytest_json_ctrf-0.2.3}/pyproject.toml

@@ -7,7 +7,7 @@ exclude = [".github", "tests", "build", "dist", ".venv", "pytestomatio.egg-info"
 
 [project]
 name = "pytest-json-ctrf"
-version = "0.1.2"
+version = "0.2.3"
 
 dependencies = [
     "pytest>6.0.0",

{pytest_json_ctrf-0.1.2 → pytest_json_ctrf-0.2.3}/pytest_json_ctrf.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: pytest-json-ctrf
-Version: 0.1.2
+Version: 0.2.3
 Summary: Pytest plugin to generate json report in CTRF (Common Test Report Format)
 Author: Oleksii Ostapov
 Project-URL: Infopulse, https://infopulse.com/
@@ -84,6 +84,12 @@ More info here: https://ctrf.io/docs/schema/examples
 ## Report Example
 ![Example Image](./assets/report_example.png)
 
+## Technical details
+For future me and others who are interested in the technical details of the implementation.  
+The main idea is to handle xdist plugin because without it collecting report is quite straightforward.  
+By the example of putest-json-report plugin, I have learned that different plugins can be registered for the controller and workers node.  
+The `pytest_runtest_logreport` hook in the controller node is used to collect the test results from all the nodes so other nodes can just add some details to the `TestReport` object.
+
 ## Credits
 
 - https://ctrf.io/ -> nice data format
@@ -91,3 +97,6 @@ More info here: https://ctrf.io/docs/schema/examples
 - https://github.com/testomatio/pytestomatio -> Source of inspiration for creating pytest plugins
 - https://github.com/infopulse/Playwright-course-python -> The report will be used in the demo project as +1 report option
 
+### Roadmap
+- Add screenshots handling
+- Add hooks for the report extension