pytest-json-ctrf 0.6.3__tar.gz → 0.6.4__tar.gz

{pytest_json_ctrf-0.6.3/pytest_json_ctrf.egg-info → pytest_json_ctrf-0.6.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pytest-json-ctrf
-Version: 0.6.3
+Version: 0.6.4
 Summary: Pytest plugin to generate json report in CTRF (Common Test Report Format)
 Author: Oleksii Ostapov
 License-Expression: MIT
@@ -132,6 +132,8 @@ The `pytest_runtest_logreport` hook in the controller node is used to collect th
 - https://github.com/infopulse/Playwright-course-python -> The report will be used in the demo project as +1 report option
 
 ## Changelog
+- 0.6.4 - summary `duration` is measured on a monotonic clock, so it stays correct when time-machine or freezegun travel is still active at the end of the session
+  - summary `start` and `stop` are still wall-clock timestamps and are shifted under that travel, so `duration` can differ from `stop - start`
 - 0.6.3 - fixed issue 7 - test and retry attempt `duration` is the sum of pytest's monotonic phase durations, so it stays correct when a time-travel library such as time-machine moves the wall clock between tests
   - `start` and `stop` are still wall-clock timestamps, so `duration` can differ from `stop - start`
   - time between phases (report hooks, failure formatting) is no longer counted

{pytest_json_ctrf-0.6.3 → pytest_json_ctrf-0.6.4}/README.md

@@ -115,6 +115,8 @@ The `pytest_runtest_logreport` hook in the controller node is used to collect th
 - https://github.com/infopulse/Playwright-course-python -> The report will be used in the demo project as +1 report option
 
 ## Changelog
+- 0.6.4 - summary `duration` is measured on a monotonic clock, so it stays correct when time-machine or freezegun travel is still active at the end of the session
+  - summary `start` and `stop` are still wall-clock timestamps and are shifted under that travel, so `duration` can differ from `stop - start`
 - 0.6.3 - fixed issue 7 - test and retry attempt `duration` is the sum of pytest's monotonic phase durations, so it stays correct when a time-travel library such as time-machine moves the wall clock between tests
   - `start` and `stop` are still wall-clock timestamps, so `duration` can differ from `stop - start`
   - time between phases (report hooks, failure formatting) is no longer counted

{pytest_json_ctrf-0.6.3 → pytest_json_ctrf-0.6.4}/ctrf/Report.py

@@ -13,16 +13,24 @@ from .TestObject import TestObject, TestStatus
 
 
 class Report:
+    # held on the class because freezegun replaces time.perf_counter and every module-level reference to it
+    _perf_counter = staticmethod(time.perf_counter)
+
     def __init__(self):
         self.test_items = OrderedDict()
         self.start_time = None
         self.stop_time = None
+        self._start_perf = None
+        self._duration_s = None
 
     def start(self) -> None:
         self.start_time = int(time.time() * 1000)
+        self._start_perf = self._perf_counter()
 
     def stop(self) -> None:
         self.stop_time = int(time.time() * 1000)
+        if self._start_perf is not None:
+            self._duration_s = self._perf_counter() - self._start_perf
 
     @staticmethod
     def _get_tool() -> dict:
@@ -49,8 +57,9 @@ class Report:
             'start': self.start_time,
             'stop': self.stop_time,
         }
-        if self.start_time is not None and self.stop_time is not None:
-            summary['duration'] = self.stop_time - self.start_time
+        # duration is monotonic, so unlike the wall-clock start/stop it survives time travel; it need not equal stop - start
+        if self._duration_s is not None:
+            summary['duration'] = round(self._duration_s * 1000)
         return summary
 
     @staticmethod

{pytest_json_ctrf-0.6.3 → pytest_json_ctrf-0.6.4}/pyproject.toml

@@ -10,7 +10,7 @@ exclude = [
 
 [project]
 name = "pytest-json-ctrf"
-version = "0.6.3"
+version = "0.6.4"
 
 # minimum pytest and Python versions: keep in sync with .github/workflows/deploy.yml and the README
 dependencies = [
@@ -45,7 +45,9 @@ ctrf = "ctrf.main"
 
 [dependency-groups]
 dev = [
+    "freezegun>=1.5",
     "jsonschema>=4.23.0",
     "pytest-rerunfailures>=14.0",
     "pytest-xdist>=3.6.1",
+    "time-machine>=2.10",
 ]

{pytest_json_ctrf-0.6.3 → pytest_json_ctrf-0.6.4/pytest_json_ctrf.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pytest-json-ctrf
-Version: 0.6.3
+Version: 0.6.4
 Summary: Pytest plugin to generate json report in CTRF (Common Test Report Format)
 Author: Oleksii Ostapov
 License-Expression: MIT
@@ -132,6 +132,8 @@ The `pytest_runtest_logreport` hook in the controller node is used to collect th
 - https://github.com/infopulse/Playwright-course-python -> The report will be used in the demo project as +1 report option
 
 ## Changelog
+- 0.6.4 - summary `duration` is measured on a monotonic clock, so it stays correct when time-machine or freezegun travel is still active at the end of the session
+  - summary `start` and `stop` are still wall-clock timestamps and are shifted under that travel, so `duration` can differ from `stop - start`
 - 0.6.3 - fixed issue 7 - test and retry attempt `duration` is the sum of pytest's monotonic phase durations, so it stays correct when a time-travel library such as time-machine moves the wall clock between tests
   - `start` and `stop` are still wall-clock timestamps, so `duration` can differ from `stop - start`
   - time between phases (report hooks, failure formatting) is no longer counted