sealights-cypress-plugin
Advanced tools
Comparing version 2.0.18 to 2.0.20
{ | ||
"name": "sealights-cypress-plugin", | ||
"version": "2.0.18", | ||
"version": "2.0.20", | ||
"description": "Support and config files for Cypress to support Sealights integration.", | ||
@@ -36,3 +36,3 @@ "scripts": { | ||
"main": "tsOutputs/index.js", | ||
"gitHead": "bf6c83664e2af721d5d1224a67dcfca412edf25b" | ||
"gitHead": "d145735ab7d5a60d996a31eaf412ca15a1b78d22" | ||
} |
@@ -11,2 +11,24 @@ # sealights-cypress-plugin | ||
## ⚠️ Usage with other plugins | ||
If you're using the Sealights plugin with other plugins, please read the following **carefully!** <br> | ||
This plugin will register multiple types of life-cycle event handlers. | ||
However, only a single event handler can exist for each type of event (due to a limitation in Cypress). | ||
Thus, if you attempt to define any of the same handlers, | ||
your handler will either be overriden by this plugin or you will override this plugin's handler. | ||
Either way, one of the plugins will stop functioning as expected. | ||
There's an (multiple actually) open [issue](https://github.com/cypress-io/cypress/issues/22428) at Cypress tracking this limitation. | ||
These are the events this plugin will subscribe to: | ||
* before:run | ||
* after:run | ||
For example, if you specify a handler for `before:run` and override this plugin's handler, | ||
then no test events will be sent to Sealights. | ||
For a workaround and ability to use multiple plugins please refer to: [cypress-on-fix](https://github.com/bahmutov/cypress-on-fix), | ||
or the original issue linked above. | ||
## Features | ||
@@ -13,0 +35,0 @@ |
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
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
33384
127