bin/mftf throws `Faild to connect` error

[pradeepkanaka]

What could be the reason for this issue?

I can browse the URL https://magento.test/

[dosubot]

Hello @pradeepkanaka! I'm here to help you with any bugs, questions, or contributions you have. Let's work together to solve this issue.

I found a similar open issue where a suggested solution involves configuring extra_hosts in your Docker setup:

extra_hosts: &appextrahosts
  - "magento.test:172.17.0.1"

Make sure to uncomment all extra_hosts: *appextrahosts lines in your configuration. After making these changes, restart your Docker setup. Additionally, ensure that you are using HTTPS by setting MAGENTO_BASE_URL=https://magento.test ^[1].

Common causes for connectivity issues to magento.test on port 443 include incorrect port mapping, missing extra_hosts configuration, SSL certificate issues, or incorrect Docker network settings. Ensure that your compose.yaml file maps the correct ports and that your SSL certificates are properly set up ^[2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[pradeepkanaka]

@dosu

Getting below error when running bin/mftf doctor

Connecting to Selenium Server ...

[OK] Successful

Loading Admin page ...

[ERROR] Failed to load page at url: https://magento.test/admin/admin
Please check Selenium Browser session have access to Magento instance.

[dosubot]

To resolve the error you're encountering with bin/mftf doctor, ensure that Selenium can access the Magento instance. Here are some steps to check and configure:

1. Verify extra_hosts Configuration: Ensure that the extra_hosts configuration in your compose.yaml file is correctly set up to map magento.test to the Docker network gateway. It should look like this:

   extra_hosts: &appextrahosts
     - "magento.test:172.17.0.1"

   Make sure this configuration is applied to both the app and selenium services.

2. Check Selenium Service: Ensure that the Selenium service is correctly configured and running. In your compose.yaml, the Selenium service should be uncommented and configured like this:

   selenium:
     image: selenium/standalone-chrome-debug:3.8.1
     ports:
       - "5900:5900"
     extra_hosts: *appextrahosts

3. Update MFTF Configuration: Ensure that the src/dev/tests/acceptance/.env file includes the line SELENIUM_HOST=selenium to define the host Codeception should connect to.

4. Nginx Configuration: Verify that your nginx.conf file allows access to the necessary paths for MFTF. Ensure the following configuration is present:

   location ~* ^/dev/tests/acceptance/utils($|/) {
       root $MAGE_ROOT;
       location ~ ^/dev/tests/acceptance/utils/command.php {
           fastcgi_pass   fastcgi_backend;
           fastcgi_index  index.php;
           fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
           include        fastcgi_params;
       }
   }

These steps should help ensure that Selenium can access the Magento instance and resolve the error you're facing with bin/mftf doctor ^[1][2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[pradeepkanaka]

@dosu

These configurations have already been added but still have the same issue. When I catch the exception that we are getting
above, it says xpath lookup error: Failed to execute 'send' on 'XMLHttpRequest'

[dosubot]

The error message xpath lookup error: Failed to execute 'send' on 'XMLHttpRequest' in the context of MFTF tests can be caused by several factors, such as:

1. Network Issues: Ensure that the network configuration allows the Selenium server to communicate with the Magento instance. Double-check the extra_hosts configuration to ensure proper DNS resolution.

2. Selenium Configuration: Verify that the Selenium server is correctly set up and running. Ensure that the SELENIUM_HOST in the .env file is set to selenium.

3. Nginx Configuration: Make sure that the Nginx configuration allows access to the necessary paths for MFTF tests, as previously mentioned.

4. JavaScript Errors: Check the browser console for any JavaScript errors that might be causing the XMLHttpRequest to fail.

5. Timeouts: Increase the timeout settings in your MFTF configuration to allow more time for the requests to complete.

If these steps do not resolve the issue, consider checking the logs for more detailed error messages that might provide additional insights.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[pradeepkanaka]

@dosu A browser is not opening to view it during the test

[dosubot]

To resolve the issue of the browser not opening during MFTF tests, ensure that your Selenium setup is correctly configured. Here are the steps to follow:

1. Enable the Selenium Image: Make sure the selenium image is enabled in your compose.yaml file. It should look like this:

   selenium:
     image: selenium/standalone-chrome-debug:3.8.1
     ports:
       - "5900:5900"
     extra_hosts: *appextrahosts

2. VNC Connection: Use a VNC client to connect to the Selenium container for debugging purposes. Connect using 127.0.0.1:5900 with the default password secret.

3. Check Configuration: Ensure that the SELENIUM_HOST in your src/dev/tests/acceptance/.env file is set to selenium.

4. Run a Sample Test: Execute a sample test to verify the setup:

   bin/mftf run:test AdminLoginSuccessfulTest

5. Validate Setup: Use the following command to check that everything is set up correctly:

   bin/mftf doctor

These steps should help in opening the browser during MFTF tests ^[1][2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[markshust]

FYI the selenium image was just moved over to compose.dev.yaml, as it's really a dev-only setup. I think those last instructions should get things working.