magento / magento/magento2-functional-testing-framework
Support xUnit-compatible Output Format
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 154
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
### Preconditions
1. Magento 2.3.4-p2
2. PHP 7.2
3. MFTF 2.5.3
### Steps to reproduce
1. Run any MFTF test.
### Expected result
1. xUnit-compatible results are written somewhere.
### Actual result
1. Only Allure-compatible results are written to `dev/tests/acceptance/tests/_output/allure-results`.
### Background
Bitbucket Pipelines [only supports xUnit-compatible test reports](https://support.atlassian.com/bitbucket-cloud/docs/test-reporting-in-pipelines/).
Since [Codeception comes with JUnit XML output](https://codeception.com/docs/02-GettingStarted#reports), this could be "easy" to implement...?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MFTF test runner and its Codeception configuration, then run any MFTF test to inspect how output is currently written to dev/tests/acceptance/tests/_output/allure-results. Done means the run also produces an xUnit-compatible report suitable for Bitbucket Pipelines while preserving the existing Allure output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100