PHP Unitary is a lightweight, user-friendly PHP unit testing library designed to make writing and running tests for your PHP code simple. With an intuitive interface and robust validation options, Unitary enables developers to ensure their code is reliable and functions as intended.

By following a simple setup process, you can create and execute tests quickly, making it easier to maintain high-quality code and catch potential issues early in the development cycle.

The documentation is divided into several sections:

• Installation
• Guide
  • Create a Test File
  • Run the Tests
  • Configurations
• Example Breakdown
• Validation List
  • Data Type Checks
  • Equality and Length Checks
  • Numeric Range Checks
  • String and Pattern Checks
  • Required and Boolean-Like Checks
  • Date and Time Checks
  • Version Checks
  • Logical Checks

To install MaplePHP Unitary, run the following command:

composer require --dev maplephp/unitary

Unitary will, by default, find all files prefixed with "unitary-" recursively from your project's root directory (where your "composer.json" file exists).

Start by creating a test file with a name that starts with "unitary-", e.g., "unitary-lib-name.php". You can place the file inside tests/unitary-lib-name.php for example.

Note: All of your library classes should be automatically be autoloaded when used in test file!

<?php
// If you add the argument "true" to the Unit class, it will run in quiet mode
// and only report if it finds any errors.
$unit = new MaplePHP\Unitary\Unit();

// Add a title to your tests (optional)
$unit->addTitle("Testing MaplePHP Unitary library!");

// Begin by adding a test
$unit->add("Checking data type", function($inst) {
    // My test; this could be your class and method here
    $myStrVar = "Lorem ipsum dolor";
    $myIntVar = 998;
    
    // Each array item is a test for "$myStrVar"
    $inst->add($myStrVar, [
        "isString" => [],
        "length" => [1, 200]
    ]);
    
    // You can have multiple subtests in each test unit, but try to follow the unit's subject! 
    $inst->add($myIntVar, [
        "isInt" => [],
        "equal" => 998,
        "custom" => function($valid) use($myIntVar) {
            return ($myIntVar === 998);
        }
    ]);
    // Every test above will be successful!
});

$unit->execute();

The example above uses both built-in validation and custom validation (see below for all built-in validation options).

Now you are ready to execute the tests. Open your command line of choice, navigate (cd) to your project's root directory (where your composer.json file exists), and execute the following command:

./vendor/bin/unitary

And that is it. Your tests have been successfully executed.

You can change the default root testing path and exclude files or whole directories from the tests.

Note: The vendor directory will be excluded from tests by default. However, if you change the --path, you will need to manually exclude the vendor directory.

The path argument takes both absolute and relative paths. The command below will find all tests recursively from the "tests" directory.

./vendor/bin/unitary --path="./tests/"

The exclude argument will always be a relative path from the --path argument's path.

./vendor/bin/unitary --exclude="./tests/unitary-query-php, tests/otherTests/*, */extras/*"

This is a quick break down of the test file that you can read if you need. After the break-down I will list all available built in tests.

1. Instantiate the Unit class

   $unit = new MaplePHP\Unitary\Unit();

   • Purpose: Creates an instance of the Unit class from the MaplePHP\Unitary namespace.
   • Argument: true enables quiet mode, which means it will only report errors and not print out all test results.

2. Add a Title (Optional)

   $unit->addTitle("Testing MaplePHP Unitary library!");

   • Purpose: Adds a title to your test suite. This is optional and is used to give context or a name to your set of tests.

3. Start Adding a Test Unit

   $unit->add("Checking data type", function($inst) {
       // Your test code here -->
   });

   • Purpose: Begins a new test unit block.
   • Arguments:
     • "Checking data type" is the name of this test block.
     • A callback function that contains the actual tests. The $inst parameter represents an instance within this test block.

4. Add Tests for $myStrVar

   $inst->add($myStrVar, [
       "isString" => [],
       "length" => [1, 200]
   ]);

   • Purpose: Add individual tests for $myStrVar.
   • Arguments:
     • $myStrVar: The variable being tested.
     • An array of validation rules:
       • "isString" => []: Checks if $myStrVar is a string.
       • "length" => [1, 200]: Checks if the length of $myStrVar is between 1 and 200 characters.

8. Execute All Tests

   $unit->execute();

   • Purpose: Runs all the tests that have been defined. If the tests pass, it will be silent due to quiet mode. If any test fails, it will report the errors. ...

Each prompt can have validation rules and custom error messages. Validation can be defined using built-in rules (e.g., length, email) or custom functions. Errors can be specified as static messages or dynamic functions based on the error type.

1. isString

   • Description: Checks if the value is a string.
   • Usage: "isString" => []

2. isInt

   • Description: Checks if the value is an integer.
   • Usage: "isInt" => []

3. isFloat

   • Description: Checks if the value is a float.
   • Usage: "isFloat" => []

4. isBool

   • Description: Checks if the value is a boolean.
   • Usage: "isBool" => []

5. isArray

   • Description: Checks if the value is an array.
   • Usage: "isArray" => []

6. isObject

   • Description: Checks if the value is an object.
   • Usage: "isObject" => []

7. number

   • Description: Checks if the value is numeric.
   • Usage: "number" => []

8. equal

   • Description: Checks if the value is equal to a specified value.
   • Usage: "equal" => ["someValue"]

9. notEqual

   • Description: Checks if the value is not equal to a specified value.
   • Usage: "notEqual" => ["someValue"]

10. length

    • Description: Checks if the string length is between a specified start and end length.
    • Usage: "length" => [1, 200]

11. equalLength

    • Description: Checks if the string length is equal to a specified length.
    • Usage: "equalLength" => [10]

12. min

    • Description: Checks if the value is greater than or equal to a specified minimum.
    • Usage: "min" => [10]

13. max

    • Description: Checks if the value is less than or equal to a specified maximum.
    • Usage: "max" => [100]

14. positive

    • Description: Checks if the value is a positive number.
    • Usage: "positive" => []

15. negative

    • Description: Checks if the value is a negative number.
    • Usage: "negative" => []

16. pregMatch

    • Description: Validates if the value matches a given regular expression pattern.
    • Usage: "pregMatch" => ["a-zA-Z"]

17. atoZ

    • Description: Checks if the value consists of characters between a-z or A-Z.
    • Usage: "atoZ" => []

18. lowerAtoZ

    • Description: Checks if the value consists of lowercase characters between a-z.
    • Usage: "lowerAtoZ" => []

19. upperAtoZ

    • Description: Checks if the value consists of uppercase characters between A-Z.
    • Usage: "upperAtoZ" => []

20. hex

    • Description: Checks if the value is a valid hex color code.
    • Usage: "hex" => []

21. email

    • Description: Validates email addresses.
    • Usage: "email" => []

22. url

    • Description: Checks if the value is a valid URL (http|https is required).
    • Usage: "url" => []

23. phone

    • Description: Validates phone numbers.
    • Usage: "phone" => []

24. zip

    • Description: Validates ZIP codes within a specified length range.
    • Usage: "zip" => [5, 9]

25. domain

    • Description: Checks if the value is a valid domain.
    • Usage: "domain" => [true]

26. dns

    • Description: Checks if the host/domain has a valid DNS record (A, AAAA, MX).
    • Usage: "dns" => []

27. matchDNS

    • Description: Matches DNS records by searching for a specific type and value.
    • Usage: "matchDNS" => [DNS_A]

28. lossyPassword

    • Description: Validates a password with allowed characters [a-zA-Z\d$@$!%*?&] and a minimum length.
    • Usage: "lossyPassword" => [8]

29. strictPassword

    • Description: Validates a strict password with specific character requirements and a minimum length.
    • Usage: "strictPassword" => [8]

30. required

    • Description: Checks if the value is not empty (e.g., not "", 0, NULL).
    • Usage: "required" => []

31. isBoolVal

    • Description: Checks if the value is a boolean-like value (e.g., "on", "yes", "1", "true").
    • Usage: "isBoolVal" => []

32. date

    • Description: Checks if the value is a valid date with the specified format.
    • Usage: "date" => ["Y-m-d"]

33. dateTime

    • Description: Checks if the value is a valid date and time with the specified format.
    • Usage: "dateTime" => ["Y-m-d H:i"]

34. age

    • Description: Checks if the value represents an age equal to or greater than the specified minimum.
    • Usage: "age" => [18]

35. validVersion

    • Description: Checks if the value is a valid version number.
    • Usage: "validVersion" => [true]

36. versionCompare

    • Description: Validates and compares if a version is equal/more/equalMore/less than withVersion.
    • Usage: "versionCompare" => ["1.0.0", ">="]

37. oneOf

    • Description: Validates if one of the provided conditions is met.
    • Usage: "oneOf" => [["length", [1, 200]], "email"]

38. allOf

    • Description: Validates if all of the provided conditions are met.
    • Usage: "allOf" => [["length", [1, 200]], "email"]