PHP Wiki qa

qa:credits

2008-05-02T12:42:30+00:00

	current
Line 1:	Line 1:
	+	==== Crediting test authors ====
	+	People who don't have karma should use the --CREDITS-- section, for example:
	+
	+	<code>
	+	---CREDITS---
	+	Joe Testwriter jt@gmail.com
	+	# testfest london 2008-05-08
	+	</code>
	+

qa:organisers

2009-05-07T13:36:23+00:00

qa:phptlessonslearned

2008-05-18T01:43:39+00:00

1211073881		current
Line 108:		Line 108:
	will generate variation tests. There will be one for each of the functions argument and an empty test. The numbered variations will iterate over an array of different data types and pass them as an argument, these tests are very useful! Again all that needs doing with these is changing the title (in the -- TEST -- section), add a comment explaining what the test is doing and filling out the EXPECTF section.		will generate variation tests. There will be one for each of the functions argument and an empty test. The numbered variations will iterate over an array of different data types and pass them as an argument, these tests are very useful! Again all that needs doing with these is changing the title (in the -- TEST -- section), add a comment explaining what the test is doing and filling out the EXPECTF section.
	With the blank variation test is a template for any other variation tests the function needs.		With the blank variation test is a template for any other variation tests the function needs.
		+
		+	===== 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 [[http://testfest.php.net/\|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
		+
		+

qa:runtests

2009-07-25T11:20:31+00:00

1248520366		current
Line 15:		Line 15:
	* [[http://wiki.php.net/qa/runtests/QA\|QA status]]		* [[http://wiki.php.net/qa/runtests/QA\|QA status]]
	Compatibility with the old version and checking that the parallel code gives the same results as sequential code are both important. The most recent state of testing is given here.		Compatibility with the old version and checking that the parallel code gives the same results as sequential code are both important. The most recent state of testing is given here.
-	* [[http://wiki.php.net/qa/runtests/faq\|FAQs]]	+	* [[http://wiki.php.net/qa/runtests/faq\|FAQs]]
-		+
-		+
-		+
-		+
-		+
-		+
-		+
-		+
-		+
-		+
-		+
-		+
-		+
-		+
-	This page [[wiki.php.net/qa/runtests/configuration]] (the address is a bit screwy, but I won't change it as I've posted a link to it) has a list of currently implemented options, and whether we will re-implement or not. Yes means we will - blank means not decided, have asked for input on QA list.	+
-		+
-	==== Additional Options ====	+
-		+
-	* Run tests in parallel?	+
-	* XML or CSV or TXT (to replace HTML)	+
-	* Option specify arguments to valgrind	+

qa:screencasts

2009-05-10T22:41:06+00:00

	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]]

qa:svnnote

2009-05-26T20:02:52+00:00

	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

qa:testcoverage

2008-05-02T15:37:42+00:00

1209585206		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
		+
		+
		+
		+
		+

qa:testfest

2009-06-05T20:21:47+00:00

1245321893		current
Line 9:		Line 9:
	\| Belgium \| May 9 \| SQlite3, ldap \| Felix de Vleigher \| felixdv@php.net \|		\| Belgium \| May 9 \| SQlite3, ldap \| Felix de Vleigher \| felixdv@php.net \|
	\| Brazil (SP ) \| June 20 \| \| \| rdohms@gmail.com \|		\| Brazil (SP ) \| June 20 \| \| \| rdohms@gmail.com \|
-	\| Brazil (Rio) \| May 30 \| \| Igor Feghali \| ifeghali@php.net \|	+	\| Brazil (Rio) \| July 3 \| \| Igor Feghali \| ifeghali@php.net \|
	\| Brazil(BR) \| June 23 \| \| Er Galvao Abbott \| galvao@galvao.eti.br \|		\| Brazil(BR) \| June 23 \| \| Er Galvao Abbott \| galvao@galvao.eti.br \|
	\| Brazil(SC) \| \| \| \| silvano@php.net \|		\| Brazil(SC) \| \| \| \| silvano@php.net \|

qa:testfestmentors

2008-04-02T12:49:05+00:00

		current
Line 1:		Line 1:
		+	table containing mentors and areas here they are willing to help out goes here

qa:testfesttalk

2009-04-27T16:47:57+00:00

1240850877		current
Line 25:		Line 25:
	* re2c		* re2c
	* Bison (before php 5.2)		* Bison (before php 5.2)
-	* lcov	+	* lcov / ggcov

qa:uploading

2009-04-01T20:31:59+00:00

1236694259		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.
		+
		+
		+
		+
		+
		+
		+

qa:whattotest

2008-05-07T13:05:35+00:00

1210165535		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>

1245321893		current
Line 9:		Line 9:
	\| Belgium \| May 9 \| SQlite3, ldap \| Felix de Vleigher \| felixdv@php.net \|		\| Belgium \| May 9 \| SQlite3, ldap \| Felix de Vleigher \| felixdv@php.net \|
	\| Brazil (SP ) \| June 20 \| \| \| rdohms@gmail.com \|		\| Brazil (SP ) \| June 20 \| \| \| rdohms@gmail.com \|
-	\| Brazil (Rio) \| May 30 \| \| Igor Feghali \| ifeghali@php.net \|	+	\| Brazil (Rio) \| July 3 \| \| Igor Feghali \| ifeghali@php.net \|
	\| Brazil(BR) \| June 23 \| \| Er Galvao Abbott \| galvao@galvao.eti.br \|		\| Brazil(BR) \| June 23 \| \| Er Galvao Abbott \| galvao@galvao.eti.br \|
	\| Brazil(SC) \| \| \| \| silvano@php.net \|		\| Brazil(SC) \| \| \| \| silvano@php.net \|

1241700449		current
Line 1:		Line 1:
	==== Suggestions and checklist ====		==== Suggestions and checklist ====
		+	===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
		+	* Make sure that the location you choose has network connection (wireless/ethernet)
	* Check that a mentor will be able to assist with your event		* Check that a mentor will be able to assist with your event
	* Publish details of your event somewhere (Usergroup wiki, homepage, blog, etc.)		* Publish details of your event somewhere (Usergroup wiki, homepage, blog, etc.)
		+	* Limit the numbers if you don't have a reasonable ratio of mentors to attendees (suggested max 1:4)
	* Anounce your event:		* Anounce your event:
-	** Local usergroup news feed	+	* Local usergroup news feed
-	** Calendar entry on php.net/cal	+	* Calendar entry on php.net/cal
-	** Announcement to php-qa@lists.php.net	+	* Announcement to php-qa@lists.php.net
-	** Any other blogs or relevant places you can think of	+	* Any other blogs or relevant places you can think of
-	* After a short while, check that your event has been approved on php.net/cal and is listed on http://wiki.php.net/qa/testfest	+	* After a short while, check that your event has been approved on http://php.net/cal and is listed on http://wiki.php.net/qa/testfest
		+
		+	===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
	* Get a list of names of attendees (and email addresses) in advance		* Get a list of names of attendees (and email addresses) in advance
	* Grant access to SVN in advance (testfest.php.net/testtfest.php)		* Grant access to SVN in advance (testfest.php.net/testtfest.php)
-	* Limit the numbers if you don't have a reasonable ratio of mentors to attendees (suggested max 1:4)
	* Mail attendees the day before to remind them to bring laptops (and possibly power supply and ethernet cable)		* Mail attendees the day before to remind them to bring laptops (and possibly power supply and ethernet cable)
	* Ask attendees (with any other OS than Windows) to try and download and compile PHP in advance (to check that they have a build env't)		* Ask attendees (with any other OS than Windows) to try and download and compile PHP in advance (to check that they have a build env't)
-	* Make sure that the location has network connection (wireless/ethernet)
	* Pick an area (extension) to test in advance and let the attendees know so that they can do some preparation.		* Pick an area (extension) to test in advance and let the attendees know so that they can do some preparation.
	* Mail the QA list to say what extension you are looking at so that you can co-ordinate with other groups if they want to work in the same area		* Mail the QA list to say what extension you are looking at so that you can co-ordinate with other groups if they want to work in the same area
	* Work out in advance which test cases are missing and have a list of then ready for people to work on		* Work out in advance which test cases are missing and have a list of then ready for people to work on
	* If you pick something that has pre-reqs (eg database, libraries) prepare some samples and make sure that people know to install the pre-reqs.		* If you pick something that has pre-reqs (eg database, libraries) prepare some samples and make sure that people know to install the pre-reqs.
		+
		+	===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.
	* Find a local source of beer for after the event		* Find a local source of beer for after the event
-		+
-		+