Expected HTTP Status Code: 200 (OK). Actual Status Code: 404 (Not Found) about magento2-functional-testing-framework HOT 13 CLOSED

Any ideas?

from magento2-functional-testing-framework.

Hi @Jeroenhuisjes.
We'll figure it out.
Can provide command you used to run tests?
There are lots of possible issues can be and first of all I want to be sure you didn't try to run skipped tests.

from magento2-functional-testing-framework.

Also this error can occur if Magento is not using URL Rewrites.
If your link to Magento backend is : magento.local/index.php/admin then you should specify in .env file MAGENTO_BASE_URL=http://magento.local/index.php/.
Otherwise it should be MAGENTO_BASE_URL=http://magento.local/

from magento2-functional-testing-framework.

Hi @okolesnyk!
Hmm we do use url rewrites on our local environments so that doesn't seem to be the problem. They run with nginx though. On my own laptop where I just run Apache it seems to work just fine.

We tried vendor/bin/codecept run and variations of this and we tried different vendor/bin/robo commands.
We use a local Selenium install. Looks like phpunit fails some kind of assertion or can't make a connection with the shop?

from magento2-functional-testing-framework.

Hey @Jeroenhuisjes
I finally figured out what is wrong.
This is our bug we should resolve.
The problem is in this file: https://github.com/magento/magento2-functional-testing-framework/blob/develop/src/Magento/FunctionalTestingFramework/Module/MagentoRestDriver.php#L120

We didn't properly test it with nginx. Because I can only reproduce this with nginx webserver.

from magento2-functional-testing-framework.

Hi @Jeroenhuisjes. Thank you for the report. We created internal ticket MQE-897 to track the progress. We will update you here about progress on this issue.

from magento2-functional-testing-framework.

@okolesnyk Thanks!

from magento2-functional-testing-framework.

Hi @Jeroenhuisjes
After a while I can not reproduce this issue anymore.
We did some changes and probably we fixed it.
Can you please verify that this issue has gone?
If you still facing same problem, please make sure you using latest MFTF v. 2.1.2.

from magento2-functional-testing-framework.

@okolesnyk
Seems to be working! Thanks 👍

from magento2-functional-testing-framework.

Thanks for confirming, @Jeroenhuisjes! We'll go ahead and close this issue.

from magento2-functional-testing-framework.

Hi.
I have the same issue on magento 2.2.5 enterprise endition and my MFTF version is 2.1.2(the last one)

My base url is: magento.test.
If i change the MAGENTO_BASE_URL from: magento.test to magento.test/index.php/admin in (/dev/tests/acceptance/.env) the error dissapear and the tests start running but it doesen't know the correct base url and the test(s) fails.
Somehow the real base url returns 404 and the backend address return 200
Does anyone know how i can solve this issue?

from magento2-functional-testing-framework.

Hi, we are running into the same problem in 2.2.0. After some investigation we found out that the first API call made by vendor/bin/codecept run to get the API token goes to BASE_URL/rest//default/V1/integration/admin/token. On this url we are getting a 404 with postman too. After removing "default" from the url we could successfully receive a token. We checked all configuration options in the .env file but could not find any configuration regarding this default value in the url.

from magento2-functional-testing-framework.

Hi.
Meanwhile i solve the problem, and as you said, i remove "default" from the API call link.
You can do that in this path: dev/tests/acceptance/tests/functional.suite.dist.yml:18.

After you do that you should run: vendor/bin/robo build:project command

from magento2-functional-testing-framework.