Tests are grouped into "suites". They are just directories. Suites can have
subdirectories if you want to group them even more. Running a suite will run
all sub-suites.
quick - The most common. Put your test here by default.
slow - Slower full featured tests. Grouped into sub-suites.
zend/good - Passing tests from Zend's suite.
zend/bad - Failing tests from Zend. Fix these and move them to zend/good.
vm-perf - Some performance tests that aren't commonly run.
Examples how to run them
Quick suite with the JIT on -
test/run test/quick
Zend tests just with the interpreter in RepoAuthoritative mode -
test/run test/zend/good -m interp -r
Slow tests with the JIT in IR mode -
test/run test/slow -m hhir
Run evertyhing that is supposed to pass -
fbmake runtests
File Layout
The format is the same as Zend's .phpt but instead of sections it is
separate files with the section name converted to an extension. This allows
you to easily run the .php file without first running the test suite.
These are the allowed extensions:
.php - The source of the test.
.expect - The exact string expected output.
.expectf - The exact string expected output with formating characters.
.expectregex - A regex that matches the output.
.out - When you run the test, the output will be stored here.
.opts - Runtime options to pass to hhvm.
.diff - The diff for .expect tests.
.hhas - HipHop Assembly.
You must have one .php; one and only one of .expect, .expectf, and
.expectregex; and the rest are optional.
Any suite can have a config.hdf file in it that will be used. If one isn't
present, then the parent suite it checked recusrivly until we use
test/config.hdf.
Name your test in a descriptive manner and when in doubt break your test into
many files. You can use comments too so future engineers know if it is a real
breakage or they need to change the expected output.
Edwin Smith