You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
The external CSS/JS dependencies of the resulting index.html file are not compatible with a stricter CI environment when loading up the report inside that environment.
Depending on your CI configuration and the security levels of your CI environment you might set up the HTTP Content-Security-Policy response header to self, which in turn refers to the origin from which the protected document (in our case the html test report) is being served, and prevents other sources from being loaded.
I'm not sure about the expected behaviour in this case, but it impacts anyone trying to use the plugin in a more closed CI environment. My suggestions for a possible fix would be:
to include these libraries somehow as part of the reporter, which doesn't seem to be a positive fix;
allow the user to somehow point at them in a different way via configuration;
or allow the user to define a custom html template?
I've made a new release of the module, version 1.11.1 which now contains all assets. This should work. I'll try to create a new release of the wdio-plugin asap.
I'm going to close this issue now and keep you posted when the new version of the wdio-module is released
Environment:
8.9.3
5.5.1
4.13.1
1.1.0
(I believe this bug is independent of cucumber framework)0.1.3
Config of webdriver.io and the reporter
Description
The external CSS/JS dependencies of the resulting index.html file are not compatible with a stricter CI environment when loading up the report inside that environment.
Depending on your CI configuration and the security levels of your CI environment you might set up the HTTP
Content-Security-Policy
response header toself
, which in turn refers to the origin from which the protected document (in our case the html test report) is being served, and prevents other sources from being loaded.I'm not sure about the expected behaviour in this case, but it impacts anyone trying to use the plugin in a more closed CI environment. My suggestions for a possible fix would be:
Snapshots
/cc @wswebcreation
The text was updated successfully, but these errors were encountered: