magento / magento/magento2-functional-testing-framework

mftf doctor produces php notices because of missed variables

Open
#877 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
154
Forks
134
PR merge metrics
No merged PRs in 30d

Description

MFTF produces php notices on running `vendor/bin/mftf doctor`.

### Preconditions
1. Magento 2.4.3-p1
2. Selenium 3.8.1
3. selenium/standalone-chrome-debug

### Steps to reproduce

1. run `vendor/bin/mftf doctor`

### Expected result
no warnings or notices in the console

### Actual result
it produces several notices:
```Connecting to Selenium Server ...
PHP Notice: Undefined property: Magento\FunctionalTestingFramework\Module\MagentoWebDriverDoctor::$httpProxy in /magento-demo/src/vendor/magento/magento2-functional-testing-framework/src/Magento/FunctionalTestingFramework/Module/MagentoWebDriverDoctor.php on line 94

Notice: Undefined property: Magento\FunctionalTestingFramework\Module\MagentoWebDriverDoctor::$httpProxy in /magento-demo/src/vendor/magento/magento2-functional-testing-framework/src/Magento/FunctionalTestingFramework/Module/MagentoWebDriverDoctor.php on line 94
PHP Notice: Undefined property: Magento\FunctionalTestingFramework\Module\MagentoWebDriverDoctor::$httpProxyPort in /magento-demo/src/vendor/magento/magento2-functional-testing-framework/src/Magento/FunctionalTestingFramework/Module/MagentoWebDriverDoctor.php on line 95

Notice: Undefined property: Magento\FunctionalTestingFramework\Module\MagentoWebDriverDoctor::$httpProxyPort in /magento-demo/src/vendor/magento/magento2-functional-testing-framework/src/Magento/FunctionalTestingFramework/Module/MagentoWebDriverDoctor.php on line 95
```

@magento I am working on this

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Magento/FunctionalTestingFramework/Module/MagentoWebDriverDoctor.php, especially lines 94-95 where the undefined httpProxy and httpProxyPort properties are reported. Run vendor/bin/mftf doctor against the stated Magento, Selenium, and Chrome setup, then verify that it completes without PHP warnings or notices.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
testing
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.