Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MFTF: Storefront Contact Us Form Submitting #29037

Open
wants to merge 9 commits into
base: 2.4-develop
Choose a base branch
from
Open

MFTF: Storefront Contact Us Form Submitting #29037

wants to merge 9 commits into from

Conversation

DmitryTsymbal
Copy link
Contributor

@DmitryTsymbal DmitryTsymbal commented Jul 8, 2020 •
edited by m2-assistant bot
Loading

This PR contains two MFTF tests for submitting "Contact Us" form on storefront.

Steps to reproduce:

1 - Navigate to "Contact Us" page

2 - Fill in all required fields with valid data

3 - Submit the form

4 - Perform Assertions

5 - Fill in email field with invalid email address

6 - Try submit the form

7 - Perform assertions

Resolved issues:

  1. resolves [Issue] MFTF: Storefront Contact Us Form Submitting #29085: MFTF: Storefront Contact Us Form Submitting

@m2-assistant
Copy link

m2-assistant bot commented Jul 8, 2020

Hi @DmitryTsymbal. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

@magento-engcom-team magento-engcom-team added Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner labels Jul 8, 2020
@dmytro-ch dmytro-ch self-assigned this Jul 8, 2020
@dmytro-ch
Copy link
Contributor

@magento run all tests

@dmytro-ch dmytro-ch added Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: MFTF test coverage labels Jul 10, 2020
@magento-engcom-team
Copy link
Contributor

Hi @dmytro-ch, thank you for the review.
ENGCOM-7818 has been created to process this Pull Request

@engcom-Alfa engcom-Alfa self-assigned this Jul 13, 2020
@engcom-Alfa
Copy link
Contributor

@magento create issue

@m2-assistant m2-assistant bot mentioned this pull request Jul 13, 2020
Open
@ghost ghost added Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. Priority: P3 May be fixed according to the position in the backlog. labels Jul 13, 2020
@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

@engcom-Echo engcom-Echo self-assigned this Jul 13, 2020
@engcom-Echo engcom-Echo added the QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) label Jul 13, 2020
@engcom-Alfa engcom-Alfa removed the QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) label Jul 13, 2020
@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Alfa engcom-Alfa added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Priority: P3 May be fixed according to the position in the backlog. and removed Priority: P3 May be fixed according to the position in the backlog. Priority: P2 A defect with this priority could have functionality issues which are not to expectations. labels Aug 3, 2022
@engcom-Alfa engcom-Alfa removed the Priority: P3 May be fixed according to the position in the backlog. label Aug 3, 2022
@engcom-Alfa engcom-Alfa added the Priority: P3 May be fixed according to the position in the backlog. label Aug 3, 2022
@engcom-Alfa
Copy link
Contributor

@magento run Functional Tests B2B

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@engcom-Lima engcom-Lima self-assigned this Sep 5, 2023
@engcom-Lima
Copy link
Contributor

✔️ QA Passed

No manual testing is required

@engcom-Lima
Copy link
Contributor

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@engcom-Dash engcom-Dash self-assigned this Sep 13, 2024
@engcom-Dash
Copy link
Contributor

@magento run all tests

@engcom-Dash
Copy link
Contributor

@magento run all tests

@engcom-Dash
Copy link
Contributor

engcom-Dash commented Oct 3, 2024 •
edited
Loading

The Functional B2B test failures are not consistent in recent 2 builds. Seems to be flaky, hence moving it to Merge in Progress.
Run 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/29037/1efa1595198e039b74d508ffb3072acb/Functional/allure-report-b2b/index.html#categories/39002bb4b823f2d59e22404a186a7115/342c58aad3915288/
image

Run 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/29037/a0c7fabef195972cd7299abeea41b8e4/Functional/allure-report-b2b/index.html#categories/a644910ae0cb11e839a98baa21929b76/6ea694f657a93eeb/
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@slavvka slavvka slavvka requested changes

@dmytro-ch dmytro-ch dmytro-ch approved these changes

Assignees

@slavvka slavvka

@dmytro-ch dmytro-ch

@engcom-Alfa engcom-Alfa

@engcom-Echo engcom-Echo

@engcom-Lima engcom-Lima

@engcom-Dash engcom-Dash

Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: MFTF test coverage Component: Contact Component: Customer Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner Priority: P3 May be fixed according to the position in the backlog. Progress: ready for testing QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Pull Requests Dashboard
Status: Merge in Progress
Milestone
2.4.1
Development

Successfully merging this pull request may close these issues.

[Issue] MFTF: Storefront Contact Us Form Submitting
8 participants
@DmitryTsymbal @dmytro-ch @magento-engcom-team @engcom-Alfa @engcom-Echo @engcom-Lima @engcom-Dash @slavvka