Testing: Resolve remaining failures of Selenium tests

[bschmalhofer]

Currently there are 103 failures from running the Selenium tests under Docker. These should be resolved. When fixing the test is too much effort, then skipping the test is fine too,

See also #175, #681, #678, #907, #909, #921, #929

[bschmalhofer]

Some fixes:

• mount /opt/otobo for the sample files
• Don't try to load Kernel::System::OTOBOCommunity

Current status: 89 test scripts failing

[wollmers]

Selenium tests of installed packages, e. g. FAQ, are not skipped and need adaption.

root@ubuntu:/opt/otobo-docker# grep -i 'selenium' prove_10.0.x_2020-12-28-101043.out
[...]

Can't call method "Get" on an undefined value at /opt/otobo/scripts/test/Selenium/Agent/AgentFAQAdd.t line 25.
[11:03:15] /opt/otobo/scripts/test/Selenium/Agent/AgentFAQAdd.t ........................................................ 
Can't call method "Get" on an undefined value at /opt/otobo/scripts/test/Selenium/Agent/AgentFAQCategory.t line 24.
[11:03:15] /opt/otobo/scripts/test/Selenium/Agent/AgentFAQCategory.t ................................................... 
Can't call method "Get" on an undefined value at /opt/otobo/scripts/test/Selenium/Agent/AgentFAQDelete.t line 24.

[...]

[bschmalhofer]

For window size issues the following link might be relevant:
https://help.applitools.com/hc/en-us/articles/360007189411--Chrome-is-being-controlled-by-automated-test-software-notification

[bschmalhofer]

There is still a problem with the mounted volume /opt/otobo in the container otobo_selenium-chrome_1 . The sample files are in /opt/otobo/scripts/test/sample , but they are not readable because of file permissions.

seluser@709d1d3578b8:/$ ls -l /opt/otobo/scripts/test/sample/NotificationEvent/Export_Notification_Appointment_reminder_notification.yml
-rw-rw---- 1 1000 1000 8418 Sep 25 15:15 /opt/otobo/scripts/test/sample/NotificationEvent/Export_Notification_Appointment_reminder_notification.yml
seluser@709d1d3578b8:/$ id
uid=1200(seluser) gid=1201(seluser) groups=1201(seluser),27(sudo)

The following assumes that all required sample files are in scripts/test/sample and that the browser needs no other files from /opt/otobo . Then a workaround could be to:

• create a dir /opt/otobo/scripts/test in the running container
• 'docker cp' the dir sample into the created dir

These actions would need to be redone when restarting the container.

An alternative would be to create yet another OTOBO specific Docker image that already includes /opt/otobo/scripts/test/sample.

[bschmalhofer]

Current status: 64 Selenium test scripts failing

[bschmalhofer]

Fixed login to the customer interface: 56 scripts still failing

[bschmalhofer]

Let's close this epic issue. Three consecutive runs reported no failures. This does not mean that the Selenium test are all passing, just that the, maybe sporadically, failing tests are marked as TODO, and have an issue assigned.