This is the reference implementation of XP RFC #0303: Subcommands supporting Windows, Linux and Mac OS X.

$ curl -sSL https://bintray.com/artifact/download/xp-runners/generic/setup-7.1.2.sh | sh
# ...

$ composer global require xp-framework/core
# ...

$ xp version
XP 7.0.2 { PHP 7.0.3 & ZE 3.0.0 } @ Windows NT SLATE 10.0 build 10586 (Windows 10) i586
Copyright (c) 2001-2016 the XP group
FileSystemCL<$APPDATA/Composer/vendor/xp-framework/core/src/main/php>
FileSystemCL<$APPDATA/Composer/vendor/xp-framework/core/src/test/php>
FileSystemCL<$APPDATA/Composer/vendor/xp-framework/core/src/main/resources>
FileSystemCL<$APPDATA/Composer/vendor/xp-framework/core/src/test/resources>
FileSystemCL<.>

The following commands are builtin:

• version - Displays version and exits - also -v
• eval {code} - Evaluates code - also -e {code}
• write {code} - Evaluates code, writes result to Console - also -w {code}
• dump {code} - Evaluates code, var_dump()s result - also -d {code}
• help [{command}] - Displays help - also -?
• run {class} - Runs a class, class file or xar
• ar {operation} [{sources}] - Works with XAR archives

If no command line arguments are given, the help command is run. If command line arguments are given, but no command is passed, the command defaults to run.

Libraries may provide commands by adding a vendor binary to their composer.json named xp.{vendor}.{name}[.{command}] - for the test command, the entry is:

{
    "bin": ["bin/xp.xp-framework.unittest.test"]
}

The xp.{module}.{ucfirst(command)}Runner class serves as the entry point (if the command name is omitted, it will simply be xp.{module}.Runner).

By installing the package globally, it becomes available in any directory.

$ composer global require xp-framework/unittest
# ...

$ xp test -e '$this->assertTrue(true)'
[.]

♥: 1/1 run (0 skipped), 1 succeeded, 0 failed
Memory used: 1265.94 kB (1416.26 kB peak)
Time taken: 0.000 seconds

XP Runners know about Composer's filesystem locations and its dependency management. Thus, the above is the short form of ./xp.exe -m /path/to/unittest [-m /path/to/dependencies/of/unittest ...] xp.unittest.Runner ...

There are three execution models:

1. Run once, exit (this is the default)
2. Watch a directory, spawn process every time a change occurs (via -watch {directory})
3. Start the process, keep it running until exits with exitcode 0 or the user presses enter (via -supervise)

The second model is useful e.g. to implement continuous unittest running, see here.

Less configuration:

• The timezone is automatically mapped from Windows and need no longer be set via date.timezone
• If no use setting is defined, a globally or locally composer-installed framework will be used

Better Windows integration:

• ANSI color escape sequences are also supported when running in Windows Console