ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

PHPUnit​Kit

by gerardroche ST3

PHPUnit support for Sublime Text 3

Labels php, phpunit, testing, tdd

Details

Installs

  • Total 5K
  • Win 3K
  • Mac 1K
  • Linux 1K
Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7 Jan 6 Jan 5 Jan 4 Jan 3 Jan 2 Jan 1 Dec 31 Dec 30 Dec 29 Dec 28 Dec 27 Dec 26 Dec 25 Dec 24 Dec 23 Dec 22 Dec 21 Dec 20 Dec 19 Dec 18 Dec 17 Dec 16 Dec 15 Dec 14 Dec 13 Dec 12 Dec 11
Windows 0 1 0 0 3 3 1 0 2 3 1 0 3 1 0 2 1 1 4 3 0 2 4 2 0 0 0 1 1 2 4 3 1 1 1 2 3 4 0 2 4 2 1 1 2 1
Mac 0 0 1 1 0 0 1 0 1 1 1 1 1 0 0 0 2 2 0 0 0 0 1 2 0 0 1 2 0 0 0 1 0 0 0 1 1 2 0 1 2 0 0 0 0 1
Linux 0 0 1 3 2 1 1 1 4 0 3 1 1 1 2 1 2 1 3 0 1 0 2 0 0 1 0 0 0 2 4 0 0 0 1 0 2 0 3 1 2 0 1 3 1 1

Readme

Source
raw.​githubusercontent.​com

Sublime PHPUnitKit

PHPUnit support for Sublime Text.

Travis CI Build Status AppVeyor Build status Coveralls Coverage Status Codecov Coverage Status Minimum Sublime Version Latest Stable Version GitHub stars Downloads

Screenshot

Features

  • Run Test File
  • Run Test Suite
  • Run Nearest Test
  • Run Last Test
  • Fully customisable configuration
  • Supports Composer installed PHPUnit
  • Supports colour results, diffs, errors, etc.
  • Jump to next and jump to previous failure

Installation

Package Control installation

The preferred method of installation is Package Control.

Manual installation

Close Sublime Text, then download or clone the repository to a directory named PHPUnitKit in the Sublime Text Packages directory for your platform:

OS | Command – | —– Linux | git clone https://github.com/gerardroche/sublime-phpunit.git ~/.config/sublime-text-3/Packages/PHPUnitKit OSX | git clone https://github.com/gerardroche/sublime-phpunit.git ~/Library/Application\ Support/Sublime\ Text\ 3/Packages/PHPUnitKit Windows | git clone https://github.com/gerardroche/sublime-phpunit.git %APPDATA%\Sublime/ Text/ 3/Packages/PHPUnitKit

Commands

All of the following commands are available via the Command Palette (press Ctrl+Shift+p (Win, Linux) or Cmd+Shift+p (OS X)) and are all prefixed with “PHPUnit: ”.

command description
TestSuite Runs the whole test suite (if the current file is a test file, runs that framework's test suite).
TestFile In a test file runs all tests in the current file, otherwise runs that file's tests.
TestNearest In a test file runs the test nearest to the cursor, otherwise runs that file's tests.
TestLast Runs the last test.
TestVisit Visits the test file from which you last run your tests (useful when you're trying to make a test pass, and you dive deep into application code and close your test buffer to make more space, and once you've made it pass you want to go back to the test file to write more tests).
TestSwitch In a test file opens the file under test, otherwise opens the test file.
TestResults Opens the test results panel.
TestCancel Cancels the test runner.
TestCoverage Opens the code coverage report in default browser.
ToggleOption Toggles PHPUnit options.

Key Bindings

Add your preferred key bindings via Menu > Preferences > Key Bindings or the Command Palette (press Ctrl+Shift+p (Win, Linux) or Cmd+Shift+p (OS X), select “Preferences: Key Bindings” and press enter).

[
    { "keys": ["ctrl+shift+a"], "command": "phpunit_test_suite" },
    { "keys": ["ctrl+shift+c"], "command": "phpunit_test_cancel" },
    { "keys": ["ctrl+shift+f"], "command": "phpunit_test_file" },
    { "keys": ["ctrl+shift+l"], "command": "phpunit_test_last" },
    { "keys": ["ctrl+shift+n"], "command": "phpunit_test_nearest" },
    { "keys": ["ctrl+shift+r"], "command": "phpunit_test_results" },
    { "keys": ["ctrl+shift+s"], "command": "phpunit_test_switch" },
    { "keys": ["ctrl+shift+v"], "command": "phpunit_test_visit" }
]
key description
F4 Jump to Next Failure
Shift+F4 Jump to Previous Failure

Configuration

You can configure the plugin via Menu > Preferences > Settings or the Command Palette (press Ctrl+Shift+p (Win, Linux) or Cmd+Shift+p (OS X), select “Preferences: Settings” and press enter).

key description type default
phpunit.options Default options to use when running PHPUnit. dict {}
phpunit.composer Use PHPUnit installed by Composer? boolean true
phpunit.on_post_save List of events to trigger when a file is saved. list []
phpunit.php_executable Path to PHP executable. string Use system PATH
phpunit.php_versions_path Path to phpenv versions. string ~/.phpenv/versions
phpunit.save_all_on_run Save all dirty buffers before running tests. boolean true
phpunit.strategy Execution environment. string default

phpunit.options

If you want some CLI options to stick around, you can configure them in your global preferences:

"phpunit.options": {
    "colors=never": true,
    "coverage-html": "build/coverage",
    "no-coverage": true,
    "d": ["display_errors=1", "xdebug.scream=0"]
}

The above transforms the options and passes them to the PHPUnit executable:

-d "display_errors=1" -d "xdebug.scream=0" --colors=never --coverage-html build/coverage --no-coverage

phpunit.composer

When enabled, the test runner will use the PHPUnit executable installed by Composer, otherwise the system PATH will be used to find the executable. Composer support is enabled by default.

"phpunit.composer": true

phpunit.on_post_save

The “on post save” option allows you to trigger events after you save a file, for example you run the test file command (currently this is the only event supported). Defaults to [] (no events).

event description
run_test_file Runs the the “test file” command for the active view.
"phpunit.on_post_save": ["run_test_file"]

phpunit.php_executable

You can instruct the test runner to use a custom PHP executable, otherwise the system PATH is used to find the executable.

"phpunit.php_executable": "~/.phpenv/versions/7.3.1/bin/php"

phpunit.save_all_on_run

You can automatically save all views that have unsaved buffers (dirty buffers) before tests are run. Defaults to true.

"phpunit.save_all_on_run": true

phpunit.strategy

You can run tests using different execution environments. Here is a table of available environments. The default is to use Sublime's builtin build panel.

strategy identifier description
Panel default Runs test commands in a panel at the bottom of your editor window.
iTerm2.app iterm Sends test commands to iTerm2 >= 2.9 (useful in MacVim GUI).
"phpunit.strategy": "iterm"

Custom commands

Aside from the main commands out-of-the-box, you can create your own custom test commands. The commands phpunit_test_suite, phpunit_test_file, phpunit_test_nearest accept any CLI option accepted by PHPUnit, for example:

// Key Binding to run two specific test suites
{"keys": ["ctrl+shift+a"], "command": "test_suite", "args": {"testsuite": "fizz,buzz"}},

// Key Binding to run test suite with code coverage
{"keys": ["ctrl+shift+c"], "command": "test_suite", "args": {"coverage-html": "build/coverage"}},

Contributing

See CONTRIBUTING.md.

Changelog

See CHANGELOG.md.

Credits

Based initially on, and inspired by, maltize/sublime-text-2-ruby-tests, stuartherbert/sublime-phpunit, and janko-m/vim-test.

License

Released under the BSD 3-Clause License.