Download the PHP package magento/magento2-functional-testing-framework without Composer

On this page you can find all versions of the php package magento/magento2-functional-testing-framework. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package magento2-functional-testing-framework

Magento Functional Testing Framework (MFTF)

Installation

For the installation guidelines and system requirements, refer to Getting Started.

Contributing

We would appreciate your contributions to new components or new features, changes to the existing features, tests, documentation, specifications, bug fixes, optimizations, or just good suggestions. Report about an issue or request features opening a GitHub issue. Learn more about contributing in our Contribution Guidelines.

If you want to participate in the documentation work, see DevDocs Contributing.

Labels Applied by the MFTF Team

Refer to the tables with descriptions of each label below. These labels are applied by the MFTF development team to community contributed issues and pull requests, to communicate status, impact, or which team is working on it.

Pull Request Status

Label Description
accept The pull request has been accepted and will be merged into mainline code.
reject The pull request has been rejected and will not be merged into mainline code. Possible reasons can include but are not limited to: issue has already been fixed in another code contribution, or there is an issue with the code contribution.
needsUpdate The Magento Team needs additional information from the reporter to properly prioritize and process the pull request.

Issue Resolution Status

Label Description
acknowledged The Magento Team has validated the issue and an internal ticket has been created.
needsUpdate The Magento Team needs additional information from the reporter to properly prioritize and process the issue or pull request.
cannot reproduce The Magento Team has not confirmed that this issue contains the minimum required information to reproduce.
non-issue The Magento Team has not recognized any issue according to provided information.

Domains Impacted

Label Description
PROD Affects the Product team (mostly feature requests or business logic change).
DOC Affects Documentation domain.
TECH Affects Architect Group (mostly to make decisions around technology changes).

Type

Label Description
bugfix The issue or pull request relates to bug fixing.
enhancement The issue or pull request that raises the MFTF to a higher degree (for example new features, optimization, refactoring, etc).

Reporting Security Issues

To report security vulnerabilities or learn more about reporting security issues in Magento software or web sites visit the Magento Bug Bounty Program on hackerone. Please create a hackerone account there to submit and follow-up on your issue.

Stay up-to-date on the latest security news and patches for Magento by signing up for Security Alert Notifications.

License

Each Magento source file included in this distribution is licensed under AGPL 3.0.

See the [email protected] for a copy.

All versions of magento2-functional-testing-framework with dependencies

PHP Build Version
Package Version
Requires php Version >=7.4
ext-curl Version *
ext-dom Version *
ext-iconv Version *
ext-intl Version *
ext-json Version *
ext-openssl Version *
allure-framework/allure-codeception Version ^1.4
aws/aws-sdk-php Version ^3.132
codeception/codeception Version ^4.1
codeception/module-asserts Version ^1.1
codeception/module-sequence Version ^1.0
codeception/module-webdriver Version ^1.0
composer/composer Version ^1.9 || ^2.0, !=2.2.16
csharpru/vault-php Version ^4.2.1
guzzlehttp/guzzle Version ^7.3.0
laminas/laminas-diactoros Version ^2.8
monolog/monolog Version ^2.3
mustache/mustache Version ~2.5
nikic/php-parser Version ^4.4
php-webdriver/webdriver Version ~1.12.0
spomky-labs/otphp Version ^10.0
symfony/console Version ^5.4
symfony/dotenv Version ^5.4
symfony/finder Version ^5.4
symfony/http-foundation Version ^5.4
symfony/mime Version ^5.4
symfony/process Version ^5.4
weew/helpers-array Version ^1.3
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package magento/magento2-functional-testing-framework contains the following files

Loading the files please wait ....