Skip to content

Decomposition of dev/tests testsuites across corresponding modules #28012

Open
@bartoszkubicki

Description

@bartoszkubicki

Summary (*)

Magento 2.3 or 2.4. There are a lot of tests inside dev/tests directory, which violates modularity of platform, because while uninstalling (I mean completely removing) package from vendor tests stays in dev/tests. Wouldn't be better to spread them across corresponding modules? What if, I would like to uninstall module Magento_Wishlist and still run all integration tests? I still will have its tests in dev/tests/integration/testsuite/Magento/Wishlist, which won't work if I remove composer package with physical code.

Examples (*)

Test inside dev/tests/integration/testsuite/Magento/*.

Proposed solution

Copy-paste modules tests - I could start with integration ones into corresponding modules, so testsuite is decoupled from fixed modules set.

Metadata

Metadata

Labels

Issue: Format is validGate 1 Passed. Automatic verification of issue format passedPriority: P3May be fixed according to the position in the backlog.Progress: PR in progressReported on 2.3.xIndicates original Magento version for the Issue report.Severity: S4Affects aesthetics, professional look and feel, “quality” or “usability”.Triage: Dev.ExperienceIssue related to Developer Experience and needs help with Triage to Confirm or Reject itfeature request

Type

No type

Projects

Status

Pull Request in Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions