Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
wdio-ctrf-json-reporter
Advanced tools
wdio-ctrf-json-reporter - npm Package Compare versions
Comparing version 0.0.6 to 0.0.7
| { | ||
| "name": "wdio-ctrf-json-reporter", | ||
| "version": "0.0.6", | ||
| "version": "0.0.7", | ||
| "description": "", | ||
@@ -5,0 +5,0 @@ "repository": { |
@@ -9,2 +9,6 @@ # Webdriverio JSON Test Results Report | ||
| ⭐ **If you find this project useful, consider giving it a GitHub star** ⭐ | ||
| It means a lot to us and helps us grow this open source library. | ||
| ## Features | ||
@@ -15,12 +19,2 @@ | ||
| ## What is CTRF? | ||
| CTRF is a universal JSON test report schema that addresses the lack of a standardized format for JSON test reports. | ||
| **Consistency Across Tools:** Different testing tools and frameworks often produce reports in varied formats. CTRF ensures a uniform structure, making it easier to understand and compare reports, regardless of the testing tool used. | ||
| **Language and Framework Agnostic:** It provides a universal reporting schema that works seamlessly with any programming language and testing framework. | ||
| **Facilitates Better Analysis:** With a standardized format, programatically analyzing test outcomes across multiple platforms becomes more straightforward. | ||
| ```json | ||
@@ -58,2 +52,12 @@ { | ||
| ## What is CTRF? | ||
| CTRF is a universal JSON test report schema that addresses the lack of a standardized format for JSON test reports. | ||
| **Consistency Across Tools:** Different testing tools and frameworks often produce reports in varied formats. CTRF ensures a uniform structure, making it easier to understand and compare reports, regardless of the testing tool used. | ||
| **Language and Framework Agnostic:** It provides a universal reporting schema that works seamlessly with any programming language and testing framework. | ||
| **Facilitates Better Analysis:** With a standardized format, programatically analyzing test outcomes across multiple platforms becomes more straightforward. | ||
| ## Installation | ||
@@ -106,17 +110,21 @@ | ||
| | Name | Type | Required | Details | | ||
| | ------------ | ---------------- | -------- | ----------------------------------------------------------------------------------- | | ||
| | `name` | String | Required | The name of the test. | | ||
| | `status` | String | Required | The outcome of the test. One of: `passed`, `failed`, `skipped`, `pending`, `other`. | | ||
| | `duration` | Number | Required | The time taken for the test execution, in milliseconds. | | ||
| | `start` | Number | Optional | The start time of the test as a Unix epoch timestamp. | | ||
| | `stop` | Number | Optional | The end time of the test as a Unix epoch timestamp. | | ||
| | `suite` | String | Optional | The suite or group to which the test belongs. | | ||
| | `message` | String | Optional | The failure message if the test failed. | | ||
| | `trace` | String | Optional | The stack trace captured if the test failed. | | ||
| | `rawStatus` | String | Optional | The original playwright status of the test before mapping to CTRF status. | | ||
| | `type` | String | Optional | The type of test (e.g., `api`, `e2e`). | | ||
| | `filepath` | String | Optional | The file path where the test is located in the project. | | ||
| | `retry` | Number | Optional | The number of retries attempted for the test. | | ||
| | `flake` | Boolean | Optional | Indicates whether the test result is flaky. | | ||
| | `browser` | String | Optional | The browser used for the test. | | ||
| | Name | Type | Required | Details | | ||
| | ----------- | ------- | -------- | ----------------------------------------------------------------------------------- | | ||
| | `name` | String | Required | The name of the test. | | ||
| | `status` | String | Required | The outcome of the test. One of: `passed`, `failed`, `skipped`, `pending`, `other`. | | ||
| | `duration` | Number | Required | The time taken for the test execution, in milliseconds. | | ||
| | `start` | Number | Optional | The start time of the test as a Unix epoch timestamp. | | ||
| | `stop` | Number | Optional | The end time of the test as a Unix epoch timestamp. | | ||
| | `suite` | String | Optional | The suite or group to which the test belongs. | | ||
| | `message` | String | Optional | The failure message if the test failed. | | ||
| | `trace` | String | Optional | The stack trace captured if the test failed. | | ||
| | `rawStatus` | String | Optional | The original playwright status of the test before mapping to CTRF status. | | ||
| | `type` | String | Optional | The type of test (e.g., `api`, `e2e`). | | ||
| | `filepath` | String | Optional | The file path where the test is located in the project. | | ||
| | `retries` | Number | Optional | The number of retries attempted for the test. | | ||
| | `flaky` | Boolean | Optional | Indicates whether the test result is flaky. | | ||
| | `browser` | String | Optional | The browser used for the test. | | ||
| ## Support Us | ||
| If you find this project useful, consider giving it a GitHub star ⭐. It means a lot to us. |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by0.5%
19248
- Number of lines in readme file
- increased by7.63%
127
No dependency changes