magento / magento/magento2-functional-testing-framework

Executing a Test included within a suite seperately

Open
#630 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
PHP
Stars
154
Forks
134
PR merge metrics
No merged PRs in 30d

Description

This is not a bug but rather a developer experience Issue.

### Summary (*)
It is not possible to run a test that is included within a suite independently which is states here in the [docs](https://devdocs.magento.com/mftf/docs/test.html#principles). You always have to either run the whole suite, change the suite to only contain the specific test or create a new suite only containing the test you want to run. This takes up time and is (from my point of view) annoying.

### Examples (*)
When having a failing test and the need to debug the test you will always have to change a suite before.
Example command:
`vendor/bin/mftf run:test AddressStateFieldShouldNotAcceptJustIntegerValuesTest`

I do not understand the intention behind this concept since you can run it "independently" as a single test within a separate suite. What is the reason it implemented this way and is it possible to change this behavior to be able to execute a test independently even if it's contained within a suite?

Contributor guide

Open the contributing guide

Research direction

Start with the documented test principles and the `vendor/bin/mftf run:test AddressStateFieldShouldNotAcceptJustIntegerValuesTest` entry point. Trace how a test included in a suite is selected, then verify that the command can run that test independently without changing or creating a suite.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
cli, testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.