Continuous integration/Entry points

Testing JavaScript
We are using  as an entry point. So if your project has JavaScript files, it should have a package.json file with at least a  definition.

Example:

If your project needs more complex building processes, the convention is to use Grunt as task runner. For example:

Good example:
 * jquery-client: package.json (no Grunt needed)
 * CSSJanus: package.json / Gruntfile.js (jshint, jscs, custom test)
 * TemplateData: package.json / Gruntfile.js (jshint, jscs, banana for mediawiki i18n)

Testing PHP
We are using  as an entry point. So if your project has PHP files it should list the test framework packages it needs in  under "require-dev" and list the commands to be run in the   property:

See for a good example.

Note that MediaWiki extensions are not standalone projects and cannot run their own test suite from composer, those repositories have a separate  job.

When running the suite under Jenkins, we might want to capture the test results to publish them on the build page. Since your test entry point has multiple commands, the extra arguments are set by Jenkins and should be included in each script command. By convention, the environment variable holding these arguments is all upper case, with the command line name suffixed with :

The Jenkins job can then set these environment variables to inject additional arguments when invoking  for e.g. Checkstyle or JUnit report.

Testing Python
See Continuous integration/Tutorials/Test your python.

Ruby
Use bundler to define your commands.