aligent/magento-unit-test-pipe repository overview

⁠Aligent Magento Unit Testing Pipe

A bitbucket pipe for running Magento unit tests

It is designed to be run in parallell, so you can leverage bitbucket parallel steps. Example pipeline⁠

The pipe detects a composer.lock file and installs packages. If no composer.lock file is found, the pipe will create a new magento project.

⁠Environment Variables

⁠Example Pipeline

image: php:8.1

definitions:
  steps:
    - step: &unit
        name: "Unit Tests"
        caches:
          - docker
        script:
          - pipe: docker://aligent/magento-unit-test-pipe:8.1
            variables:
              TESTS_PATH: ../../../vendor/magento/magento2-base/dev/tests/integration/testsuite/Magento/Framework/MessageQueue/TopologyTest.php
              REPOSITORY_URL: https://mirror.mage-os.org/
              GROUP: --group group_a,group_b

pipelines:
  branches:
    production:
      - step: *unit

⁠Running Locally

The pipe can be run locally in order to allow for unit testing without running within Bitbucket.

/build should be used as a volume for the current directory, and should also be used as the working directory.

When running for a stand-alone module (i.e. without a composer.lock file), you will need to specify the COMPOSER_PACKAGES environment variable) Example:

docker run -v $PWD:/build --env REPOSITORY_URL=https://mirror.mage-os.org --env COMPOSER_PACKAGES=aligent/magento-unit-tests-path --workdir=/build aligent/magento-unit-test-pipe:8.1

⁠Contributing

Commits published to the main branch will trigger an automated build for the latest tag in DockerHub