PHP Wiki

testfest-2010

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 1:		Line 1:
		+	====== PHP TestFest 2010 ======
		+
		+	//This page contains out-dated material and is archived here for informational purposes. For recent information, see the [[qa:testfest\| main PHP TestFest page]].//
		+
	===== What is TestFest? =====		===== What is TestFest? =====

testfest-2009

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/09/01 07:55	current
Line 1:	Line 1:
	+	====== PHP TestFest 2009 ======

	+	//This page contains out-dated material and is archived here for informational purposes. For recent information, see the [[qa:testfest\| main PHP TestFest page]].//
	+
	+	===== How do I join? How do I get more information? =====
	+
	+	See the [[http://qa.php.net/testfest.php\|TestFest]] homepage on the QA team website for details. Alternatively you can join #php.pecl on Efnet or the #phptestfest channel on Freenode IRC server. There should usually be someone around to help.
	+	Follow twitter [[http://twitter.com/phptestfest\|testfest]]
	+
	+	==== Summary of registered groups ====
	+
	+	^ Group name ^ Date ^ Ext to test ^ mentor ^ Organiser email ^
	+	\| Belgium \| May 9 \| SQlite3, ldap \| Felix de Vleigher \| felixdv@php.net \|
	+	\| Brazil (SP ) \| June 20 \| \| \| rdohms@gmail.com \|
	+	\| Brazil (Rio) \| July 3 \| \| Igor Feghali \| ifeghali@php.net \|
	+	\| Brazil(BR) \| June 23 \| \| Er Galvao Abbott \| galvao@galvao.eti.br \|
	+	\| Brazil(SC) \| \| \| \| silvano@php.net \|
	+	\| Brazil(CEPUG) \| \| \| \| brunoviana@gmail.com \|
	+	\| Catalonia \| June 13 \| \| Hannes Magnusson \| alex@corretge.cat \|
	+	\| Canada (Montreal) \| May 1/2/3 \| Date, time \| Derick Rethans \| afilina@phpquebec.org \|
	+	\| Colombia \| \| \| \| andphe@gmail.com \|
	+	\| France \| May 9 \| CURL \| \| perrick@noparking.net \|
	+	\| Germany (Munich) \| April 16/17 \| \| Pierre Joye \| Pierre Joye \|
	+	\| Germany (Berlin) \| May 9/10 \| gettext, sockets, soap, xsl, posix \| \| till@php.net \|
	+	\| Germany (Wurzburg)\| May 30/31 \| \| \| info@fruityweb.de \|
	+	\| Ireland \| \| \| \| davic@php.ie \|
	+	\| Italy \| June 20/20/21 \| \| \| francesco@cphp.it \|
	+	\| Netherlands \| May 9 \| CURL \| \| stefan@phpgg.nl \|
	+	\| Norway \| June 9 \| \| Hannes Magnusson \| russ@redpill-linpro.com\|
	+	\| Peru \| April 4 \| \| \| info.latino@dokeos.com \|
	+	\| USA (tek) \| May 21 \| \| \| stefan@phpgg.nl \|
	+	\| USA (NYPHP) \| May 23 \| XmlReader/XMLWriter/DOM \| Elizabeth Smith \| Hans Zaunere \|
	+	\| USA (Atlanta) \| \| DOM \| \| Ben Ramsey \|
	+	\| USA (Nashville) \| \| \| \| Will Fitch \|
	+	\| UK (London) \| May 9 \| SPL \| Zoe Slattery \| matt.raines@phplondon.org \|
	+	\| UK (NorthWest) \| May 9 \| SPL \| Scott MacVicar \| lorna@lornajane.net \|
	+	\| NZ (Christchurch) \| June 20 \| \| \| lukemoynihan@gmail.com \|
	+
	+	==== Results ====
	+	See
	+	* http://results.testfest.php.net/displayresults.php (32 bit)
	+	* http://testfest.php.net/displayresults.php (64 bit)
	+
	+
	+	===== Registered UGs =====
	+
	+	==== Belgium ====
	+
	+
	+	* Belgian PHP Usergroup, http://www.phpbelgium.be.
	+	* Contact: Felix De Vliegher, <felixdv@php.net>
	+	* Date: Saturday May 9th 9am-6pm
	+	* Location: Combell offices, Skaldenstraat 121, 9042 Gent, Belgium [[http://maps.google.com/maps?f=q&source=s_q&hl=nl&geocode=&q=Skaldenstraat+121+Gent+9042&sll=37.0625,-95.677068&sspn=34.534108,93.076172&ie=UTF8&ll=51.113707,3.788931&spn=0.006681,0.022724&z=16&iwloc=A \| Google maps]]
	+	* Subscribe/RSVP here: http://tr.im/jpSY
	+	* Extension to test: SQLite3, Ldap
	+
	+	==== Brazil ====
	+
	+	* PHPSP (http://www.phpsp.org.br) Contact Names: Augusto Pascutti & Rafael Dohms <admin@phpsp.org.br> - May
	+	* PHP Rio (http://www.phprio.org) Contact Name: Igor Feghali <ifeghali@php.net>
	+	* PHPBR (http://www.phpbr.com.br) Contact Name: Er Galvão Abbott <galvao@phpbr.com.br>
	+	* PHPSC (http://www.phpsc.com.br) Contact Name: Silvano Girardi Jr. <silvano@php.net>
	+	* CEPUG (http://www.cepug.org) Contact Name: Bruno Viana <brunoviana@gmail.com>
	+
	+	==== Catalonia ====
	+
	+	* CCCPHP, http://cccphp.net. Saturday 13th of june at [[http://ca.wikipedia.org/wiki/Verges\|Verges]] (Baix Empordà). [[http://cccphp.googlecode.com/svn/trunk/org.TestFest2009/cartell%20PHP%20TestFest%202009.pdf\|Agenda]]. [[http://www.facebook.com/home.php#/event.php?eid=75135753753&ref=ts\|Facebook]]. Return of Service to Open Source. Contact name: Àlex Corretgé, <alex@corretge.cat>
	+
	+	==== Canada ====
	+
	+	=== Montreal ===
	+
	+	* Organized by PHP Quebec [[http://phpquebec.org]]
	+	* Contact: Anna Filina <afilina@phpquebec.org>
	+	* Dates
	+	* Friday May 1st 7pm-10pm (social/casual/unofficial warm-up)
	+	* Saturday May 2nd 9am-6pm (TestFest/CodeFest)
	+	* Sunday May 3rd 9am-6pm (TestFest/CodeFest)
	+	* Location: Helm - 273 Bernard W.
	+	* More info about the event: [[http://codefest.ws]]
	+
	+	==== Colombia ====
	+
	+	* Organized by Colombia PHP [[http://groups.google.com/group/php-colombia]] [[http://www.colombiaphp.net]]
	+	* Contact: Andrés Felipe Vargas <andphe@gmail.com>
	+	* Date: to define
	+	* Location: irc #php-co at freenode.net
	+
	+	==== France ====
	+
	+	=== Paris ===
	+
	+	* Organized by AFUP[[http://afup.org]]
	+	* Contact: Perrick Penet <perrick@noparking.net>
	+	* Date: Saturday May 9th 10am-8pm (PhpCamp / TestFest)
	+	* Location: La Cantine - 151 rue Montmartre - Passage des Panoramas - 12 Galerie Montmartre - 75002 Paris
	+	* More info about the event: [[http://afup.org/pages/rendezvous/?id=6]]
	+	* Extension to test: CURL
	+
	+
	+	==== Germany ====
	+
	+	=== Munich ===
	+	* PLEASE RSVP:
	+	* Contact Pierre, email:pierre@php.net
	+	* or come online on Freenode #phptestfest
	+
	+	* Prepare Slides
	+	* How PHP Works
	+	* [[http://wiki.php.net/qa/testfesttalk\|How to write PHPT]]
	+	* 16th Evening Meeting will stand at [[http://www.nockherberg.com/\|Nockhenberg Biergarten]]
	+	* 18.30 Welcome
	+	* 19.00 Talks
	+	* PHP 5.3 - Sebastian Bergmann
	+	* QA and PHP, Sebastian Schürmann
	+	* Food&Drinks
	+	* 17th TestFest Day
	+	* Location: [[http://www.microsoft.com/germany/unternehmen/informationen/gmbh_profil/niederlassungen/muenchen.mspx\|Microsoft EMEA Office in Unterschleißheim]]
	+	* 09:30 welcome, 09:45 presentation (until ~11:30)
	+	* Introductions and presentations of the test infrastructure for PHP
	+	* Write a bunch of tests :)
	+
	+
	+
	+	=== Berlin ===
	+
	+	* Contact Till, email:till@php.net
	+
	+	* Chosen date: May 9th/10th (weekend)
	+
	+	* Location: [[http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Boxhagener+Stra%C3%9Fe+119,+10245+Friedrichshain,+Berlin&sll=52.50743,13.467888&sspn=0.010239,0.019312&ie=UTF8&ll=52.512447,13.461277&spn=0.010238,0.019312&t=h&z=16&iwloc=addr\|Boxhagener Str. 119, Berlin]]
	+
	+	* PLEASE RSVP: [[http://wiki.upstream-berlin.com/index.php/PHPTestFest2009]]
	+
	+	* Extensions: gettext, sockets, soap, xsl, posix
	+
	+	* Blog entries about the testfest:
	+	* http://cweiske.de/tagebuch/PHP%20Testfest%20Berlin%202009.htm
	+	* http://till.klampaeckel.de/blog/archives/34-Great-success!.html
	+
	+	=== Würzburg ===
	+	* The PHP user group Wuerzburg decided to start a test fest from 30 May to 31 May.
	+	* Contact - Steffen Hartmann <info@fruityweb.de>
	+
	+	* UG Website: [[http://www.phpug-wuerzburg.de/]]
	+
	+	==== Ireland ====
	+
	+	* Irish PHP User Group (http://php.ie). Contact Jaime Hemmett email: jaime@hemmett.org, David Coallier email: davidc@php.ie
	+
	+	==== Italy ====
	+
	+	=== Cesena ===
	+
	+	* Organized by [[http://www.grusp.it\|GrUSP]] and [[http://www.ideato.it\|ideato srl]]
	+	* Contact: Francesco Trucchia <francesco@cphp.it>
	+	* Dates
	+	* Friday June 19 10-17 (Code dojo TestFest)
	+	* Saturday June 20 10-17 (Pair CodeFest)
	+	* Sunday June 21 10-17 (Deploy TestFest)
	+	* Location: [[http://maps.google.it/maps?f=q&source=s_q&hl=it&geocode=&q=ideato&ie=UTF8&z=8&iwloc=A\|Ideato srl]] - via Quinto Bucci 205, 47023 Cesena (FC).
	+	* More info about the event: [[http://wiki.grusp.it/eventi:phptestfest:riviera2009]]
	+
	+	==== Netherlands ====
	+
	+	* Organized by [[http://phpgg.nl/\|Dutch PHP Usergroup]] with support of [[http://www.microsoft.nl/\|Microsoft]]
	+	* Contact: Stefan Koopmanschap <stefan@phpgg.nl>
	+	* Date and time: Saturday 9 May, 10:30 - 17:00
	+	* Location: Hogeschool Domstad, Utrecht
	+	* More info about the event: [[http://phpgg.nl/testfest2009\|TestFest 2009]]
	+	* Focus on extension: curl
	+
	+	==== Norway ====
	+
	+	===Oslo===
	+
	+	* Organized by [[http://php.no/\|Norway PHP Usergroup]] in association with [[http://redpill-linpro.com/\|Redpill Linpro]]
	+	* Contact: Russell Flynn <russ@redpill-linpro.com>
	+	* Date and time: Tuesday 9th June, 15:30 - 22:00
	+	* Location: Offices of [[http://redpill-linpro.com/\|Redpill Linpro]], Storo, Oslo
	+	* More info about the event: [[http://php.no/wiki/index.php?title=09.06.2009_-_TestFest\|TestFest 2009 Norway]]
	+
	+	==== Peru ====
	+	* Grupo PHP Perú, www.php.org.pe. Contact name: Yannick Warnier, email: info.latino@dokeos.com (Meeting 4/4/9) ([[http://dokeoslead.wordpress.com/2009/04/05/php-testfest-2009-first-try/ \| See report ]])
	+	==== USA ====
	+
	+	* php\|tek (http://tek.mtacon.com/c/s/hackathon) Contact names Stefan Koopmanschap email:stefan@phpgg.nl, Matthew Turland matthew@blueparabola.com
	+	* NYPHP (http://www.nyphp.org) Contact name: Hans Zaunere
	+	* Extensions to test: xmlreader/xmlwriter
	+	* Atlanta PHP (http://atlantaphp.org) Contact name: Ben Ramsey. Subject: DOM
	+	* Nashville PHP (http://www.nashvillephp.org) Contact name: Will Fitch
	+
	+	==== UK ====
	+
	+	* PHP NorthWest. Contact Lorna Jane Mitchell. email: lorna@lornajane.net
	+	* Date and Time: Saturday 9th May, 12 noon until 4pm
	+	* Location: Newton Building, School of Computing, Science and Engineering, Salford University
	+	* Extension to test: SPL
	+	* PHP London. Contact Matt Raines. email: matt.raines@phplondon.org
	+	* Planned date Saturday May 9th - 10:00 to 18:00.
	+	* Location IBM Southbank buildings
	+	* Extension to test: SPL
	+	* Sign up here: http://www.phplondon.org/wiki/May_9th_2009
	+
	+	==== NZ ====
	+
	+	* Web Design Meetup Christchurch. Contact Luke Moynihan. email lukemoynihan@gmail.com
	+	* Date and Time: Saturday 20th June, 10am until 5pm
	+	* Location: Media Suite, Ferrymead, 23 Humphreys Drive, Office 6 (above Kenso)
	+	* Please RSVP
	+
	+
	+	===== Individuals looking for local events =====
	+	This is a log of individual requests to groups participating in TestFest.
	+	* Looking for an event in Bulgaria (Sofia)
	+	===== Available Mentors =====
	+	^ Mentor Name ^ Area of expertise ^ User group to mentor ^ Dates unavailable on-line ^
	+	\| Hannes Magnusson \| Any extension is OK \| Catalonia and Norway \| \|
	+	\| Scott MacVicar \| \| PHPNW \| \|
	+	\| Mikko Koppanen \| \| \| \|
	+	\| Elizabeth Marie Smith \| Anything but XML ext \| In USA - Midwest - NEW YORK \| \|
	+	\| Derick Rethans \| \| \| \|
	+	\| Pierre A. Joye \| \| Munich (with dsop), NL \| \|
	+	\| Felix De Vliegher \| \| Belgium \| \|
	+	\| Igor Feghali \| \| Rio, SP and CEPUG (Brazil) \| \|
	+	\| Ant Phillips \| \| \| \|
	+	\| Zoe Slattery \| Anything core \| London \| 7th - 15th April (likely) \|
	+	\| Raghubansh Kumar \| Anything core, Coding Guidelines \| \| \|
	+	\| Nuno Lopes \| \| Lisbon and Germany \| \|
	+	\| Michael Maclean \| XML exts \| \| 11th to 18th April \|
	+	\| Till Klampaeckel \| \| Berlin, Germany \| \|
	+
	+
	+	===== To do list =====
	+	===== Materials for user groups: =====
	+	* iso images with PHP executable, PHP source, DOCS.
	+	* Linux. Owner:
	+	* Windows. Owner: Pierre
	+	* OSX. Owner:
	+	* A place to put the iso images so that people can download them. Owner:
	+	* VM images with full test environment.
	+	* Windows image. Owner: Pierre
	+	* OSX?
	+	* Linux VirtualBox VM (Ubuntu 32-bit for now): Eric Lee Stewart (http://www.ericstewart.org/tfvm/)
	+	* Unix VirtualBox VM (FreeBSD 32-bit for now): <del>Eric Lee Stewart</del>
	+
	+	===== Locations =====
	+	* Companies prepared to loan their offices on a Saturday?
	+	===== Other Resources =====
	+
	+	==== Internal ====
	+	* [[QA:PHPTLessonsLearned\|Lessons Learned in PHP Testing]]
	+	* [[QA:TestCoverage\|How to get test coverage (Linux)]]
	+	* [[QA:WhatToTest\|More information on what to test]]
	+	* [[QA:Credits\|Crediting test case authors]]
	+	* [[QA:Uploading\|Where to put tests]] (Testfest SVN)
	+	* [[QA:Organisers\|Suggestions & checklist for TestFest organisers]]
	+	* [[qa:testfesttalk\|A reusable talk for the 2009 testfest]]
	+	* [[qa:svnnote\|note for SVN admins]]
	+
	+	==== External ====
	+	* [[http://sebastian-bergmann.de/archives/776-Prepare-for-TestFest.html\|Attendees: how to prepare for TestFest]]
	+	* [[http://sebastian-bergmann.de/archives/777-PHP-Test-Fest-Slides.html\|Basics on phpt slides]]
	+	* [[http://cvs.php.net/viewvc.cgi/php-src/README.TESTING?revision=1.24&view=markup\|Information on run-test.php]]
	+	* [[http://felix.phpbelgium.be/blog/2008/05/22/writing-phpt-tests-on-your-mac/\|Writing phpt tests on Mac OS X]]

documentation

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/09/01 20:04		current
Line 114:		Line 114:
	Parent class for classes that set run configuration settings. See 'setting' directory for sub-classes. Note that run settings can be derived from eith command line options or Environment variables, the functions of teh settings classes is mainly to determine which of these has been used and to set the run configuration accordingly.		Parent class for classes that set run configuration settings. See 'setting' directory for sub-classes. Note that run settings can be derived from eith command line options or Environment variables, the functions of teh settings classes is mainly to determine which of these has been used and to set the run configuration accordingly.

		+	===== Test case classes =====
		+	====rtPhpTestFile====
		+	Reads the contents of a test file, checks that it's a valid test (see precondtions) and removes windows-style line endings.
		+	rtPhpTest
		+	The main test case class. Takes the contents of the file read by rtPhpTestFile and creates section objects for each section (see Test Case Sections). The run() method runs any executable sections and then compares teh test out put with the expected output.
		+
		+	====rtTestPreCondtion====
		+	There are a number of preconditions that must be met before a test can be run. This is the parent class for preconditions. Preconditions are checked as the test file is read (see section on test precondtions)
		+	====rtTestConfiguration ====
		+	The run configuration can be modified by test case sections. The test configuration class implements the modifications and is used by rtFileSection when running the test.
		+	====rtPhpRunner ====
		+	As the name suggests, this runs PHP code. It's an almost exact copy of the original run-tests code (system_with_timeout()). No reason to change something that works fine as it is.
		+	==== rtPhpTestResults ====
		+	Collates the results of running (or attempting to run) a test. If the test has failed ensures that the difference between the expected and actual output is calculated and saved. Decides which files to keep and which to delete. Keeps a record of any saved files and of teh overall status (pass, fail, skip etc) of the test.
		+
		+	==== rtTestDifference ====
		+	Exact copy of the differencing code in the original run-tests. This code is complex, it might be possible to do better but for now it seems best not to try and modify it.
		+
		+	==== rtOutputWriter ====
		+	Takes the list of test results and writes in the desired format. Is a parent class for various different formats out output class. Currently only the 'list' format is implemented.
		+
		+
		+
		+	====Test Section Classes ====
		+
		+	Each test is made up from a number of sections, for example,
		+	--TEST--
		+	a title
		+	--FILE--
		+	<?php
		+	some php code
		+	?>
		+	--EXPECT--
		+	the expected result of running the PHP code.
		+
		+	All sections have a name and some contents. Sometimes the contents just have information - for example the test title, sometimes the contents are executable, or used to compare against the output.
		+
		+	The base class for all sections is rtSection. This class has a method which initialises the contents to an array of strings.
		+
		+	There are four subclasses which extend rtSection, these are rtInformationSection, rtExecutableSection, rtoutputSection and rtConfigurationSection. Each of these are extended again by classes which represent specific sections. The class hierarchy is shown in the attached ODP charts.
		+
		+	A brief description of the responsibilities of each class is given below.
		+
		+	====Information Sections====
		+	===rtTestSection ===
		+	This class just contains the test case title.
		+
		+	===rtCreditsSection ===
		+	This class contains information about who wrote the test
		+
		+	===rtXfailSection===
		+	The presence of this section in the test indicates that the test is expected to fail. The contents contain information about the reason for an expected failure.
		+
		+	====Executable Sections====
		+
		+	===rtFileSection===
		+	This is the most complex of the sections. The contents represent the PHP code that needs to be run. The section is responsible for assembling the command line that will run the code. The format of the command line is:
		+
		+	php_executable php_arguments test.php test_arguments
		+
		+	Note that both php_arguments aand test_arguments can be modified by other test sections and are therefore supplied from a TestConfiguration object and not from the RunConfiguration.
		+	The executable code is supplied in a file called test.php, where 'test' is the name of the testcase. The file is constructed fron teh test case contents and written by this section.
		+	===rtSkipIfSection===
		+	Executes code to determine if the test should be run or not. For example:
		+	<?php
		+	if( substr(PHP_OS, 0, 3) == 'WIN') {
		+	die('skip Not for Windows');
		+	Note that the first word in the comment is always 'skip' or 'warn'. For example in ext/standard/tests/time/001.phpt:
		+
		+	<?php
		+	if (!function_exists('microtime'))
		+	die('skip microtime() not available');
		+	die('warn system dependent');
		+	?>
		+	Note: the warning is a pretty strange thing to do as part of a section called SKIPIF. I've implemented it here for compatibility but it would be better to have a separate WARN section
		+
		+
		+
		+	===rtCleanSection===
		+	This section runs code that should clean up after a test. Many people forget that this is a separate piece of executable code - therefore you can't define $myFile in the body of the test and expect to be able to unling $myFile in the CLEAN section. There are currently 71 tests that need to be fixed because the CLEAN sections are a mess.
		+
		+	The old run-tests code just chucks away any results from running a CLAEN section. In this code if the results of running the clean section are not an empty string then the results are printed out with a WARN flag.
		+	====OutputSections====
		+	These sections deal with the expected output of the test and compare it with the actual output.
		+	rtExpectSection
		+
		+	rtExpectFSection
		+
		+	rtExectRegexSection
		+
		+	====Configuration sections====
		+	These sections have additional configuration information that changes the way that a single test is run
		+	===rtArgsSection===
		+	This section contains command line arguments for the test case. For an example of the usage see
		+	ext/standard/tests/general_functions/getopt.phpt
		+
		+	Test test_arguments are appended after the testcase as a string preceeded by '--'
		+
		+	php_executable php_arguments test.php test_arguments
		+	===rtEnvSection===
		+	This section adds any environmental variables that are required by a single testcase. For an example of usage see:
		+	ext/standard/tests/general_functions/parse_ini_basic.phpt
		+	The environmental variables specified in the test case are appended to the array of environment variables which is constructed in the run configuration and set in teh testsConfiguration
		+	===rtIniSection===
		+	This section adds additional commanline arguments to the PHP command line:
		+	php_executable php_arguments test.php test_arguments
		+
		+	These are added in the form of -d flags and are appended to those already set in the runConfiguration

	====== Parallel Execution ======		====== Parallel Execution ======

testfesttalk

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 1:		Line 1:
	====== PHPT roundup talk ======		====== PHPT roundup talk ======
-	This wikipage contains all extra information for the talk prepared for phptestfest 2009. They heavily rely on content written by other people before. Every resource of the talk, even the slides (in different formats) will be in this place. Other testfesters can use and modify this talk to save precious time.	+	This wikipage contains all extra information for the talk prepared for [[qa:testfest-2009\|phptestfest 2009]]. They heavily rely on content written by other people before. Every resource of the talk, even the slides (in different formats) will be in this place. Other testfesters can use and modify this talk to save precious time.

	[[http://tinyurl.com/c9bqf4]]		[[http://tinyurl.com/c9bqf4]]

whattotest

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/05/07 13:05		current
Line 174:		Line 174:

	==== Script 3 ====		==== Script 3 ====
-	This script lists all the classes in PHP and then finds their methods using a ReflectionClass. Using essentially the same logic as the other two scripts teh code searches for tests that refer to these methods. The script is flawed in that many classes have methods of the same name (for example \_\_toString occurs in many classes), so looking for all tests that refer to \_\_toString will give a list of mainly irrelevant tests. Because of this I've excluded any method beginning "\_\_" from the search, even so, the results should be treated with care.	+	This script lists all the classes in PHP and then finds their methods using a ReflectionClass. Using essentially the same logic as the other two scripts teh code searches for tests that refer to these methods. The script is flawed in that many classes have methods of the same name (for example %%__toString%% occurs in many classes), so looking for all tests that refer to %%__toString%% will give a list of mainly irrelevant tests. Because of this I've excluded any method beginning "%%__%%" from the search, even so, the results should be treated with care.

	<code php>		<code php>

windows-test-environment

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2010/05/27 02:15		current
Line 12:		Line 12:
	===== Install the Latest Version of PHP 5.2 =====		===== Install the Latest Version of PHP 5.2 =====

-	* Visit the [[http://windows.php.net/download/\|PHP Windows Download]] page. Download the "Zip" file of the latest version of "VC9 x86 Non Thread Safe" for PHP 5.2. Do not download the "Installer" or "Debug Package". When downloading, save the file to a location you plan to use for your PHPT development and testing.	+	* Visit the [[http://windows.php.net/download/\|PHP Windows Download]] page. Download the "Zip" file of the latest version of "VC6 x86 Non Thread Safe" for PHP 5.2. Do not download the "Installer" or "Debug Package". When downloading, save the file to a location you plan to use for your PHPT development and testing.
	* Unzip the file you downloaded. Rename the unzipped folder to "php52".		* Unzip the file you downloaded. Rename the unzipped folder to "php52".

development

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2012/05/22 08:06		current
Line 1:		Line 1:
	====== Setting up development environment ======		====== Setting up development environment ======
	run-tests.php is a PHP script so all you really need is a fairly standard development environment. This is a brief set of instructions.		run-tests.php is a PHP script so all you really need is a fairly standard development environment. This is a brief set of instructions.
-	If you just want to run the code this page is not for you - look [[http://wiki.php.net/qa/runtests/howtorun\|here]]	+	If you just want to run the code this page is not for you - look [[http://wiki.php.net/qa/runtests/howtorun\|here]]

	==== Installing PHP ====		==== Installing PHP ====

commandline

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/09/03 18:46		current
Line 7:		Line 7:
	\| h \| \| help \| yes \| yes \|		\| h \| \| help \| yes \| yes \|
	\| p \| PHP_TEST_EXECUTABLE \| Specifies PHP executable to be tested \| yes \| yes \|		\| p \| PHP_TEST_EXECUTABLE \| Specifies PHP executable to be tested \| yes \| yes \|
-	\| v \| \| Writes the PHP command that's passed to proc_open(), and ... \| NO (see below) \| \|	+	\| v \| \| Writes the PHP command that's passed to proc_open(), and ... \| yes \| yes, see verbose-mode \|
	\| q \| NO_INTERACTION \| Suppress option to send results to QA? Only ever relevant if run using 'make test' I think \| yes \| \|		\| q \| NO_INTERACTION \| Suppress option to send results to QA? Only ever relevant if run using 'make test' I think \| yes \| \|
	\| x \| SKIP_SLOW_TESTS \| Skip slow tests \| NO \| \|		\| x \| SKIP_SLOW_TESTS \| Skip slow tests \| NO \| \|
Line 29:		Line 29:
	\| show-(all, php...) \| \| Show 'all' files, 'php' test file ... etc \| NO \| \|		\| show-(all, php...) \| \| Show 'all' files, 'php' test file ... etc \| NO \| \|
	\| no-clean \| \| Don't execute the CLEAN section \| yes \| \|		\| no-clean \| \| Don't execute the CLEAN section \| yes \| \|
-	\| verbose \| \| Writes the PHP command that's passed to proc_open(), and... \| NO (see below) \| \|	+	\| verbose \| \| Writes the PHP command that's passed to proc_open(), and... \| yes \| yes, see verbose-mode \|

	===== New options =====		===== New options =====

howtorun

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2012/05/22 07:59		current
Line 26:		Line 26:

	===== Run the code =====		===== Run the code =====
-	At the moment the code will run a single test, eg:	+	Run a single test, eg:
	<code>		<code>
	runtests my_test.phpt		runtests my_test.phpt
	</code>		</code>

-	All the tests under a given directory, eg:	+	Run all the tests under a given directory, eg:
	<code>		<code>
	runtests ext/standard/tests/		runtests ext/standard/tests/
Line 37:		Line 37:

	The output format is different to run-tests.php. If a single test is run a short summary is printed to stdout. If one or more directories of tests are run the output is printed after each group (directory) of tests has been run. Again, a summary is printed to stdout but details are written to a file.		The output format is different to run-tests.php. If a single test is run a short summary is printed to stdout. If one or more directories of tests are run the output is printed after each group (directory) of tests has been run. Again, a summary is printed to stdout but details are written to a file.
		+
		+	Run all the tests under path_to_php/ext in parallel on 4 processors
		+
		+	<code>
		+	runtests path_to_php/ext -z 4
		+	</code>
		+
		+	Generate XML formatted output to a file:
		+
		+	<code>
		+	runtests -o xml -s /tmp/somefile path_to_php/tests
		+	</code>
		+
		+	Get more verbose results to the screen:
		+	<code>
		+	runtests -vvv path_to_php/tests
		+	</code>
		+
		+	Note: there are three levels of verbosity, -v, -vv and -vvv. But default all you will see is a '.' for each test.
		+

	<code>		<code>
Line 43:		Line 63:

	will give you all of the possible command line options.		will give you all of the possible command line options.
-

differencewindows

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/08/06 08:17		current
Line 1:		Line 1:
	^ Summary ^ Test name ^Reason for difference ^		^ Summary ^ Test name ^Reason for difference ^
-	\|3 tests fail in phpruntests and do not fail in run-tests \| \| \|	+	\|6 tests fail in phpruntests and do not fail in run-tests \| \| \|
	\| \| ext\standard\tests\general_functions\phpinfo.phpt\|Occasional fail – can't explain \|		\| \| ext\standard\tests\general_functions\phpinfo.phpt\|Occasional fail – can't explain \|
	\| \| tests\basic\bug20539.phpt \|This warns and skips in the old version, we are missing the warn and skip. Needs a fix? \|		\| \| tests\basic\bug20539.phpt \|This warns and skips in the old version, we are missing the warn and skip. Needs a fix? \|
		+	\| \| ext\standard\tests\mail\mail_basic_alt1-win32.phpt \| -"- \|
		+	\| \| ext\standard\tests\mail\mail_basic_alt2-win32.phpt \| -"- \|
		+	\| \| ext\standard\tests\mail\mail_basic_alt3-win32.phpt \| -"- \|
		+	\| \| ext\standard\tests\mail\mail_basic_alt4-win32.phpt \| -"- \|
	\|1 tests fail in run-tests and do not fail in phpruntests \| \| \|		\|1 tests fail in run-tests and do not fail in phpruntests \| \| \|
	\| \|ext\standard\tests\strings\bug37244.phpt \| \|		\| \|ext\standard\tests\strings\bug37244.phpt \| \|

testcoverage

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/04/30 19:53		current
Line 23:		Line 23:
	* genhtml dom.info -o dom_coverage. This will make a directory called dom_coverage with html coverage files in it.		* genhtml dom.info -o dom_coverage. This will make a directory called dom_coverage with html coverage files in it.
	* View the coverage files :-)		* View the coverage files :-)
		+
		+	==== How would I look at the coverage of a subset of the tests? ====
		+	For example - suppose I wanted to take all the tests which are there because of bug reports and just look at what the base test cases cover.
		+	* cd /home/zoe/BUILDS/php53_dev/ext/dom
		+	* '' find tests -name "bug*.phpt" \| xargs -i mv {} {}.bak '' ( Copies all the tests to test.phpt.bak )
		+	* make clean; make
		+	* cd /home/zoe/TESTS/coverage; ./runcov.sh run
		+	* run lcov and genhtml as above
		+
		+	Just for interest, the code coverage of the dom extension without the bug tests is 2101 of 4708 lines (44.6%).
		+
		+	Don't forget to copy the bug tests back afterwards:
		+	* '' find tests -name "bug*.phpt.bak" \| sed 's/.bak/ /' \| xargs -i mv {}.bak {} ''
		+	* NB: no space between the two slashes after .bak
		+
		+
		+
		+
		+

mac-test-environment

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2010/05/27 02:13		current
Line 47:		Line 47:

	Watch a Screencast demonstration of this entire process. [[http://www.youtube.com/watch?v=lkw5jQ_EU2A\|Screencast demonstration.]]		Watch a Screencast demonstration of this entire process. [[http://www.youtube.com/watch?v=lkw5jQ_EU2A\|Screencast demonstration.]]
		+
		+	===== Other Tips =====
		+
		+	Spotlight will index all of these PHP source files (including tests) and you might not want to do that. If not, consider doing the following:
		+
		+	* Open: //System Preferences//
		+	* Select: //Spotlight//
		+	* Select: //Privacy//
		+	* Select: //+//
		+	* Then, choose the root folder(s) you'd like to hide, like php52, php53, and php-trunk used in the demo.

differencemac4

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/08/05 20:44		current
Line 2:		Line 2:
	\|5 tests fail in phpruntests and do not fail in run-tests \| \| \|		\|5 tests fail in phpruntests and do not fail in run-tests \| \| \|
	\| \| ext/standard/tests/general_functions/phpinfo.phpt \| ? \|		\| \| ext/standard/tests/general_functions/phpinfo.phpt \| ? \|
-	\| \| ext/standard/tests/strings/htmlentities02.phpt \| not sure, but to me it looks like an encoding-problem of the test-files (?) \|	+	\| \| ext/standard/tests/strings/htmlentities02.phpt \| This test fails when mbstring is configd. It fails on both new and old code, its just that the status is reported as WARN&FAIL on the old version. The new one does not support mixed status flags \|
	\| \| ext/standard/tests/strings/htmlentities04.phpt \| --"-- \|		\| \| ext/standard/tests/strings/htmlentities04.phpt \| --"-- \|
	\| \| ext/standard/tests/strings/htmlentities15.phpt \| --"-- \|		\| \| ext/standard/tests/strings/htmlentities15.phpt \| --"-- \|

differencemac

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/08/05 20:43		current
Line 2:		Line 2:
	\|4 tests fail in phpruntests and do not fail in run-tests \| \| \|		\|4 tests fail in phpruntests and do not fail in run-tests \| \| \|
	\| \| ext/standard/tests/general_functions/phpinfo.phpt \| ? \|		\| \| ext/standard/tests/general_functions/phpinfo.phpt \| ? \|
-	\| \| ext/standard/tests/strings/htmlentities02.phpt \| not sure, but to me it looks like an encoding-problem of the test-files (?) \|	+	\| \| ext/standard/tests/strings/htmlentities02.phpt \| This test fails when mbstring is configd. It fails on both new and old code, its just that the status is reported as WARN&FAIL on the old version. The new one does not support mixed status flags \|
	\| \| ext/standard/tests/strings/htmlentities04.phpt \| --"-- \|		\| \| ext/standard/tests/strings/htmlentities04.phpt \| --"-- \|
	\| \| ext/standard/tests/strings/htmlentities15.phpt \| --"-- \|		\| \| ext/standard/tests/strings/htmlentities15.phpt \| --"-- \|

phptlessonslearned

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/07/17 17:59		current
Line 111:		Line 111:
	===== Submitting Tests =====		===== Submitting Tests =====

-	If you concentrate on a certain extension you will probably write several tests for this extension. When it's done you can submit those tests to the [[https://testfest.org/\|TestFest website]], but be sure, that every test is working fine. You can do so by running:	+	If you concentrate on a certain extension you will probably write several tests for this extension. When it's done you can submit those tests to the [[https://phptestfest.org/\|TestFest website]], but be sure, that every test is working fine. You can do so by running:

	make test TESTS=/path/to/php5/ext/yourextension/tests		make test TESTS=/path/to/php5/ext/yourextension/tests

difference

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/07/19 16:08		current
Line 1:		Line 1:
-	^ Summary ^ Test name ^ Reason for difference ^	+	^ Summary ^ Test name ^Reason for difference ^
	\|1 tests fail in phpruntests and do not fail in run-tests \| \| \|		\|1 tests fail in phpruntests and do not fail in run-tests \| \| \|
-	\| \|ext/standard/tests/general_functions/phpinfo.phpt \| Occasional fail – can't explain \|	+	\| \|ext/standard/tests/general_functions/phpinfo.phpt \|Occasional fail – can't explain \|
	\|1 tests fail in run-tests and do not fail in phpruntests \| \| \|		\|1 tests fail in run-tests and do not fail in phpruntests \| \| \|
-	\| \|ext/phar/tests/zip/phar_stub.phpt \| Occasional fail - can't explain \|	+	\| \|ext/standard/tests/mail/mail_variation2.phpt \|Occasional fail - can't explain \|
-	\|39 tests bork in phpruntests and do not bork in run-tests \| \| \|	+	\|4 tests bork in phpruntests and do not bork in run-tests \| \| \|
-	\| \| Zend/tests/function_exists_error.phpt \| empty section \|	+	\| \|ext/pdo_sqlite/tests/common.phpt \|Requires REDIRECTTEST \|
-	\| \| ext/pcre/tests/preg_split_basic.phpt \| empty section \|	+	\| \|ext/sqlite/tests/pdo/common.phpt \|Requires REDIRECTTEST \|
-	\| \|ext/pdo_sqlite/tests/common.phpt \| REDIRECTTEST \|	+	\| \|tests/lang/bug35382.phpt \|Requires FILEEOF, will not be implemented\|
-	\| \|ext/posix/tests/posix_access.phpt \| DESCRIPTION \|	+	\| \|tests/lang/comments2.phpt\|Requires FILEEOF, will not be implemented\|
-	\| \|ext/posix/tests/posix_access_error_modes.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_access_error_wrongparams.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_ctermid.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_getcwd.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_getgrnam.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_getpwnam.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_getrlimit.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_getsid.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_getsid_error.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_initgroups.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_isatty.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_mkfifo_safemode.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_mknod.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_times.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_ttyname.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_ttyname_error_wrongparams.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_uname.phpt \| DESCRIPTION \|	+
-	\| \|ext/sqlite/tests/pdo/common.phpt \| REDIRECTTEST \|	+
-	\| \|ext/standard/tests/array/bug40709.phpt \| empty section \|	+
-	\| \|ext/standard/tests/file/mkdir_variation5-win32.phpt \| empty section \|	+
-	\| \|ext/standard/tests/file/touch_basic-win32.phpt \| empty section \|	+
-	\| \|ext/standard/tests/strings/addslashes_basic.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/addslashes_error.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/addslashes_variation1.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/addslashes_variation2.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/addslashes_variation3.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/join_variation6.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/stripcslashes_variation1.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/ucwords_basic.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/ucwords_error.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/wordwrap_variation3.phpt \| empty section\|	+
-	\| \| tests/classes/arrayobject_001.phpt \| empty section\|	+
-	\| \|tests/lang/bug35382.phpt \| FILEEOF\|	+
-	\| \|tests/lang/comments2.phpt\| FILEEOF\|	+
-	\| \|tests/run-test/test010.phpt \| STDIN \|	+
	\|0 tests bork in run-tests and do not bork in phpruntests \| \| \|		\|0 tests bork in run-tests and do not bork in phpruntests \| \| \|
	\|0 tests skip in phpruntests and do not skip in run-tests \| \| \|		\|0 tests skip in phpruntests and do not skip in run-tests \| \| \|
-	\| 3 tests skip in run-tests and do not skip in phpruntests \| \| \|	+	\|0 tests skip in run-tests and do not skip in phpruntests \| \| \|
-	\| \|ext/posix/tests/posix_ttyname_error_wrongparams.phpt \|BORKS instead, could fix by deleting empty sects \|	+
-	\| \|ext/standard/tests/file/mkdir_variation5-win32.phpt \|BORKS instead, could fix by deleting empty sects \|	+
-	\| \|ext/standard/tests/file/touch_basic-win32.phpt \| BORKS instead, could fix by deleting empty sects\|	+

requirements

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/07/25 07:23		current
Line 31:		Line 31:
	* Provide the same functionality as REDEIRECTTEST, not necessarily using the current design		* Provide the same functionality as REDEIRECTTEST, not necessarily using the current design
	* Provide an API so thatthe code can be used by other applications (from Greg Beaver).		* Provide an API so thatthe code can be used by other applications (from Greg Beaver).
		+	* An option to specify arguments to valgrind

ubuntu-test-environment

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2010/05/18 01:22		current
Line 10:		Line 10:

	The rest of the instructions assume you will be building your test environment on your user's home directory "~/". If you choose to build in another location, please change the corresponding paths in all commands found throughout the rest of the instructions.		The rest of the instructions assume you will be building your test environment on your user's home directory "~/". If you choose to build in another location, please change the corresponding paths in all commands found throughout the rest of the instructions.
		+
	===== Download the Automated Build Scripts =====		===== Download the Automated Build Scripts =====

Line 37:		Line 38:

	You have now built a test environment for PHP on your desktop. The build environment will include a folder for each of the main PHP branches: “php52”, “php53”, and “php-trunk”.		You have now built a test environment for PHP on your desktop. The build environment will include a folder for each of the main PHP branches: “php52”, “php53”, and “php-trunk”.
		+
		+	===== Screencast =====
		+
		+	Watch a Screencast demonstration of this entire process. [[http://www.youtube.com/watch?v=w6HlZrPRJXo\|Screencast demonstration.]]

organisers

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 1:		Line 1:
		+	====== PHP TestFest Organizer Tips ======
		+
	==== Suggestions and checklist ====		==== Suggestions and checklist ====
		+
	===Advance planning===		===Advance planning===
		+
	* Contact your nearest user group to see if they are, or know of anybody already planning on running a TestFest in your area		* Contact your nearest user group to see if they are, or know of anybody already planning on running a TestFest in your area
	* Find a suitable location and choose a date within the TestFest range		* Find a suitable location and choose a date within the TestFest range
Line 15:		Line 19:

	===In the run-up to the event===		===In the run-up to the event===
		+
	* Svn access for the group is mailed to the organisers listed on http://wiki.php.net/qa/testfest		* Svn access for the group is mailed to the organisers listed on http://wiki.php.net/qa/testfest
	* Get a list of names of attendees (and email addresses) in advance		* Get a list of names of attendees (and email addresses) in advance
Line 26:		Line 31:

	===On the day===		===On the day===
		+
	* Either at the event or in advance have someone give a short talk on the extension and show example of how to use it		* Either at the event or in advance have someone give a short talk on the extension and show example of how to use it
	* Be prepared for network failure - have copies of PHP source, Windows builds and docs on a stick.		* Be prepared for network failure - have copies of PHP source, Windows builds and docs on a stick.

runtests

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2012/05/18 17:55		current
Line 6:		Line 6:
	Initial requirements are listed here, additional ones will be added as we find them.		Initial requirements are listed here, additional ones will be added as we find them.
	* [[http://wiki.php.net/qa/runtests/development\|Development]]		* [[http://wiki.php.net/qa/runtests/development\|Development]]
		+	If you are interested in in looking at the code, fixing bugs, understanding how it is tested etc. This is the section that you need.
	* [[http://wiki.php.net/qa/runtests/documentation\|Documentation]]		* [[http://wiki.php.net/qa/runtests/documentation\|Documentation]]
	This is developer documentation, it contains information for people who work on and maintain the code		This is developer documentation, it contains information for people who work on and maintain the code
	* [[http://wiki.php.net/qa/runtests/howtorun\|How to run the code]]		* [[http://wiki.php.net/qa/runtests/howtorun\|How to run the code]]
-	This is for users, there are instructions for checking out runnning and testing.	+	This is for users, there are instructions for checking out runnning the code.
	* [[http://wiki.php.net/qa/runtests/todos\|To do lists]]		* [[http://wiki.php.net/qa/runtests/todos\|To do lists]]
-	This is our current list of development items and the name of the person responsible for each one	+	This is our current list of development items.
	* [[http://wiki.php.net/qa/runtests/decisions\|Decisions]]		* [[http://wiki.php.net/qa/runtests/decisions\|Decisions]]
	Sometimes we have made a decision not to re-implement a feature of run-tests or to do something differently. The reasons for making such decions are recorded here.		Sometimes we have made a decision not to re-implement a feature of run-tests or to do something differently. The reasons for making such decions are recorded here.

curl

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 4:		Line 4:

	===== With a webserver =====		===== With a webserver =====
-	The cURL extensions tests can be run with the help of a file on a webserver that can be reached by the machine the tests are run on. An environmental variable pointing to the host needs to be set as follows (on Unix):\\	+	The cURL extensions tests can be run with the help of both a file on a webserver and a ftp server that can be reached by the machine the tests are run on. Environmental variables needs to be set as follows (on Unix):\\
-	<code>export PHP_CURL_HTTP_REMOTE_SERVER=http://www.example.com</code>	+	<code>
		+	export PHP_CURL_HTTP_REMOTE_SERVER=http://www.example.com
		+	export PHP_CURL_FTP_REMOTE_SERVER="ftp.example.net";
		+	export PHP_CURL_FTP_REMOTE_USER="ftpusername";
		+	export PHP_CURL_FTP_REMOTE_PASSWD="ftppassword";
		+	</code>
	Where http://www.example.com is the url to the host providing the test file. If the variable is not set the tests will assume you have webserver unning on the machine the tests are run on.		Where http://www.example.com is the url to the host providing the test file. If the variable is not set the tests will assume you have webserver unning on the machine the tests are run on.

-	The file used for testing can be found in the ''ext/curl/tests/responder'' directory and needs to be copied to the root of the webserver that is going to be used for testing.	+	The ''get.php'' file used for testing can be found in the ''ext/curl/tests/responder'' directory and needs to be copied to the root of the webserver that is going to be used for testing.

	===== With a local file =====		===== With a local file =====

webdev

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/07/23 19:21		current
Line 1:		Line 1:
	====== PHP TestFest 2008 ======		====== PHP TestFest 2008 ======
		+
		+	//This page contains out-dated material and is archived here for informational purposes. For recent information, see the [[qa:testfest\| main PHP TestFest page]].//

	===== Test Fest Web development team and strategies =====		===== Test Fest Web development team and strategies =====

testfest

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 1:		Line 1:
-	===== How do I join? How do I get more information? =====	+	====== PHP TestFest ======

-	See the [[http://qa.php.net/testfest.php\|TestFest]] homepage on the QA team website for details. Alternatively you can join #php.pecl on Efnet or the #phptestfest channel on Freenode IRC server. There should usually be someone around to help.	+	See the [[https://phptestfest.org/\|PHP TestFest]] homepage for details. Alternatively you can join the ''#phptestfest'' channel on Freenode IRC and follow [[https://twitter.com/phptestfest\|@phptestfest]] on Twitter.
-	Follow twitter [[http://twitter.com/phptestfest\|testfest]]	+

-	==== Summary of registered groups ====	+	===== Historical Information =====

-	^ Group name ^ Date ^ Ext to test ^ mentor ^ Organiser email ^	+	* [[qa:testfest-2009\|PHP TestFest 2009]]
-	\| Belgium \| May 9 \| SQlite3, ldap \| Felix de Vleigher \| felixdv@php.net \|	+	* [[qa:testfest-2010\|PHP TestFest 2010]]
-	\| Brazil (SP ) \| June 20 \| \| \| rdohms@gmail.com \|	+
-	\| Brazil (Rio) \| July 3 \| \| Igor Feghali \| ifeghali@php.net \|	+
-	\| Brazil(BR) \| June 23 \| \| Er Galvao Abbott \| galvao@galvao.eti.br \|	+
-	\| Brazil(SC) \| \| \| \| silvano@php.net \|	+
-	\| Brazil(CEPUG) \| \| \| \| brunoviana@gmail.com \|	+
-	\| Catalonia \| June 13 \| \| Hannes Magnusson \| alex@corretge.cat \|	+
-	\| Canada (Montreal) \| May 1/2/3 \| Date, time \| Derick Rethans \| afilina@phpquebec.org \|	+
-	\| Colombia \| \| \| \| andphe@gmail.com \|	+
-	\| France \| May 9 \| CURL \| \| perrick@noparking.net \|	+
-	\| Germany (Munich) \| April 16/17 \| \| Pierre Joye \| Pierre Joye \|	+
-	\| Germany (Berlin) \| May 9/10 \| gettext, sockets, soap, xsl, posix \| \| till@php.net \|	+
-	\| Germany (Wurzburg)\| May 30/31 \| \| \| info@fruityweb.de \|	+
-	\| Ireland \| \| \| \| davic@php.ie \|	+
-	\| Italy \| June 20/20/21 \| \| \| francesco@cphp.it \|	+
-	\| Netherlands \| May 9 \| CURL \| \| stefan@phpgg.nl \|	+
-	\| Norway \| June 9 \| \| Hannes Magnusson \| russ@redpill-linpro.com\|	+
-	\| Peru \| April 4 \| \| \| info.latino@dokeos.com \|	+
-	\| USA (tek) \| May 21 \| \| \| stefan@phpgg.nl \|	+
-	\| USA (NYPHP) \| May 23 \| XmlReader/XMLWriter/DOM \| Elizabeth Smith \| Hans Zaunere \|	+
-	\| USA (Atlanta) \| \| DOM \| \| Ben Ramsey \|	+
-	\| USA (Nashville) \| \| \| \| Will Fitch \|	+
-	\| UK (London) \| May 9 \| SPL \| Zoe Slattery \| matt.raines@phplondon.org \|	+
-	\| UK (NorthWest) \| May 9 \| SPL \| Scott MacVicar \| lorna@lornajane.net \|	+
-	\| NZ (Christchurch) \| June 20 \| \| \| lukemoynihan@gmail.com \|	+

-	==== Results ====
-	See
-	* http://results.testfest.php.net/displayresults.php (32 bit)
-	* http://testfest.php.net/displayresults.php (64 bit)
-
-
-	===== Registered UGs =====
-
-	==== Belgium ====
-
-
-	* Belgian PHP Usergroup, http://www.phpbelgium.be.
-	* Contact: Felix De Vliegher, <felixdv@php.net>
-	* Date: Saturday May 9th 9am-6pm
-	* Location: Combell offices, Skaldenstraat 121, 9042 Gent, Belgium [[http://maps.google.com/maps?f=q&source=s_q&hl=nl&geocode=&q=Skaldenstraat+121+Gent+9042&sll=37.0625,-95.677068&sspn=34.534108,93.076172&ie=UTF8&ll=51.113707,3.788931&spn=0.006681,0.022724&z=16&iwloc=A \| Google maps]]
-	* Subscribe/RSVP here: http://tr.im/jpSY
-	* Extension to test: SQLite3, Ldap
-
-	==== Brazil ====
-
-	* PHPSP (http://www.phpsp.org.br) Contact Names: Augusto Pascutti & Rafael Dohms <admin@phpsp.org.br> - May
-	* PHP Rio (http://www.phprio.org) Contact Name: Igor Feghali <ifeghali@php.net>
-	* PHPBR (http://www.phpbr.com.br) Contact Name: Er Galvão Abbott <galvao@phpbr.com.br>
-	* PHPSC (http://www.phpsc.com.br) Contact Name: Silvano Girardi Jr. <silvano@php.net>
-	* CEPUG (http://www.cepug.org) Contact Name: Bruno Viana <brunoviana@gmail.com>
-
-	==== Catalonia ====
-
-	* CCCPHP, http://cccphp.net. Saturday 13th of june at [[http://ca.wikipedia.org/wiki/Verges\|Verges]] (Baix Empordà). [[http://cccphp.googlecode.com/svn/trunk/org.TestFest2009/cartell%20PHP%20TestFest%202009.pdf\|Agenda]]. [[http://www.facebook.com/home.php#/event.php?eid=75135753753&ref=ts\|Facebook]]. Return of Service to Open Source. Contact name: Àlex Corretgé, <alex@corretge.cat>
-
-	==== Canada ====
-
-	=== Montreal ===
-
-	* Organized by PHP Quebec [[http://phpquebec.org]]
-	* Contact: Anna Filina <afilina@phpquebec.org>
-	* Dates
-	* Friday May 1st 7pm-10pm (social/casual/unofficial warm-up)
-	* Saturday May 2nd 9am-6pm (TestFest/CodeFest)
-	* Sunday May 3rd 9am-6pm (TestFest/CodeFest)
-	* Location: Helm - 273 Bernard W.
-	* More info about the event: [[http://codefest.ws]]
-
-	==== Colombia ====
-
-	* Organized by Colombia PHP [[http://groups.google.com/group/php-colombia]] [[http://www.colombiaphp.net]]
-	* Contact: Andrés Felipe Vargas <andphe@gmail.com>
-	* Date: to define
-	* Location: irc #php-co at freenode.net
-
-	==== France ====
-
-	=== Paris ===
-
-	* Organized by AFUP[[http://afup.org]]
-	* Contact: Perrick Penet <perrick@noparking.net>
-	* Date: Saturday May 9th 10am-8pm (PhpCamp / TestFest)
-	* Location: La Cantine - 151 rue Montmartre - Passage des Panoramas - 12 Galerie Montmartre - 75002 Paris
-	* More info about the event: [[http://afup.org/pages/rendezvous/?id=6]]
-	* Extension to test: CURL
-
-
-	==== Germany ====
-
-	=== Munich ===
-	* PLEASE RSVP:
-	* Contact Pierre, email:pierre@php.net
-	* or come online on Freenode #phptestfest
-
-	* Prepare Slides
-	* How PHP Works
-	* [[http://wiki.php.net/qa/testfesttalk\|How to write PHPT]]
-	* 16th Evening Meeting will stand at [[http://www.nockherberg.com/\|Nockhenberg Biergarten]]
-	* 18.30 Welcome
-	* 19.00 Talks
-	* PHP 5.3 - Sebastian Bergmann
-	* QA and PHP, Sebastian Schürmann
-	* Food&Drinks
-	* 17th TestFest Day
-	* Location: [[http://www.microsoft.com/germany/unternehmen/informationen/gmbh_profil/niederlassungen/muenchen.mspx\|Microsoft EMEA Office in Unterschleißheim]]
-	* 09:30 welcome, 09:45 presentation (until ~11:30)
-	* Introductions and presentations of the test infrastructure for PHP
-	* Write a bunch of tests :)
-
-
-
-	=== Berlin ===
-
-	* Contact Till, email:till@php.net
-
-	* Chosen date: May 9th/10th (weekend)
-
-	* Location: [[http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Boxhagener+Stra%C3%9Fe+119,+10245+Friedrichshain,+Berlin&sll=52.50743,13.467888&sspn=0.010239,0.019312&ie=UTF8&ll=52.512447,13.461277&spn=0.010238,0.019312&t=h&z=16&iwloc=addr\|Boxhagener Str. 119, Berlin]]
-
-	* PLEASE RSVP: [[http://wiki.upstream-berlin.com/index.php/PHPTestFest2009]]
-
-	* Extensions: gettext, sockets, soap, xsl, posix
-
-	* Blog entries about the testfest:
-	* http://cweiske.de/tagebuch/PHP%20Testfest%20Berlin%202009.htm
-	* http://till.klampaeckel.de/blog/archives/34-Great-success!.html
-
-	=== Würzburg ===
-	* The PHP user group Wuerzburg decided to start a test fest from 30 May to 31 May.
-	* Contact - Steffen Hartmann <info@fruityweb.de>
-
-	* UG Website: [[http://www.phpug-wuerzburg.de/]]
-
-	==== Ireland ====
-
-	* Irish PHP User Group (http://php.ie). Contact Jaime Hemmett email: jaime@hemmett.org, David Coallier email: davidc@php.ie
-
-	==== Italy ====
-
-	=== Cesena ===
-
-	* Organized by [[http://www.grusp.it\|GrUSP]] and [[http://www.ideato.it\|ideato srl]]
-	* Contact: Francesco Trucchia <francesco@cphp.it>
-	* Dates
-	* Friday June 19 10-17 (Code dojo TestFest)
-	* Saturday June 20 10-17 (Pair CodeFest)
-	* Sunday June 21 10-17 (Deploy TestFest)
-	* Location: [[http://maps.google.it/maps?f=q&source=s_q&hl=it&geocode=&q=ideato&ie=UTF8&z=8&iwloc=A\|Ideato srl]] - via Quinto Bucci 205, 47023 Cesena (FC).
-	* More info about the event: [[http://wiki.grusp.it/eventi:phptestfest:riviera2009]]
-
-	==== Netherlands ====
-
-	* Organized by [[http://phpgg.nl/\|Dutch PHP Usergroup]] with support of [[http://www.microsoft.nl/\|Microsoft]]
-	* Contact: Stefan Koopmanschap <stefan@phpgg.nl>
-	* Date and time: Saturday 9 May, 10:30 - 17:00
-	* Location: Hogeschool Domstad, Utrecht
-	* More info about the event: [[http://phpgg.nl/testfest2009\|TestFest 2009]]
-	* Focus on extension: curl
-
-	==== Norway ====
-
-	===Oslo===
-
-	* Organized by [[http://php.no/\|Norway PHP Usergroup]] in association with [[http://redpill-linpro.com/\|Redpill Linpro]]
-	* Contact: Russell Flynn <russ@redpill-linpro.com>
-	* Date and time: Tuesday 9th June, 15:30 - 22:00
-	* Location: Offices of [[http://redpill-linpro.com/\|Redpill Linpro]], Storo, Oslo
-	* More info about the event: [[http://php.no/wiki/index.php?title=09.06.2009_-_TestFest\|TestFest 2009 Norway]]
-
-	==== Peru ====
-	* Grupo PHP Perú, www.php.org.pe. Contact name: Yannick Warnier, email: info.latino@dokeos.com (Meeting 4/4/9) ([[http://dokeoslead.wordpress.com/2009/04/05/php-testfest-2009-first-try/ \| See report ]])
-	==== USA ====
-
-	* php\|tek (http://tek.mtacon.com/c/s/hackathon) Contact names Stefan Koopmanschap email:stefan@phpgg.nl, Matthew Turland matthew@blueparabola.com
-	* NYPHP (http://www.nyphp.org) Contact name: Hans Zaunere
-	* Extensions to test: xmlreader/xmlwriter
-	* Atlanta PHP (http://atlantaphp.org) Contact name: Ben Ramsey. Subject: DOM
-	* Nashville PHP (http://www.nashvillephp.org) Contact name: Will Fitch
-
-	==== UK ====
-
-	* PHP NorthWest. Contact Lorna Jane Mitchell. email: lorna@lornajane.net
-	* Date and Time: Saturday 9th May, 12 noon until 4pm
-	* Location: Newton Building, School of Computing, Science and Engineering, Salford University
-	* Extension to test: SPL
-	* PHP London. Contact Matt Raines. email: matt.raines@phplondon.org
-	* Planned date Saturday May 9th - 10:00 to 18:00.
-	* Location IBM Southbank buildings
-	* Extension to test: SPL
-	* Sign up here: http://www.phplondon.org/wiki/May_9th_2009
-
-	==== NZ ====
-
-	* Web Design Meetup Christchurch. Contact Luke Moynihan. email lukemoynihan@gmail.com
-	* Date and Time: Saturday 20th June, 10am until 5pm
-	* Location: Media Suite, Ferrymead, 23 Humphreys Drive, Office 6 (above Kenso)
-	* Please RSVP
-
-
-	===== Individuals looking for local events =====
-	This is a log of individual requests to groups participating in TestFest.
-	* Looking for an event in Bulgaria (Sofia)
-	===== Available Mentors =====
-	^ Mentor Name ^ Area of expertise ^ User group to mentor ^ Dates unavailable on-line ^
-	\| Hannes Magnusson \| Any extension is OK \| Catalonia and Norway \| \|
-	\| Scott MacVicar \| \| PHPNW \| \|
-	\| Mikko Koppanen \| \| \| \|
-	\| Elizabeth Marie Smith \| Anything but XML ext \| In USA - Midwest - NEW YORK \| \|
-	\| Derick Rethans \| \| \| \|
-	\| Pierre A. Joye \| \| Munich (with dsop), NL \| \|
-	\| Felix De Vliegher \| \| Belgium \| \|
-	\| Igor Feghali \| \| Rio, SP and CEPUG (Brazil) \| \|
-	\| Ant Phillips \| \| \| \|
-	\| Zoe Slattery \| Anything core \| London \| 7th - 15th April (likely) \|
-	\| Raghubansh Kumar \| Anything core, Coding Guidelines \| \| \|
-	\| Nuno Lopes \| \| Lisbon and Germany \| \|
-	\| Michael Maclean \| XML exts \| \| 11th to 18th April \|
-	\| Till Klampaeckel \| \| Berlin, Germany \| \|
-
-
-	===== To do list =====
-	===== Materials for user groups: =====
-	* iso images with PHP executable, PHP source, DOCS.
-	* Linux. Owner:
-	* Windows. Owner: Pierre
-	* OSX. Owner:
-	* A place to put the iso images so that people can download them. Owner:
-	* VM images with full test environment.
-	* Windows image. Owner: Pierre
-	* OSX?
-	* Linux VirtualBox VM (Ubuntu 32-bit for now): Eric Lee Stewart (http://www.ericstewart.org/tfvm/)
-	* Unix VirtualBox VM (FreeBSD 32-bit for now): <del>Eric Lee Stewart</del>
-
-	===== Locations =====
-	* Companies prepared to loan their offices on a Saturday?
-	===== Other Resources =====
-
-	==== Internal ====
-	* [[QA:PHPTLessonsLearned\|Lessons Learned in PHP Testing]]
-	* [[QA:TestCoverage\|How to get test coverage (Linux)]]
-	* [[QA:WhatToTest\|More information on what to test]]
-	* [[QA:Credits\|Crediting test case authors]]
-	* [[QA:Uploading\|Where to put tests]] (Testfest SVN)
-	* [[QA:Organisers\|Suggestions & checklist for TestFest organisers]]
-	* [[qa:testfesttalk\|A reusable talk for the 2009 testfest]]
-	* [[qa:svnnote\|note for SVN admins]]
-
-	==== External ====
-	* [[http://sebastian-bergmann.de/archives/776-Prepare-for-TestFest.html\|Attendees: how to prepare for TestFest]]
-	* [[http://sebastian-bergmann.de/archives/777-PHP-Test-Fest-Slides.html\|Basics on phpt slides]]
-	* [[http://cvs.php.net/viewvc.cgi/php-src/README.TESTING?revision=1.24&view=markup\|Information on run-test.php]]
-	* [[http://felix.phpbelgium.be/blog/2008/05/22/writing-phpt-tests-on-your-mac/\|Writing phpt tests on Mac OS X]]

configure

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/05/18 21:05		current
Line 7:		Line 7:
	./configure --prefix=/Users/g2/php/ --with-config-file-path=/Users/g2/php/php53/ --with-pear=/opt/local/ --with-iconv=/opt/local --with-bz2=/opt/local/ --with-zlib=/opt/local/ --with-libxml-dir=/opt/local --with-gettext=/opt/local --with-libexpat-dir=/opt/local --with-freetype-dir=/opt/local --with-openssl=/opt/local/ --with-t1lib=/opt/local/ --with-tidy=/opt/local --with-xsl=/opt/local --with-curl=/opt/local --with-pcre-regex=/opt/local --with-gd --with-jpeg-dir=/opt/local --with-png-dir=/opt/local --with-mhash=/opt/local --with-mcrypt=/opt/local --with-readline=/opt/local --enable-fastcgi --disable-short-tags --enable-pcntl --enable-soap --enable-exif --enable-sockets --enable-sysvsem --enable-sysvshm --with-xml --enable-sysvmsg --enable-calendar --enable-exif --with-xmlrpc --enable-ftp --enable-wdd --enable-soap --enable-bcmath --enable-mbstring --enable-dba --enable-zip --with-mime-magic --enable-gd-native-ttf --enable-xdebug		./configure --prefix=/Users/g2/php/ --with-config-file-path=/Users/g2/php/php53/ --with-pear=/opt/local/ --with-iconv=/opt/local --with-bz2=/opt/local/ --with-zlib=/opt/local/ --with-libxml-dir=/opt/local --with-gettext=/opt/local --with-libexpat-dir=/opt/local --with-freetype-dir=/opt/local --with-openssl=/opt/local/ --with-t1lib=/opt/local/ --with-tidy=/opt/local --with-xsl=/opt/local --with-curl=/opt/local --with-pcre-regex=/opt/local --with-gd --with-jpeg-dir=/opt/local --with-png-dir=/opt/local --with-mhash=/opt/local --with-mcrypt=/opt/local --with-readline=/opt/local --enable-fastcgi --disable-short-tags --enable-pcntl --enable-soap --enable-exif --enable-sockets --enable-sysvsem --enable-sysvshm --with-xml --enable-sysvmsg --enable-calendar --enable-exif --with-xmlrpc --enable-ftp --enable-wdd --enable-soap --enable-bcmath --enable-mbstring --enable-dba --enable-zip --with-mime-magic --enable-gd-native-ttf --enable-xdebug
	</html>		</html>
		+
		+	=====Further Information=====
		+
		+	[[http://www.php.net/manual/en/configure.php\|PHP Manual - configure options]]

svnnote

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/09/01 07:55	current
Line 1:	Line 1:
	+	Hi XXXX
	+
	+	I've added you as an 'organiser' in the TestFest Subversion repository. The repository is here:
	+
	+	http://testfest.php.net/repos/testfest
	+
	+	You have the authority to add other users from your User Group. To do this, use the web interface here:
	+
	+	http://testfest.php.net/testfest.php
	+
	+	Log in using this user ID : YYYY (email)
	+
	+	and this password:
	+	some-passwd
	+
	+	Please only check tests in under the directory:
	+
	+	http://testfest.php.net/repos/testfest/group-name
	+
	+	To checkout:
	+
	+	svn checkout http://testfest.php.net/repos/testfest/user-group-name
	+
	+	where user-group-name = NewZealandUG for example.
	+
	+	To add new tests to version control:*
	+
	+	svn add
	+
	+	To commit tests:
	+
	+	svn commit -m 'new tests for whatever' ---username=your-user-name --password your-password
	+
	+	Please make sure that people attending your event have a subversion client installed

uploading

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/03/10 14:10		current
Line 1:		Line 1:
	===== What to do with your test when you have written it =====		===== What to do with your test when you have written it =====

-	At the moment the best thing to do is send the test to the QA mailing list, php-qa@lists.php.net. For the 2009 TestFest we will be setting up a Subversion repository so that users can check in their tests directly. When this is available instructions for how to use it will be added to this page.	+	There is an SVN repository here:

		+	http://testfest.php.net/repos/testfest

-	* TBD - owner zoe@php.net	+	Directories have been created for each registered user group, for example, http://testfest.php.net/repos/testfest/LondonUG is for use by the London user group.
		+
		+	Under each user group directory there is a directory structure which is exactly the same as the PHP 53 source tree, except that only test directories are included and there are no files in any directory. There is a directory called 'Independent Contributors' for people that are not associated with any particular user group.
		+
		+	The intention is that groups or individuals will put tests in the right place in the source tree, for example, tests for strings functions would go in ~ext/standard/tests/strings. If you aren't clear about where to put tests please ask or have a look at the full PHP source tree for tests of similar types.
		+
		+	==== Access to SVN ====
		+
		+	Anyone can browse the repository or checkout files, eg
		+
		+	svn checkout http://testfest.php.net/repos/testfest/LondonUG
		+
		+	We will add all user group leads as SVN administrators - it will then be your responsibility to grant access to other members of your groups. A user interface to help with that is being developed.
		+
		+	A user ID and password is requred to be able to check in.
		+
		+
		+
		+
		+
		+
		+

performance

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/08/21 20:19		current
Line 8:		Line 8:
	[[http://wiki.php.net/_media//qa/runtests/documentation/performance_chart.png?w=&h=&cache=cache\|{{:qa:runtests:documentation:performance_chart_thumb.png\|}}]]		[[http://wiki.php.net/_media//qa/runtests/documentation/performance_chart.png?w=&h=&cache=cache\|{{:qa:runtests:documentation:performance_chart_thumb.png\|}}]]

-	For detailed data have a look at this file:	+	For the detailed data have a look at this file:
	{{:qa:runtests:documentation:taskscheduler_performance.ods\|taskScheduler_performance.ods}}		{{:qa:runtests:documentation:taskscheduler_performance.ods\|taskScheduler_performance.ods}}

Line 14:		Line 14:
	===== cpu-usage =====		===== cpu-usage =====

-	As you can see the new phpruntests is able to exhaust the cpu much more better than the old version:	+	As you can see the new phpruntests is able to exhaust the cpu much more better than the old version. (This screen is from a 4-way MacPro).

	[[http://wiki.php.net/_media//qa/runtests/documentation/cpu_usage.png?w=&h=&cache=cache\|{{:qa:runtests:documentation:cpu_usage_thumb.png\|}}]]		[[http://wiki.php.net/_media//qa/runtests/documentation/cpu_usage.png?w=&h=&cache=cache\|{{:qa:runtests:documentation:cpu_usage_thumb.png\|}}]]

-	(This screen is from a 4-way MacPro).

todos

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2012/05/21 21:08		current
Line 15:		Line 15:
	* Package as a single file (like run-tests.php)		* Package as a single file (like run-tests.php)
	* Add a test using --disable-all and check that it runs (not parallel, which will always need pcntl()...DONE		* Add a test using --disable-all and check that it runs (not parallel, which will always need pcntl()...DONE
		+	* Code review
		+	* Should rtTestTaskGroup and rtPhpTestGroup be merged?
		+	* Check memory usage

codingstandards

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/07/25 10:55		current
Line 1:		Line 1:
	====== Coding Standards ======		====== Coding Standards ======
		+	* Use the [[http://pear.php.net/manual/en/standards.php\|PEAR coding standard]] (22/04/2009 - see php-qa list for concerns)
		+	* Deviation from the standard: Do not use _ prefix for private members. (Reason: too much re-work to existing code)
		+	* We prefix classnames with rt (Reason: avoid name conflicts with built-in PHP classes)
		+	* We do not follow the original PEAR class naming scheme (Reason: we use autoload and name prefixes, so we can keep classnames shorter than DIR_DIR_DIR_CLASS)
		+	* We will not include both File and Class doc blocks. (Reason: Only ever one class per file)
		+	* Don't use private, always use protected instead. (Requested by Greg)

decisions

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/07/25 11:02		current
Line 4:		Line 4:
	* [[http://wiki.php.net/qa/runtests/decisions/codingstandards\|Coding Standards]]		* [[http://wiki.php.net/qa/runtests/decisions/codingstandards\|Coding Standards]]
	* [[http://wiki.php.net/qa/runtests/decisions/notimplemented\|Decided not to re-implement]]		* [[http://wiki.php.net/qa/runtests/decisions/notimplemented\|Decided not to re-implement]]
		+	* [[http://wiki.php.net/qa/runtests/decisions/design\|Design decisions]]

qa

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2012/05/22 08:03		current
Line 1:		Line 1:
	====== Test differences between the old and new versions of run-tests ======		====== Test differences between the old and new versions of run-tests ======

-	All differences are reported for the standard PHPT QA set - see [[http://wiki.php.net/qa/runtests/howtorun\|here]] for a description of the test set and instructions on how to run.	+	All differences are reported for the standard PHPT QA set - see [[http://wiki.php.net/qa/runtests/development\|here]] for a description of the test set and instructions on how to run.

	===== Linux sequential running =====		===== Linux sequential running =====

notimplemented

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/09/01 07:55	current
Line 1:	Line 1:
	+	====== Things which will not be re-implemented ======
	+
	+	===== GZIP_POST, DEFLATE_POST =====
	+	The way these are currently implemented the test has to look like this:
	+
	+	<code>
	+	--POST--
	+	Some posted content
	+
	+	--GZIP_POST--
	+	1
	+	--FILE--
	+	etc
	+	</code>
	+
	+	This isn't really necessary. In the new implementation the --GZIP_POST-- section will just contain the content to be posted and gzip'd. Same for DEFLATE_POST.
	+	This affects two tests:
	+
	+	* ext/soap/tests/server019.phpt
	+	* ext/soap/tests/server020.phpt
	+
	+

screencasts

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/09/01 07:55	current
Line 1:	Line 1:
	+	====== Screencasts ======

	+	Some quick screencasts to show you how to write tests.
	+
	+	[[http://www.youtube.com/watch?v=ehF3vD3sS6w\|How to write a simple phpt]]

2009/09/03 18:46		current
Line 7:		Line 7:
	\| h \| \| help \| yes \| yes \|		\| h \| \| help \| yes \| yes \|
	\| p \| PHP_TEST_EXECUTABLE \| Specifies PHP executable to be tested \| yes \| yes \|		\| p \| PHP_TEST_EXECUTABLE \| Specifies PHP executable to be tested \| yes \| yes \|
-	\| v \| \| Writes the PHP command that's passed to proc_open(), and ... \| NO (see below) \| \|	+	\| v \| \| Writes the PHP command that's passed to proc_open(), and ... \| yes \| yes, see verbose-mode \|
	\| q \| NO_INTERACTION \| Suppress option to send results to QA? Only ever relevant if run using 'make test' I think \| yes \| \|		\| q \| NO_INTERACTION \| Suppress option to send results to QA? Only ever relevant if run using 'make test' I think \| yes \| \|
	\| x \| SKIP_SLOW_TESTS \| Skip slow tests \| NO \| \|		\| x \| SKIP_SLOW_TESTS \| Skip slow tests \| NO \| \|
Line 29:		Line 29:
	\| show-(all, php...) \| \| Show 'all' files, 'php' test file ... etc \| NO \| \|		\| show-(all, php...) \| \| Show 'all' files, 'php' test file ... etc \| NO \| \|
	\| no-clean \| \| Don't execute the CLEAN section \| yes \| \|		\| no-clean \| \| Don't execute the CLEAN section \| yes \| \|
-	\| verbose \| \| Writes the PHP command that's passed to proc_open(), and... \| NO (see below) \| \|	+	\| verbose \| \| Writes the PHP command that's passed to proc_open(), and... \| yes \| yes, see verbose-mode \|

	===== New options =====		===== New options =====

2009/08/06 08:17		current
Line 1:		Line 1:
	^ Summary ^ Test name ^Reason for difference ^		^ Summary ^ Test name ^Reason for difference ^
-	\|3 tests fail in phpruntests and do not fail in run-tests \| \| \|	+	\|6 tests fail in phpruntests and do not fail in run-tests \| \| \|
	\| \| ext\standard\tests\general_functions\phpinfo.phpt\|Occasional fail – can't explain \|		\| \| ext\standard\tests\general_functions\phpinfo.phpt\|Occasional fail – can't explain \|
	\| \| tests\basic\bug20539.phpt \|This warns and skips in the old version, we are missing the warn and skip. Needs a fix? \|		\| \| tests\basic\bug20539.phpt \|This warns and skips in the old version, we are missing the warn and skip. Needs a fix? \|
		+	\| \| ext\standard\tests\mail\mail_basic_alt1-win32.phpt \| -"- \|
		+	\| \| ext\standard\tests\mail\mail_basic_alt2-win32.phpt \| -"- \|
		+	\| \| ext\standard\tests\mail\mail_basic_alt3-win32.phpt \| -"- \|
		+	\| \| ext\standard\tests\mail\mail_basic_alt4-win32.phpt \| -"- \|
	\|1 tests fail in run-tests and do not fail in phpruntests \| \| \|		\|1 tests fail in run-tests and do not fail in phpruntests \| \| \|
	\| \|ext\standard\tests\strings\bug37244.phpt \| \|		\| \|ext\standard\tests\strings\bug37244.phpt \| \|

2009/08/05 20:44		current
Line 2:		Line 2:
	\|5 tests fail in phpruntests and do not fail in run-tests \| \| \|		\|5 tests fail in phpruntests and do not fail in run-tests \| \| \|
	\| \| ext/standard/tests/general_functions/phpinfo.phpt \| ? \|		\| \| ext/standard/tests/general_functions/phpinfo.phpt \| ? \|
-	\| \| ext/standard/tests/strings/htmlentities02.phpt \| not sure, but to me it looks like an encoding-problem of the test-files (?) \|	+	\| \| ext/standard/tests/strings/htmlentities02.phpt \| This test fails when mbstring is configd. It fails on both new and old code, its just that the status is reported as WARN&FAIL on the old version. The new one does not support mixed status flags \|
	\| \| ext/standard/tests/strings/htmlentities04.phpt \| --"-- \|		\| \| ext/standard/tests/strings/htmlentities04.phpt \| --"-- \|
	\| \| ext/standard/tests/strings/htmlentities15.phpt \| --"-- \|		\| \| ext/standard/tests/strings/htmlentities15.phpt \| --"-- \|

2009/08/05 20:43		current
Line 2:		Line 2:
	\|4 tests fail in phpruntests and do not fail in run-tests \| \| \|		\|4 tests fail in phpruntests and do not fail in run-tests \| \| \|
	\| \| ext/standard/tests/general_functions/phpinfo.phpt \| ? \|		\| \| ext/standard/tests/general_functions/phpinfo.phpt \| ? \|
-	\| \| ext/standard/tests/strings/htmlentities02.phpt \| not sure, but to me it looks like an encoding-problem of the test-files (?) \|	+	\| \| ext/standard/tests/strings/htmlentities02.phpt \| This test fails when mbstring is configd. It fails on both new and old code, its just that the status is reported as WARN&FAIL on the old version. The new one does not support mixed status flags \|
	\| \| ext/standard/tests/strings/htmlentities04.phpt \| --"-- \|		\| \| ext/standard/tests/strings/htmlentities04.phpt \| --"-- \|
	\| \| ext/standard/tests/strings/htmlentities15.phpt \| --"-- \|		\| \| ext/standard/tests/strings/htmlentities15.phpt \| --"-- \|

2009/07/19 16:08		current
Line 1:		Line 1:
-	^ Summary ^ Test name ^ Reason for difference ^	+	^ Summary ^ Test name ^Reason for difference ^
	\|1 tests fail in phpruntests and do not fail in run-tests \| \| \|		\|1 tests fail in phpruntests and do not fail in run-tests \| \| \|
-	\| \|ext/standard/tests/general_functions/phpinfo.phpt \| Occasional fail – can't explain \|	+	\| \|ext/standard/tests/general_functions/phpinfo.phpt \|Occasional fail – can't explain \|
	\|1 tests fail in run-tests and do not fail in phpruntests \| \| \|		\|1 tests fail in run-tests and do not fail in phpruntests \| \| \|
-	\| \|ext/phar/tests/zip/phar_stub.phpt \| Occasional fail - can't explain \|	+	\| \|ext/standard/tests/mail/mail_variation2.phpt \|Occasional fail - can't explain \|
-	\|39 tests bork in phpruntests and do not bork in run-tests \| \| \|	+	\|4 tests bork in phpruntests and do not bork in run-tests \| \| \|
-	\| \| Zend/tests/function_exists_error.phpt \| empty section \|	+	\| \|ext/pdo_sqlite/tests/common.phpt \|Requires REDIRECTTEST \|
-	\| \| ext/pcre/tests/preg_split_basic.phpt \| empty section \|	+	\| \|ext/sqlite/tests/pdo/common.phpt \|Requires REDIRECTTEST \|
-	\| \|ext/pdo_sqlite/tests/common.phpt \| REDIRECTTEST \|	+	\| \|tests/lang/bug35382.phpt \|Requires FILEEOF, will not be implemented\|
-	\| \|ext/posix/tests/posix_access.phpt \| DESCRIPTION \|	+	\| \|tests/lang/comments2.phpt\|Requires FILEEOF, will not be implemented\|
-	\| \|ext/posix/tests/posix_access_error_modes.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_access_error_wrongparams.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_ctermid.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_getcwd.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_getgrnam.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_getpwnam.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_getrlimit.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_getsid.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_getsid_error.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_initgroups.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_isatty.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_mkfifo_safemode.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_mknod.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_times.phpt \| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_ttyname.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_ttyname_error_wrongparams.phpt\| DESCRIPTION \|	+
-	\| \|ext/posix/tests/posix_uname.phpt \| DESCRIPTION \|	+
-	\| \|ext/sqlite/tests/pdo/common.phpt \| REDIRECTTEST \|	+
-	\| \|ext/standard/tests/array/bug40709.phpt \| empty section \|	+
-	\| \|ext/standard/tests/file/mkdir_variation5-win32.phpt \| empty section \|	+
-	\| \|ext/standard/tests/file/touch_basic-win32.phpt \| empty section \|	+
-	\| \|ext/standard/tests/strings/addslashes_basic.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/addslashes_error.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/addslashes_variation1.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/addslashes_variation2.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/addslashes_variation3.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/join_variation6.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/stripcslashes_variation1.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/ucwords_basic.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/ucwords_error.phpt \| empty section\|	+
-	\| \|ext/standard/tests/strings/wordwrap_variation3.phpt \| empty section\|	+
-	\| \| tests/classes/arrayobject_001.phpt \| empty section\|	+
-	\| \|tests/lang/bug35382.phpt \| FILEEOF\|	+
-	\| \|tests/lang/comments2.phpt\| FILEEOF\|	+
-	\| \|tests/run-test/test010.phpt \| STDIN \|	+
	\|0 tests bork in run-tests and do not bork in phpruntests \| \| \|		\|0 tests bork in run-tests and do not bork in phpruntests \| \| \|
	\|0 tests skip in phpruntests and do not skip in run-tests \| \| \|		\|0 tests skip in phpruntests and do not skip in run-tests \| \| \|
-	\| 3 tests skip in run-tests and do not skip in phpruntests \| \| \|	+	\|0 tests skip in run-tests and do not skip in phpruntests \| \| \|
-	\| \|ext/posix/tests/posix_ttyname_error_wrongparams.phpt \|BORKS instead, could fix by deleting empty sects \|	+
-	\| \|ext/standard/tests/file/mkdir_variation5-win32.phpt \|BORKS instead, could fix by deleting empty sects \|	+
-	\| \|ext/standard/tests/file/touch_basic-win32.phpt \| BORKS instead, could fix by deleting empty sects\|	+