https://github.com/subiabre/phpmetro
Streamlined sampling and analysis of results in PHP.
https://github.com/subiabre/phpmetro
analysis sampling statistics testing
Last synced: 4 months ago
JSON representation
Streamlined sampling and analysis of results in PHP.
- Host: GitHub
- URL: https://github.com/subiabre/phpmetro
- Owner: subiabre
- License: mit
- Created: 2020-02-16T22:21:44.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2022-01-23T19:52:44.000Z (about 4 years ago)
- Last Synced: 2025-08-11T03:23:05.735Z (8 months ago)
- Topics: analysis, sampling, statistics, testing
- Language: PHP
- Homepage:
- Size: 232 KB
- Stars: 9
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# PHPMetro
Streamlined statistical sampling and analysis of results.
[](https://packagist.org/packages/subiabre/phpmetro)
[](https://packagist.org/packages/subiabre/phpmetro)
[](https://codecov.io/gh/subiabre/phpmetro)
[](//packagist.org/packages/subiabre/phpmetro)
[](https://packagist.org/packages/subiabre/phpmetro)
PHPMetro provides the foundation to perform sampling and analysis of data in a PHPUnit-like fashion, aiming to make it as easy as possible for PHP developers to compose analysis suites and get statistical results.
1. [About](#About)
2. [Requirements](#Requirements)
3. [Installation](#Installation)
4. [Configuration](#Configuration)
5. [Usage (basic tutorial)](#Usage)
6. [Support](#Support)
---
## About
I created this package on winter 2019 because I was working on a project that required me to not only perform unit and functional tests of my code, but to also create and perform several statistical analyses of my code. PHPMetro was my response to that requirement.
>**WARNING**: Despite the origin of this project being that of a professional environment, it's not granted to be suitable for all production environments.
## Requirements
- PHP >= 7.2*
- [Composer](https://getcomposer.org)
*Package should be compatible with older versions of PHP down to 5.x, but it's not granted.
## Installation
PHPMetro is distributed on [packagist](https://packagist.org/packages/subiabre/phpmetro).
```console
$ composer require --dev subiabre/phpmetro
```
Once installed you'll get the phpmetro binary in your bin folder, by default **vendor/bin**. After installation you'll want to run `composer suggests subiabre/phpmetro` to see some more libraries you'll find useful when writing your analyses, as PHPMetro only contains a basic toolset for describing analysis cases with an specific workflow, and a runner to perform all our analyses based on a given configuration.
## Configuration
PHPMetro **needs** to be fed a `.xml` config file on run. This file will tell where to search for our Analysis classes and how to run them.
### Getting the template configuration
Easiest way is to copy to the root of your project the example config file at your vendor folder:
```console
$ cp vendor/subiabre/phpmetro/phpmetro.xml phpmetro.xml
```
The binary will automatically search for any `phpmetro.xml` at the root folder and load it unless you specify a location, you can use that to use and run several different configurations and suites.
```console
$ ./vendor/bin/phpmetro path/to/config.xml
```
### Configuring
The *.xml* config file specifies general run directives for the PHPMetro binary as well as defines the analyses by suite groups.
The default file can be environment specific: `phpmetro.xml.local` will override `phpmetro.xml.dist` and this will override `phpmetro.xml`.
1. [Configuring PHPMetro](#Configuring-PHPMetro)
2. [Configuring Suites](#Configuring-Suites)
#### Configuring PHPMetro
```xml
...
```
The two attributes you see are required and they mean:
- **verbose**: When set to "true" PHPMetro will display additional run info. Equals to running the command with the `-v` flag.
There are no more run configurations. The runner will automatically fetch files from the suites you define. You can set more configurations per suite.
#### Configuring Suites
```xml
MyApp\Tests\Metro
tests/Metro
```
Suites must be inside the `` tag. Each suite accepts the following attributes:
- **name**: The display name of the suite. Required.
- **suffix**: Any combinations of letters that the analysis class files use as suffix. Optional. Defaults to "Analysis".
- **ignore**: When set to "true" it will indicate the runner to skip the execution of that suite. Optional. Defaults to "false".
>**NOTE**: Suffixes don't necessarily have to include the '.php' file extension. In fact the suite right-trims it from the suffix.
Inside each suite there must be two more tags specificating:
- **namespace**: The common namespace for the suite classes.
- **directory**: The folder where all the classes are at.
>**NOTE**: You must adhere to the [PSR-4](https://getcomposer.org/doc/04-schema.md#psr-4) specification when filenaming your Analyses. If you have an Analysis with the namespace `MyApp\Tests\Foo\BarAnalysis`, for this class to be properly identified by PHPMetro it will have to be located at `tests/Foo/BarAnalysis.php`.
## Usage
Say you have your own random number generator, `MyApp\RandomNumber`, and want to see some statistics about it. PHPMetro is your package for that! Let's put it under "Analysis".
### Creating an Analysis class
An *Analysis* is an special class that extends from `AnalysisCase` and contains a set up with samples and several tests over the samples.
```php
addSample('RandomNumber', 100, function(): int {
$randomNumber = new RandomNumber();
return $randomNumber->new();
});
}
```
To add data to a sample we use the `addSample` function, this function takes exactly 3 parameters:
- **$name**: The sample name. String.
- **$size**: The sample size in number of records, i.e the number of times to perform the function. Integer.
- **$function**: The function to be run on each iteration of the sample. Needs to specify a return a value. Callable.
>**NOTE**: Function calls that don't specify a return a value will not generate a Sample.
The `setUp` method is required by the `AnalysisInterface`. All analyses must implement this method with the purpose of being run before test methods in the Analysis.
You can call to `addSample` anywhere inside your class methods actually, this function will hold the execution of the runner until it finishes adding records. However it is recommended that you add your Samples on set up for performance and maintainability reasons.
>**NOTE**: Unlike other testing frameworks and libraries, PHPMetro will run the method `setUp` only once before running all tests instead of once before each test.
Now that there is Sample data we can start performing some calculations on it. For that you must simply just add Test methods in your class.
### Writing Test methods
A *Test* is an special class method inside your Analysis class that performs some kind of calculation and returns the result. These methods must match the regular expression `test[A-Za-z09]*` and return a basic data type.
>**WARNING**: Tests that return complex data types such as arrays or objects that can't be typecasted to strings will throw an error exception and stop the PHPMetro run.
>**NOTE**: Tests that don't specify a return type will be ignored and not executed.
For example, we want to test what's the median average of the generated random numbers.
Our Analysis class should look like this:
```php
addSample('RandomNumbers', 100, function() {
$randomNumber = new RandomNumber();
return $randomNumber->new();
});
}
public function testMedianAverage(): int
{
$sample = $this->getSample('RandomNumbers');
return Average::median($sample);
}
}
```
To calculate it we first accessed the sample we added on set up with `getSample`, and then passed it to [MathPHP](https://packagist.org/packages/markrogoyski/math-php)'s `Average` to calculate the median for us.
You can keep writing more Tests to calculate different things with your Samples. Write Tests as you need them.
Finally, to run the Analyses just run the binary:
```console
$ ./vendor/bin/phpmetro
```
Your Tests results should start appearing on your console screen.
>You can check more usage examples inside `tests/Self` folder. Which is the self analysis suite described in `tests/phpmetro.xml`.
## Support
You can support this project by contributing to open issues or creating pull requests to improve/fix existing code. Contributors are welcome.
If you liked this package give it a star or tell a friend about it.
If you have any doubt or commentary, [contact me](mailto:subiabrewd@mail.com).
Thank you!