PHPT - Test File Layout.

Below is a reference manual for PHPT test file layouts.

Section Summary List.

[] indicates optional sections.

--TEST--
[--DESCRIPTION--]
[--CREDITS--]
[--SKIPIF--]
[--REQUEST--]
[--POST-- | --PUT-- | --POST_RAW-- | --GZIP_POST-- | --DEFLATE_POST-- | --GET--]
[--COOKIE--]
[--STDIN--]
[--INI--]
[--ARGS--]
[--ENV--]
--FILE-- | --FILEEOF-- | --FILE_EXTERNAL-- | --REDIRECTTEST--
[--HEADERS--]
[--CGI--]
[--XFAIL--]
[--EXPECTHEADERS--]
--EXPECT-- | --EXPECTF-- | --EXPECTREGEX--
[--CLEAN--]

--TEST--

Description:
Title of test as a single line short description.

Required:
Yes

Test Script Support:
run-tests.php, server-tests.php

Format:
Plain text. We recommend a single line only.

Example 1 (snippet):

--TEST--
Test filter_input() with GET and POST data.

Example 1 (full): sample001.phpt

--DESCRIPTION--

Description:
If your test requires more than a single line title to adequately describe it, you can use this section for further explanation. Multiple lines are allowed and besides being used for information, this section is completely ignored by the test binary.

Required:
No

Test Script Support:
run-tests.php, server-tests.php

Format:
Plain text, multiple lines.

Example 1 (snippet):

--DESCRIPTION--
This test covers both valid and invalid usages of
filter_input() with INPUT_GET and INPUT_POST data
and several differnet filter sanitizers.

Example 1 (full): sample001.phpt

--CREDITS--

Description:
If you don't have CVS commit rights, put your name and email on the first line. If the test is part of a TesFest event, then # followed by the name of the event and the date (YYYY-MM-DD) on the second line.

Required:
It's required for credit during TestFests.

Test Script Support:
run-tests.php, server-tests.php

Format:
Name Email
[Event]

Example 1 (snippet):

--CREDIT--
Felipe Pena 

Example 1 (full): sample001.phpt

Example 2 (snippet):

--CREDITS--
Zoe Slattery zoe@php.net
# TestFest Munich 2009-05-19

Example 2 (full): sample002.phpt

--SKIPIF--

Description:
A condition or set of conditions used to determine if a test should be skipped. Tests that are only applicable to a certain platform, extension or PHP version are good reasons for using a --SKIPIF-- section.

A common practice for extension tests is to write your --SKIPIF-- extension criteria into a file call skipif.inc and then including that file in the --SKIPIF-- section of all your extension tests. This promotes the DRY principle and reduces future code maintenance.

Required:
No.

Test Script Support:
run-tests.php, server-tests.php

Format:
PHP code enclosed by PHP tags.

Example 1 (snippet):

--SKIPIF--
<?php if (!extension_loaded("filter")) die("Skipped: filter extension required."); ?>

Example 1 (full): sample001.phpt

Example 2 (snippet):

--SKIPIF--
<?php include('skipif.inc'); ?>

Example 2 (full): sample003.phpt

--REQUEST--

Description:
Settings used for building the URL in an HTTP request. Currently only available with server-tests.php.

Required:
No.

Test Script Support:
server-tests.php

Format:
PHP source which is run through eval() and then split into key value pairs, one pair per line. Do not use <?php and ?> wrapper tags.

Valid settings for this section include:

• SCRIPT_NAME - The inital part of the request url
• PATH_INFO - The pathinfo part of a request url
• FRAGMENT - The fragment section of a url (after #)
• QUERY_STRING - The query part of a url (after ?)

Example 1 (snippet):

--REQUEST--
return <<<END
SCRIPT_NAME=/nothing.php
QUERY_STRING=$filename
END;

Example 1 (full): sample004.phpt

--POST--

Description:
POST variables or data to be passed to the test script. This section forces the use of the CGI binary instead of the usual CLI one.

Required:
No.

Requirements:
PHP CGI binary.

Test Script Support:
run-tests.php, server-tests.php

Format:
Follows the HTTP post data format.

Example 1 (snippet):

--POST--
c=<p>string</p>&d=12345.7

Example 1 (full): sample001.phpt

Example 2 (snippet):

--POST--
<SOAP-ENV:Envelope
  SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
  xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:si="http://soapinterop.org/xsd">
  <SOAP-ENV:Body>
    <ns1:test xmlns:ns1="http://testuri.org" />
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Example 2 (full): sample005.phpt

--POST_RAW--

Description:
Raw POST data to be passed to the test script. This differs from the section above because it doesn't automatically set the Content-Type, this leaves you free to define your own within the section. This section forces the use of the CGI binary instead of the usual CLI one.

Required:
No.

Requirements:
PHP CGI binary.

Test Script Support:
run-tests.php

Format:
Follows the HTTP post data format.

Example 1 (snippet):

--POST_RAW--
Content-type: multipart/form-data, boundary=AaB03x

--AaB03x
content-disposition: form-data; name="field1"

Joe Blow
--AaB03x
content-disposition: form-data; name="pics"; filename="file1.txt"
Content-Type: text/plain

abcdef123456789
--AaB03x--

Example 1 (full): sample006.phpt

--PUT--

Description:
Similar to the section above, PUT data to be passed to the test script. This section forces the use of the CGI binary instead of the usual CLI one.

Required:
No.

Requirements:
PHP CGI binary.

Test Script Support:
run-tests.php

Format:
Raw data optionally preceeded by a Content-Type header.

Example 1 (snippet):

--PUT--
Content-Type: text/json

{"name":"default output handler","type":0,"flags":112,"level":0,"chunk_size":0,"buffer_size":16384,"buffer_used":3}

--GZIP_POST--

Description:
When this section exists, the POST data will be gzencode()'d. This section forces the use of the CGI binary instead of the usual CLI one.

Required:
No.

Test Script Support:
run-tests.php

Format:
Just add the content to be gzencode()'d in the section.

Example 1 (snippet):

--GZIP_POST--
<SOAP-ENV:Envelope
  SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
  xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:si="http://soapinterop.org/xsd">
  <SOAP-ENV:Body>
    <ns1:test xmlns:ns1="http://testuri.org" />
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Example 1 (full): sample005.phpt

--DEFLATE_POST--

Description:
When this section exists, the POST data will be gzcompress()'ed. This section forces the use of the CGI binary instead of the usual CLI one.

Required:
No.

Requirements:

Test Script Support:
run-tests.php

Format:
Just add the content to be gzcompress()'ed in the section.

Example 1 (snippet):

--DEFLATE_POST--
<?xml version="1.0" encoding="ISO-8859-1"?>
<SOAP-ENV:Envelope
  SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
  xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:si="http://soapinterop.org/xsd">
  <SOAP-ENV:Body>
    <ns1:test xmlns:ns1="http://testuri.org" />
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Example 1 (full): sample007.phpt

--GET--

Description:
GET variables to be passed to the test script. This section forces the use of the CGI binary instead of the usual CLI one.

Required:
No.

Requirements:
PHP CGI binary.

Test Script Support:
run-tests.php, server-tests.php

Format:
A single line of text passed as the GET data to the script.

Example 1 (snippet):

--GET--
a=<b>test</b>&b=http://example.com

Example 1 (full): sample001.phpt

Example 2 (snippet):

--GET--
ar[elm1]=1234&ar[elm2]=0660&a=0234

Example 2 (full): sample008.phpt

--COOKIE--

Description:
Cookies to be passed to the test script. This section forces the use of the CGI binary instead of the usual CLI one.

Required:
No.

Requirements:
PHP CGI binary.

Test Script Support:
run-tests.php

Format:
A single line of text in a valid HTTP cookie format.

Example 1 (snippet):

--COOKIE--
hello=World;goodbye=MrChips

Example 1 (full): sample002.phpt

--STDIN--

Description:
Data to be fed to the test script's standard input.

Required:
No.

Test Script Support:
run-tests.php

Format:
Any text within this section is passed as STDIN to PHP.

Example 1 (snippet):

--STDIN--
fooBar
use this to input some thing to the php script

Example 1 (full): sample009.phpt

--INI--

Description:
To be used if you need a specific php.ini setting for the test.

Required:
No.

Test Script Support:
run-tests.php, server-tests.php

Format:
Key value pairs. One setting per line. Content that is not a valid ini setting may cause failures.

Example 1 (snippet):

--INI--
precision=14

Example 1 (full): sample001.phpt

Example 2 (snippet):

--INI--
session.use_cookies=0
session.cache_limiter=
register_globals=1
session.serialize_handler=php
session.save_handler=files

Example 2 (full): sample003.phpt

--ARGS--

Description:
A single line defining the arguments passed to php.

Required:
No.

Test Script Support:
run-tests.php, server-tests.php

Format:
A single line of text that is passed as the argument(s) to the PHP CLI.

Example 1 (snippet):

--ARGS--
--arg value --arg=value -avalue -a=value -a value

Example 1 (full): sample010.phpt

--ENV--

Description:
Configures environment variables such as those found in the $_SERVER global array.

Required:
No.

Test Script Support:
run-tests.php, server-tests.php

Format:
PHP source which is run through eval() and then split into key value pairs, one pair per line. Do not use <?php and ?> tags.

Some variables are made easily available for use in this section, they include:

• $filename - full native path to file, will become PATH_TRANSLATED
• $filepath - =dirname($filename)
• $scriptname - this is what will become SCRIPT_NAME unless you override it
• $docroot - the equivelant of DOCUMENT_ROOT under Apache
• $cwd - the directory that the test is being initiated from
• $this->conf - all server-tests configuration vars
• $this->env - all environment variables that will get passed to the test

Example 1 (snippet):

--ENV--
return <<<END
REDIRECT_URL=$scriptname
PATH_TRANSLATED=c:\apache\1.3.27\htdocs\nothing.php
QUERY_STRING=$filename
PATH_INFO=/nothing.php
SCRIPT_NAME=/phpexe/php.exe/nothing.php
SCRIPT_FILENAME=c:\apache\1.3.27\htdocs\nothing.php
END;

Example 1 (full): sample004.phpt

--FILE--

Description:
The test source code.

Required:
One of the FILE type sections is required.

Test Script Support:
run-tests.php, server-tests.php

Format:
PHP source code enclosed by PHP tags.

Example 1 (snippet):

--FILE--
<?php
ini_set('html_errors', false);
var_dump(filter_input(INPUT_GET, "a", FILTER_SANITIZE_STRIPPED));
var_dump(filter_input(INPUT_GET, "b", FILTER_SANITIZE_URL));
var_dump(filter_input(INPUT_GET, "a", FILTER_SANITIZE_SPECIAL_CHARS, array(1,2,3,4,5)));
var_dump(filter_input(INPUT_GET, "b", FILTER_VALIDATE_FLOAT, new stdClass));
var_dump(filter_input(INPUT_POST, "c", FILTER_SANITIZE_STRIPPED, array(5,6,7,8)));
var_dump(filter_input(INPUT_POST, "d", FILTER_VALIDATE_FLOAT));
var_dump(filter_input(INPUT_POST, "c", FILTER_SANITIZE_SPECIAL_CHARS));
var_dump(filter_input(INPUT_POST, "d", FILTER_VALIDATE_INT));
var_dump(filter_var(new stdClass, "d"));
var_dump(filter_input(INPUT_POST, "c", "", ""));
var_dump(filter_var("", "", "", "", ""));
var_dump(filter_var(0, 0, 0, 0, 0));
echo "Done\n";
?>

Example 1 (full): sample001.phpt

--FILEEOF--

Description:
An alternative to --FILE-- where any trailing line breaks (\n || \r || \r\n found at the end of the section) are omitted. This is an extreme edge-case feature, so 99.99% of the time you won't need this section.

Required:
One of the FILE type sections is required.

Test Script Support:
run-tests.php

Format:
PHP source code enclosed by PHP tags.

Example 1 (snippet):

--FILEEOF--
<?php
eval("echo 'Hello'; // comment");
echo " World";
//last line comment

Example 1 (full): sample011.phpt

--FILE_EXTERNAL--

Description:
An alternative to --FILE--. This is used to specify that an external file should be used as the --FILE-- contents of the test file, and is designed for running the same test file with different ini, environment, post/get or other external inputs. Basically it allows you to DRY up some of your tests. The file must be in the same directory as the test file, or in a subdirectory.

Required:
One of the FILE type sections is required.

Test Script Support:
run-tests.php

Format:
path/to/file. Single line.

Example 1 (snippet):

--FILE_EXTERNAL--
files/file012.php

Example 1 (full): sample012.phpt

--REDIRECTTEST--

Description:
This block allows you to redirect from one test to a bunch of other tests. It also allows you to set configurations which are used on all tests in your destination.

Required:
One of the FILE type sections is required.

Test Script Support:
run-tests.php

Format:
PHP source which is run through eval(). The tests destination is the value of an array index 'TESTS'. Also, keep in mind, you can not use a REDIRECTTEST which is being pointed to by another test which contains a REDIRECTTEST. In other words, no nesting.

The relative path declared in 'TESTS' is relative to the base directory for the PHP source code, not relative to the current directory.

Last note, the array in this section must be returned to work.

Example 1 (snippet):

--REDIRECTTEST--
return array(
  'ENV' => array(
      'PDOTEST_DSN' => 'sqlite2::memory:'
    ),
  'TESTS' => 'ext/pdo/tests'
  );

Example 1 (full): sample013.phpt
Note: The destination tests for this example are not included. See the PDO extension tests for reference to live tests using this section.

Example 2 (snippet):

--REDIRECTTEST--
# magic auto-configuration

$config = array(
  'TESTS' => 'ext/pdo/tests'
);

if (false !== getenv('PDO_MYSQL_TEST_DSN')) {
  # user set them from their shell
  $config['ENV']['PDOTEST_DSN'] = getenv('PDO_MYSQL_TEST_DSN');
  $config['ENV']['PDOTEST_USER'] = getenv('PDO_MYSQL_TEST_USER');
  $config['ENV']['PDOTEST_PASS'] = getenv('PDO_MYSQL_TEST_PASS');
  if (false !== getenv('PDO_MYSQL_TEST_ATTR')) {
    $config['ENV']['PDOTEST_ATTR'] = getenv('PDO_MYSQL_TEST_ATTR');
  }
} else {
  $config['ENV']['PDOTEST_DSN'] = 'mysql:host=localhost;dbname=test';
  $config['ENV']['PDOTEST_USER'] = 'root';
  $config['ENV']['PDOTEST_PASS'] = '';
}

return $config;

Example 2 (full): sample014.phpt
Note: The destination tests for this example are not included. See the PDO extension tests for reference to live tests using this section.

--HEADERS--

Description:
Header to be used when sending the request. Currently only available with server-tests.php.

Required:
No.

Test Script Support:
server-tests.php

Format:
PHP source which is run through eval() and then split into key value pairs. Do not use <?php and ?> wrapper tags.

Example 1 (snippet):

--HEADERS--
return <<<END
Content-Type=multipart/form-data; boundary=---------------------------240723202011929
Content-Length=862
END;

Example 1 (full): sample015.phpt

--CGI--

Description:
This section takes no value. It merely provides a simple marker for tests that MUST be run as CGI, even if there is no --POST-- or --GET-- sections in the test file. Currently only available with server-tests.php.

Required:
No.

Test Script Support:
server-tests.php

Format:
No value, just the --CGI-- statement.

Example 1 (snippet):

--CGI--

Example 1 (full): sample016.phpt

--XFAIL--

Description:
This section identifies this test as one that is currently expected to fail. It should include a brief description of why it's expected to fail. Reasons for such expectations include tests that are written before the functionality they are testing is implemented or notice of a bug which is due to upstream code such as an extension which provides PHP support for some other software.

Please do NOT include an --XFAIL-- without providing a text description for the reason it's being used.

Required:
No.

Test Script Support:
run-tests.php

Format:
A short plain text description of why this test is currently expected to fail.

Example 1 (snippet):

--XFAIL--
This bug might be still open on aix5.2-ppc64 and hpux11.23-ia64

Example 1 (full): sample017.phpt

--EXPECTHEADERS--

Description:
The expected headers. Any header specified here must exist in the response and have the same value or the test fails. Additional headers found in the actual tests while running are ignored.

Required:
No.

Test Script Support:
run-tests.php, server-tests.php

Format:
HTTP style headers. May include multiple lines.

Example 1 (snippet):

--EXPECTHEADERS--
Status: 404

Example 1 (full): sample004.phpt

Example 2 (snippet):

--EXPECTHEADERS--
Content-type: text/html; charset=UTF-8
Status: 403 Access Denied

Example 2 (full): sample018.phpt
Note: The destination tests for this example are not included. See the phar extension tests for reference to live tests using this section.

--EXPECT--

Description:
The expected output from the test script. This must match the actual output from the test script exactly for the test to pass.

Required:
One of the EXPECT type sections is required.

Test Script Support:
run-tests.php, server-tests.php

Format:
Plain text. Multiple lines of text are allowed.

Example 1 (snippet):

--EXPECT--
array(2) {
  ["hello"]=>
  string(5) "World"
  ["goodbye"]=>
  string(7) "MrChips"
}

Example 1 (full): sample002.phpt

--EXPECTF--

Description:
An alternative of --EXPECT--. Where it differs from --EXPECT-- is that it uses a number of substitution tags for strings, spaces, digits, etc. that appear in test case output but which may vary between test runs. The most common example of this is to use %s and %d to match the file path and line number which are output by PHP Warnings.

Required:
One of the EXPECT type sections is required.

Test Script Support:
run-tests.php, server-tests.php

Format:
Plain text including tags which are inserted to represent different types of output which are not guaranteed to have the same value on subsequent runs or when run on different platforms.

The following is a list of all tags and what they are used to represent:

• %e: Represents a directory separator, for example / on Linux.
• %s: One or more of anything (character or white space) except the end of line character.
• %S: Zero or more of anything (character or white space) except the end of line character.
• %a: One or more of anything (character or white space) including the end of line character.
• %A: Zero or more of anything (character or white space) including the end of line character.
• %w: Zero or more white space characters.
• %i: A signed integer value, for example +3142, -3142.
• %d: An unsigned integer value, for example 123456.
• %x: One or more hexadecimal character. That is, characters in the range 0-9, a-f, A-F.
• %f: A floating point number, for example: 3.142, -3.142, 3.142E-10, 3.142e+10.
• %c: A single character of any sort (.).
• %r...%r: Any string (...) enclosed between two %r will be treated as a regular expression.
• %unicode|string%: Matches the string 'unicode' in PHP6 test output and 'string' in PHP5 test output.
• %binary_string_optional%: Matches 'Binary string' in PHP6 output, 'string' in PHP5 output. Used in PHP Warning messages.
• %unicode_string_optional%: Matches 'Unicode string' in PHP6 output, 'string' in PHP5 output. Used in PHP Warning messages.
• %u|b%: Matches a single 'u' in PHP6 test output where the PHP5 output from the same test hs no character in that position.

Example 1 (snippet):

--EXPECTF--
string(4) "test"
string(18) "http://example.com"
string(27) "<b>test</b>"

Notice: Object of class stdClass could not be converted to int in %ssample001.php on line %d
bool(false)
string(6) "string"
float(12345.7)
string(29) "<p>string</p>"
bool(false)

Warning: filter_var() expects parameter 2 to be long, string given in %s011.php on line %d
NULL

Warning: filter_input() expects parameter 3 to be long, string given in %s011.php on line %d
NULL

Warning: filter_var() expects at most 3 parameters, 5 given in %s011.php on line %d
NULL

Warning: filter_var() expects at most 3 parameters, 5 given in %s011.php on line %d
NULL
Done

Example 1 (full): sample001.phpt

Example 2 (snippet):

--EXPECTF--
Warning: bzopen() expects exactly 2 parameters, 0 given in %s on line %d
NULL

Warning: bzopen(): '' is not a valid mode for bzopen(). Only 'w' and 'r' are supported. in %s on line %d
bool(false)

Warning: bzopen(): filename cannot be empty in %s on line %d
bool(false)

Warning: bzopen(): filename cannot be empty in %s on line %d
bool(false)

Warning: bzopen(): 'x' is not a valid mode for bzopen(). Only 'w' and 'r' are supported. in %s on line %d
bool(false)

Warning: bzopen(): 'rw' is not a valid mode for bzopen(). Only 'w' and 'r' are supported. in %s on line %d
bool(false)

Warning: bzopen(no_such_file): failed to open stream: No such file or directory in %s on line %d
bool(false)
resource(%d) of type (stream)
Done

Example 2 (full): sample019.phpt

Example 3 (snippet):

--EXPECTF--
object(DOMNodeList)#%d (0) {
}
int(0)
bool(true)
bool(true)
string(0) ""
bool(true)
bool(true)
bool(false)
bool(false)

Example 2 (full): sample020.phpt

--EXPECTREGEX--

Description:
An alternative of --EXPECT--. This form allows the tester to specify the result in a regular expression.

Required:
One of the EXPECT type sections is required.

Test Script Support:
run-tests.php, server-tests.php

Format:
Plain text including regular expression patterns which represent data that can vary between subsequent runs of a test or when run on different platforms.

Example 1 (snippet):

--EXPECTREGEX--
M_E       : 2.718281[0-9]*
M_LOG2E   : 1.442695[0-9]*
M_LOG10E  : 0.434294[0-9]*
M_LN2     : 0.693147[0-9]*
M_LN10    : 2.302585[0-9]*
M_PI      : 3.141592[0-9]*
M_PI_2    : 1.570796[0-9]*
M_PI_4    : 0.785398[0-9]*
M_1_PI    : 0.318309[0-9]*
M_2_PI    : 0.636619[0-9]*
M_SQRTPI  : 1.772453[0-9]*
M_2_SQRTPI: 1.128379[0-9]*
M_LNPI    : 1.144729[0-9]*
M_EULER   : 0.577215[0-9]*
M_SQRT2   : 1.414213[0-9]*
M_SQRT1_2 : 0.707106[0-9]*
M_SQRT3   : 1.732050[0-9]*

Example 1 (full): sample021.phpt

Example 2 (snippet):

--EXPECTF--
*** Testing imap_append() : basic functionality ***
Create a new mailbox for test
Create a temporary mailbox and add 0 msgs
.. mailbox '%s' created
Add a couple of msgs to new mailbox {%s}INBOX.%s
bool(true)
bool(true)
Msg Count after append : 2
List the msg headers
array(2) {
  [0]=>
  string(%d) "%w%s       1)%s webmaster@something. Test message (%d chars)"
  [1]=>
  string(%d) "%w%s       2)%s webmaster@something. Another test (%d chars)"
}

Example 2 (full): sample025.phpt

Example 3 (snippet):

--EXPECTREGEX--
string\(4\) \"-012\"
string\(8\) \"2d303132\"
(string\(13\) \"   4294967284\"|string\(20\) \"18446744073709551604\")
(string\(26\) \"20202034323934393637323834\"|string\(40\) \"3138343436373434303733373039353531363034\")

Example 3 (full): sample023.phpt

--CLEAN--

Description:
Code that is executed after a test completes. It's main purpose is to allow you to clean up after yourself. You might need to remove files created during the test or close sockets or database connections following a test. Infact, even if a test fails or encounters a fatal error during the test, the code found in the --CLEAN-- section will still run.

Code in the clean section is run in a completely different process than the one the test was run in. So do not try accessing variables you created in the --FILE-- section from inside the --CLEAN-- section, they won't exist.

Using the switch --no-clean on run-tests.php, you can prevent the code found in the --CLEAN-- section of a test from running. This allows you to inspect generated data or files without them being removed by the --CLEAN-- section.

Required:
No.

Test Script Support:
run-tests.php

Format:
PHP source code enclosed by PHP tags.

Example 1 (snippet):

--CLEAN--
<?php
  $temp_filename = dirname(__FILE__)."/DomDocument_save_basic.tmp";
  unlink($temp_filename);
?>

Example 1 (full): sample024.phpt

Example 2 (snippet):

--CLEAN--
<?php 
require_once('clean.inc');
?>

Example 2 (full): sample025.phpt

Example 3 (snippet):

--CLEAN--
<?php
$key = ftok(dirname(__FILE__)."/003.phpt", 'q');
$s = shm_attach($key);
shm_remove($s);
?>

Example 3 (full): sample022.phpt