I have following, very simple, XML config for PHPUnit:
Along with the solutions above you could use more architecture-driven testing workflow where you manage your tests, directories and testsuites from phpunit.xml
like this:
tests/Unit
, tests/Feature
);All
testsuite that combines all default tests you would run as a full test suite and assign it via defaultTestSuite="All"
key within Tinker
test suite with tests that you could use for tinkering, keeping example tests etc. you would exclude from normal testing workflow. Do not inlcude it in the All
test suite.So you will be able to:
phpunit
CLI command to always run the default All
tests.phpunit --testsuite SuiteOne
, phpunit --filter SomeTest
or phpunit --filter SomeTest::test_some_test_method
--testsuite
with --filter
argumentsCouple this workflow with the capability to run the current test or test file from within your IDE (for Sublime Text there are Mac and Linux/Windows plugins) and you will be completelly equipped to instantly chose what test to execute.