-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing: Selenium test use skin ivory, but that skin does not exist #678
Comments
Another instance is the skin highcontrast which is used in scripts/test/Selenium/Agent/AgentTicketZoom.t . |
@StefanRother-OTOBO : Why is there only the default skin in var/httpd/htdocs/skins/Agent and in var/httpd/htdocs/skins/Customer ? Especially a highcontrast skin would be good to have. |
Hi Bernhard, |
See also #682. |
Is this test just about testing this skin? Then we could just skip it for the moment. |
@svenoe It just tests, that the skin selection/switch to another skin works. A manual test works. So no big risk to skip it at the moment. Improvement could be to skip, if there is only one (the default) skin. |
Thanks Helmut - yes, ok, at least for the moment this is unimportant then and could be skipped, in my opinion. |
Becaus skin 'ivory' does not exist. See #678.
For #682 some test cases were set to TODO because of this issue. Test cases in the following scrips must be un-TODOed when this issue is resolved:
|
There are no immediate plans to add skin. The existing test the depend on a skin are TODOed. Let's leave them in place, in case that skins will be added in future. Closing this issue. |
See the failing test in scripts/test/Selenium/SysConfig/AgentSetting.t .
Providing a sample skin should resolve the issue.
The text was updated successfully, but these errors were encountered: