ERP5Type/tests: log details about browser environment

This can help debugging test failures on test nodes

product/ERP5Type/tests/ERP5TypeFunctionalTestCase.py

@@ -35,6 +35,7 @@ import re
 import subprocess
 import shutil
 import transaction
+import logging
 from ZPublisher.HTTPResponse import HTTPResponse
 from zExceptions.ExceptionFormatter import format_exception
 from Products.ERP5Type.tests.ERP5TypeTestCase import ERP5TypeTestCase
@@ -46,6 +47,8 @@ from selenium.webdriver.common.by import By
 from selenium.webdriver.support.ui import WebDriverWait
 from selenium.webdriver.support import expected_conditions as EC
 
+logger = logging.getLogger(__name__)
+
 # selenium workaround for localhost / 127.0.0.1 resolution
 # ------
 # Selenium connects starts a service on localhost, but when ERP5
@@ -149,8 +152,8 @@ class Xvfb(Process):
     else:
       raise EnvironmentError("All displays locked : %r" % (self.display_list,))
 
-    print 'Xvfb : %d' % self.process.pid
-    print 'Take screenshots using xwud -in %s/Xvfb_screen0' % self.fbdir
+    logger.debug('Xvfb : %d', self.process.pid)
+    logger.debug('Take screenshots using xwud -in %s/Xvfb_screen0', self.fbdir)
 
 class FunctionalTestRunner:
 
@@ -188,8 +191,7 @@ class FunctionalTestRunner:
     xvfb = Xvfb(self.instance_home)
     try:
       if not (debug and os.getenv('DISPLAY')):
-        print("\nSet 'erp5_debug_mode' environment variable to 1"
-              " to use your existing display instead of Xvfb.")
+        logger.debug("You can set 'erp5_debug_mode' environment variable to 1 to use your existing display instead of Xvfb.")
         xvfb.run()
       capabilities = webdriver.common.desired_capabilities \
         .DesiredCapabilities.FIREFOX.copy()
@@ -207,6 +209,20 @@ class FunctionalTestRunner:
         kw.update(firefox_binary=firefox_bin, executable_path=geckodriver)
       browser = webdriver.Firefox(**kw)
       start_time = time.time()
+      logger.info("Running with browser: %s", browser)
+      logger.info("Reported user agent: %s", browser.execute_script("return navigator.userAgent"))
+      logger.info(
+          "Reported screen information: %s",
+          browser.execute_script(
+              '''
+              return JSON.stringify({
+                  'screen.width': window.screen.width,
+                  'screen.height': window.screen.height,
+                  'screen.pixelDepth': window.screen.pixelDepth,
+                  'innerWidth': window.innerWidth,
+                  'innerHeight': window.innerHeight
+                })'''))
+
       browser.get(self._getTestBaseURL() + '/login_form')
       login_field = WebDriverWait(browser, 10).until(
         EC.presence_of_element_located((By.NAME, '__ac_name')),

[Jérome Perrin]

I have seen "Support Request Pipe on Front Page Dashboard" of erp5_officejs_support_request_ui_test:testFunctionalSupportRequest failing a few times recently on development branches:

https://nexedijs.erp5.net/#/test_result_module/20200731-7BAA9D0D/121

https://nexedijs.erp5.net/#/test_result_module/20200731-91E84699/119

I know this test depends on the window size, so I figured it might be helpful to make this information available in log files.