PHPackages                             joomla-projects/joomla-testing - 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. joomla-projects/joomla-testing

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

joomla-projects/joomla-testing
==============================

Joomla automated testing scripts with container capabilities

071.5k↓50%4PHP

Since Aug 24Pushed 5y ago12 watchersCompare

[ Source](https://github.com/joomla-projects/joomla-testing)[ Packagist](https://packagist.org/packages/joomla-projects/joomla-testing)[ RSS](/packages/joomla-projects-joomla-testing/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (3)Used By (0)

NOTE - This repository has been archived for now.

GSOC 2017 Parallel Testing Project
----------------------------------

[](#gsoc-2017-parallel-testing-project)

### Summary

[](#summary)

The project aims to reduce time of acceptance tests for Joomla extensions, with the initial focus on Weblinks.

This is made possible by running the tests in parallel in an environment of multiple Joomla servers and Selenium clients. The environment is automatically generated by the virtualisation project. Furthermore, a special algorithm has been designed and implemented to manage the optimal execution of the tasks, also taking account for their dependencies.

### Run the parallel testing module

[](#run-the-parallel-testing-module)

In order to run the tests, simply run the following command:

```
 vendor/bin/robo run:coordinator isacandrei weblinks container-test > coordinator.log 2>&1

```

The logs will be available on the coordinator.log file.

The extension acceptance tests logs are currently saved in the \_output folder of the extension.

The current setup has 5 servers and 3 clients. Therefore the expected behaviour is to run the first three tests, and when one finishes, run the one from the remaining ones. When another one finishes, the last test will be run.

At the end, a statistics of the tasks on each server is stored in the logs, summarising how many tasks are completed successfully and how many are failed.

### Documentation

[](#documentation)

1. [Documentation](https://docs.joomla.org/Parallel_Testing)
2. [First Post](https://community.joomla.org/gsoc-2017/3127-parallel-testing-gsoc-2017.html)
3. [Second Post](https://docs.google.com/document/d/1SH-6h994C_X1CGuBK7WDZWLPScz9QpI1ZuYqShN-3aI/edit?usp=sharing)
4. [Meeting reports](https://volunteers.joomla.org/teams/gsoc-17-parallel-testing)

Repositories List:
------------------

[](#repositories-list)

- [Weblinks](https://github.com/isacandrei/weblinks/tree/container-test)
- [Joomla Browser](https://github.com/isacandrei/joomla-browser/tree/container-test)
- [Virtualisation](https://github.com/isacandrei/virtualisation/tree/container-test)
- [Joomla Testing](https://github.com/isacandrei/joomla-testing/tree/container-test)
- [Joomla Testing Robo](https://github.com/isacandrei/joomla-testing-robo/tree/container-test)
- [Docker Joomla Automated Testing](https://github.com/isacandrei/docker-joomla-automated-testing/tree/container-test)

PR Commits Lists:
-----------------

[](#pr-commits-lists)

- [Joomla Browser](https://github.com/joomla-projects/joomla-browser/pull/140/commits)
- [Virtualisation 1](https://github.com/joomla-projects/virtualisation/pull/13/commits)
- [Virtualisation 2](https://github.com/joomla-projects/virtualisation/pull/14/commits)
- [Virtualisation 3](https://github.com/joomla-projects/virtualisation/pull/15/commits)
- [Joomla Testing 1](https://github.com/joomla-projects/joomla-testing/pull/1/commits)
- [Joomla Testing 2](https://github.com/joomla-projects/joomla-testing/pull/4/commits)
- [Weblinks 1](https://github.com/jatitoam/weblinks/pull/2/commits)
- [Weblinks 2](https://github.com/jatitoam/weblinks/pull/3/commits)
- [Docker Joomla Automated Testing](https://github.com/joomla-projects/docker-joomla-automated-testing/pull/2/commits)
- [Joomla Testing Robo 1](https://github.com/joomla-projects/joomla-testing-robo/pull/10/commits)
- [Joomla Testing Robo 2](https://github.com/joomla-projects/joomla-testing-robo/pull/12/commits)

All the PRs have been accepted and merged into the public repositories. The project is ready to use and will be integrated with Travis for Joomla extensions. The only dependency needed for each extension is the yml file with the required tests and working acceptance tests, all being described in the documentation listed above.

###  Health Score

29

—

LowBetter than 59% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity27

Limited adoption so far

Community16

Small or concentrated contributor base

Maturity44

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 60% 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.

### Community

Maintainers

![](https://www.gravatar.com/avatar/10b2f49e604583bbe4a444a3893954ec31d3dfa9a78d84550524964f1ab1b262?d=identicon)[jatitoam](/maintainers/jatitoam)

---

Top Contributors

[![jatitoam](https://avatars.githubusercontent.com/u/1500978?v=4)](https://github.com/jatitoam "jatitoam (3 commits)")[![puneet0191](https://avatars.githubusercontent.com/u/3048593?v=4)](https://github.com/puneet0191 "puneet0191 (1 commits)")[![zero-24](https://avatars.githubusercontent.com/u/2596554?v=4)](https://github.com/zero-24 "zero-24 (1 commits)")

### Embed Badge

![Health badge](/badges/joomla-projects-joomla-testing/health.svg)

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

###  Alternatives

[phpspec/prophecy

Highly opinionated mocking framework for PHP 5.3+

8.5k551.7M682](/packages/phpspec-prophecy)[brianium/paratest

Parallel testing for PHP

2.5k118.8M754](/packages/brianium-paratest)[beberlei/assert

Thin assertion library for input validation in business models.

2.4k96.9M570](/packages/beberlei-assert)[mikey179/vfsstream

Virtual file system to mock the real file system in unit tests.

1.4k108.0M2.7k](/packages/mikey179-vfsstream)[orchestra/testbench

Laravel Testing Helper for Packages Development

2.2k39.1M32.1k](/packages/orchestra-testbench)[phpspec/phpspec

Specification-oriented BDD framework for PHP 7.1+

1.9k36.7M3.1k](/packages/phpspec-phpspec)

PHPackages © 2026

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