[Bamboo Cloud docs]
[Bamboo Knowledge Base]
This page describes how to configure a PHPUnit task.
Before you begin:
To configure a PHPUnit task:
Update the task settings:
|Task Description||Enter a description of the task, for display in Bamboo.|
|Disable this task||Check, or clear, to selectively run this task.|
|Executable||Select the PHPUnit executable that you wish to configure for this task (e.g. "PHPUnit 3.3.x" or "PHPUnit"). The executable that you select will become one of the task's capability requirements (and hence, one of the job's requirements). For details, please see Configuring a job's requirements .|
|Arguments||Type the name of the directory/files that will be analysed recursively by PHPUnit. The default value is "." (i.e. the working subdirectory, if specified). You must specify at least one argument.|
|Environment Variables||(Optional) Additional system environment variables that you want to pass to your build. Note that existing environment variables are automatically available to the executable. You can also include Bamboo global or build-specific variables (see Using global, plan or build-specific variables).|
Multiple variables should be separated with spaces. Parameters with spaces must be quoted (e.g ANT_OPTS="-Xms200m -Xmx700m").
|Working Sub Directory||(Optional) An alternative subdirectory, relative to the job's root directory, where Bamboo will run the executable. The root directory contains everything checked out from the job's configured source repository. If you leave this field blank, Bamboo will look for build files in the root directory. This option is useful if your task has a build script in a subdirectory and the executable needs to be run from within that subdirectory.|
|Log test execution to XML file||Select if you want PHPUnit to record test results in JUnit format. This format is also used by TestNG. |
Test Result File — the relative location, and name, of the file to record PHPUnit test results.
|Generate code coverage report in HTML format||Select if you want PHPUnit to generate code coverage data in HTML format (e.g. for PHPUnit HTML Code Coverage reports). |
HTML Code Coverage Directory — the relative location of the directory to store the code coverage report.