PHPackages                             elgentos/testing-suite - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Testing &amp; Quality](/categories/testing)
4. /
5. elgentos/testing-suite

ActiveLibrary[Testing &amp; Quality](/categories/testing)

elgentos/testing-suite
======================

Elgentos Testing Suite

v1.3.0(6mo ago)5136.1k↓34.7%[3 issues](https://github.com/elgentos/testing-suite/issues)5

Since Aug 2Pushed 6mo ago10 watchersCompare

[ Source](https://github.com/elgentos/testing-suite)[ Packagist](https://packagist.org/packages/elgentos/testing-suite)[ RSS](/packages/elgentos-testing-suite/feed)WikiDiscussions main Synced 2w ago

READMEChangelog (9)Dependencies (5)Versions (11)Used By (5)

elgentos/testing-suite
======================

[](#elgentostesting-suite)

This uses `youwe/testing-suite`, but we can add/change tests/packages/configuration as we like.

Installation
------------

[](#installation)

```
composer require elgentos/testing-suite --dev

```

Configuration
-------------

[](#configuration)

Add this to your `phpstan.neon`;

```
includes:
    - vendor/bitexpert/phpstan-magento/extension.neon

```

Baselines
---------

[](#baselines)

When implementing this into an existing project, you might want to consider generating baselines so the tests will pass without having to fix *all* the files.

### Phpstan baseline

[](#phpstan-baseline)

Generate the baseline (replace `app/design/frontend app/code` with your dirs);

```
vendor/bin/phpstan analyse --level 4 --configuration ./phpstan.neon app/code app/design/frontend --generate-baseline

```

Then add this to your `phpstan.neon`;

```
includes:
  - phpstan-baseline.neon

```

### Phpmd baseline

[](#phpmd-baseline)

Generate the baseline (replace `app/design/frontend,app/code` with your dirs);

```
vendor/bin/phpmd app/design/frontend,app/code text ./phpmd.xml --generate-baseline

```

### Phpcs baseline

[](#phpcs-baseline)

Generate the baseline (replace `app/design/frontend app/code` with your dirs);

```
vendor/bin/phpcs app/design/frontend app/code --extensions=php,phtml --report=\\DR\\CodeSnifferBaseline\\Reports\\Baseline --report-file=phpcs.baseline.xml --basepath=.\

```

Run it
------

[](#run-it)

```
vendor/bin/grumphp run

```

Gitlab CI/CD
============

[](#gitlab-cicd)

If you are implementing this in an existing project, do the work to make all tests pass (or add the baselines). As soon as all tests pass, make sure to make the static testing job required in our internal Gitlab CI/CD, by adding this to the projects' `.gitlab-ci.yml`:

```
static:testingsuite:
  allow_failure: false

```

Configure Phpstorm
------------------

[](#configure-phpstorm)

This assumes you're using [our Docker environment](https://github.com/JeroenBoersma/docker-compose-development/).

1. Go to **Settings &gt; PHP &gt; Quality Tools**
2. Perform these steps for `PHP_CodeSniffer`, `Mess Detector`, `PHP CS Fixer` and `PHPStan`:
    1. Click on the `...` behind the Configuration dropdown.
    2. Click on the blue `+` sign.
    3. Choose `development_php81:latest`, click OK
    4. Click Ok
3. Go to **Settings &gt; Editor &gt; Inspections &gt; PHP &gt; Quality Tools**
    1. Disable `PHP CS Fixer validation`
    2. Enable `PHP Mess Detector validation`
        1. Under "Custom Rulesets", clear the list and add `vendor/youwe/coding-standard-magento2/src/YouweMagento2/`
        2. Click Apply
    3. Enable `PHP_CodeSniffer validation`
        1. Under "Coding standard", choose "YouweMagento2"
        2. Click Apply
    4. Enable `PHPStan validation`
        1. Make sure the Configuration file and the Autoload file paths are empty
        2. Make sure you have the `phpstan.neon` file in your project root
        3. Click Apply
    5. Disable `Psalm validation`

###  Health Score

44

—

FairBetter than 90% of packages

Maintenance54

Moderate activity, may be stable

Popularity36

Limited adoption so far

Community20

Small or concentrated contributor base

Maturity55

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 63.6% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~141 days

Recently: every ~289 days

Total

10

Last Release

208d ago

Major Versions

0.2.2 → v1.3.02026-01-22

### Community

Maintainers

![](https://www.gravatar.com/avatar/88a6d8dc588e8f2a0948335563a754687f71304f0bd3b7f7049d4bcdc00a563c?d=identicon)[peterjaap](/maintainers/peterjaap)

---

Top Contributors

[![peterjaap](https://avatars.githubusercontent.com/u/431360?v=4)](https://github.com/peterjaap "peterjaap (14 commits)")[![wahidnory](https://avatars.githubusercontent.com/u/3277057?v=4)](https://github.com/wahidnory "wahidnory (5 commits)")[![WouterSteen](https://avatars.githubusercontent.com/u/5089604?v=4)](https://github.com/WouterSteen "WouterSteen (3 commits)")

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/elgentos-testing-suite/health.svg)

```
[![Health](https://phpackages.com/badges/elgentos-testing-suite/health.svg)](https://phpackages.com/packages/elgentos-testing-suite)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
