API functional tests drop all tables from main database

zunsakai commented 2 years ago

Preconditions and environment

Magento 2.4.5
PHP 8.1
Mysql 8.0

Steps to reproduce

Install magento live site into database magento_db
Create separate database magento_functional_tests
In folder dev/tests/api-functional/config, copy install-config-mysql.php.dist to install-config-mysql.php, post-install-setup-command-config.php.dist to post-install-setup-command-config.php
Write down db name (magento_functional_tests), user, password,... into dev/tests/api-functional/config/install-config-mysql.php

In dev/tests/api-functional/phpunit_graphql.xml.dist add new testsuite base on my module

<testsuite name="MYVENDOR_FUNCTIONAL_TESTS_APP_CODE">
<directory>../../../app/code/MyVendor/*/Test/Functional</directory>
</testsuite>

In dev/tests/api-functional/phpunit_graphql.xml.dist set TESTS_BASE_URL to local domain, TESTS_MAGENTO_INSTALLATION to enabled
cd dev/tests/api-functional
../../../vendor/bin/phpunit --configuration ../../../dev/tests/api-functional/phpunit_graphql.xml.dist --testsuite "MYVENDOR_FUNCTIONAL_TESTS_APP_CODE"

Expected result

Web Api tests should run on test database as configured in step 4 (magento_functional_tests) Main database is intact.

Actual result

Test database is intact. All tables are deleted from main database (magento_db)

Additional information

I don't know why it affects the main database, but in the scope of testing, don't touch the main data.

Release note

No response

Triage and priority

[ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
[ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
[X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
[ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
[ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

m2-assistant[bot] commented 2 years ago

Hi @kylepham103. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

Summary of the issue
Information on your environment
Steps to reproduce
Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

Join Magento Community Engineering Slack and ask your questions in #github channel.

:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

zunsakai commented 2 years ago

I also found a few similar tickets here https://github.com/magento/magento2/issues/26875 https://github.com/magento/magento2/issues/18769 But I have not found any solution or explanation for this problem. I tried other configs, but main database is always affected

chalov-anton commented 2 years ago

@magento give me 2.4-develop instance

magento-deployment-service[bot] commented 2 years ago

Hi @chalov-anton. Thank you for your request. I'm working on Magento instance for you.

magento-deployment-service[bot] commented 2 years ago

Hi @chalov-anton, here is your Magento Instance: https://8f1a02000c0d783ab56d9c1b872b7876.instances.magento-community.engineering Admin access: https://8f1a02000c0d783ab56d9c1b872b7876.instances.magento-community.engineering/admin_5fbc Login: 8e4bf987 Password: 2c754f4e0522

gwharton commented 1 year ago

Also see the following related

https://github.com/magento/magento2/issues/27213

And the following with a detailed analysis of why it does what it does when I looked at it last year.

https://github.com/magento/magento2/issues/33696

m2-assistant[bot] commented 1 year ago

Hi @engcom-November. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
[ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop branch
Details
- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 5. Add label Issue: Confirmed once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

engcom-November commented 1 year ago

Verified the issue on Magento 2.4-develop instance and the issue is reproducible. On using separate database while running API functional tests, all the data from main database is removed. Hence confirming this issue.

github-jira-sync-bot commented 1 year ago

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-7088 is successfully created for this GitHub issue.

m2-assistant[bot] commented 1 year ago

:white_check_mark: Confirmed by @engcom-November. Thank you for verifying the issue.
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

cmuench commented 1 year ago

Where can we see the update of this issue? Anyone here?

cmuench commented 1 year ago

Anyone working on that issue?

JesKingDev commented 1 year ago

This is bananas. +1 on getting this fixed.

omarabdelaz1z commented 8 months ago

Any updates? Still occurs in 2.4.6 p-3

magento / magento2