PHP-QAT
|
|
The PHP/QA Team is a small group of developers
whose primary goal is to support the PHP core developers by providing
them with timely quality assurance.
|
Projects & Goals
|
|
Find more information about PHP/QA Team's current
projects and future goals.
|
Release Candidates
|
|
What are release candidates and how you can help us testing them.
|
Contact Information
|
Questions about the PHP-QAT should be sent to the
PHP/QAT Mailing List
Bug Reports should be submitted to the official PHP bug list
(http://bugs.php.net)
All other questions should be directed to the appropriate
PHP mailing list.
|
 |
|
|
TestFest (May 2008)
|
|
| |
|
The TestFest is an event that aims at improving the
code coverage of the
test suite for the PHP language
itself. As part of this event, local User Groups (UG) are invited to
join the TestFest. These UGs can meet physically or come together
virtually. The point however is that people network to learn together.
Aside from being an opportunity for all of you to make friends with
like minded people in your (virtual) community, it also will hopefully
reduce the work load for the PHP.net mentors. All it takes is someone
to organize a UG to spearhead the event and to get others involved in
writing phpt tests. The submissions will
then be reviewed by members of php.net before getting included in the
official test suite.
|
 |
Participating Users Group
Please check the PHP.net wiki page for
details.
Frequently Asked Questions
Why should I care?
Aside from having to opportunity to help in improving the language
itself, we will also raffle off 10
elePHPants to
submitters. Every submission (test) that is considered helpful
receives one entry into the raffle. Furthermore, people that show they
are capable of writing tests entirely on their own may be given
official PHP.net accounts with direct commit access to cvs.php.net and
an @php.net email address. As a result participants should also read
over the general guidelines
for getting CVS access.
When will the TestFest take place?
UGs are free to pick any timeframe in May 2008. Each local TestFest
can last a day, a week or any other timeframe.
Why is the timeframe so short? What if June would be a better date?
We want to ensure that we have mentors ready and available to answer
questions. In order to get some sort of commitment from mentors we
cannot make this timeframe indefinitely long. That being said we
might hold future TestFests. Also people are of course invited to
join the QA team any time of year.
How will local organizers be assisted?
We will make a list of areas available of areas of PHP that need
more testing. Along with that list we will provide contact
information for mentors. The mentors will also review the submissions
later on. Ideally questions regarding the testing framework itself
will be answered by local organizers. Please check the
wiki to get details on
the available mentors and focus areas.
I want to organize an event, but there is nobody here that
knows how to write tests for PHP. What can I do?
First look at the documentation on how to
write phpt tests. It's actually not that hard. If you still need
help feel free to contact the
QA mailinglist.
Where are tests submitted to?
We have implemented a simple front-end that allows people to upload
their phpt files. People can register themselves and the create a tak (new test) and upload
their files as attachments. More details can be found here
Submitters are asked to follow the phpt coding standards.
I volunteered to be a mentor, how do I review tests?
Just register with the test tracking tool and
mail the
QA mailinglist to ask for admin authority. Admin authority will be granted
to those who already have PHP commit rights. When you have admin authority you can log
into the test tracking system and assign tests to yourself. Simply review the test, if it's good
then commit it, if not then either fix it or return it to the contributor explaining why you
are unable to commit.
What version of PHP should be used?
We prefer that the tests are made for 5.3/HEAD. You can grab a build
of 5.3 at the snaps page. Source
code and Windows builds are available. Possibly there will be a
release candidate of PHP 5.3 available as well. If requiring PHP
5.3/HEAD is an issue for your UG, please let us know so that we can
see how your UG can still participate.
How are submissions reviewed? How do I get feedback?
Mentors will have access to all the submissions and will review
submissions at their own pace in their given area of expertise. We
hope this will be done in a timely manner, but please understand
that we cannot give any guarantees, especially if the event turns out
to be as successful as we hope. Submittors will be able to see who
is reviewing their submission as well as when their submission has
been processed. If the submission led to a commit the
interface will show any difference that might exist between the
submission and the final committed version. Furthermore the mentor
might provide some individual commentary.
How do I join? How do I get more information?
We are still in the process of building the necessary infrastructure.
Hopefully before the end of April we will have everything in place.
Until then please contact the
QA mailinglist if you are interested in participating or if
you have any questions. Alternatively you can join #php.pecl on
Efnet or the #phptestfest channel on Freenode IRC server. There
should usually be someone around to help.
Do you also provide a smaller version of the logo?
Yes here you go (scale as needed):
|
|
|
