ok, folks -- after a long development period, we are very,
very close
to having automated patch testing working on drupal.org!
here's the current status: the platform which sends and
receives file
tests and results is installed and running on drupal.org.
files are
being sent to the testbed server for testing, but the
results are not
being returned or displayed on drupal.org yet.
this interim phase will allow us to work out any remaining
kinks in
the file testing platform.
so, in short, here's what you need to know to help!
1. only patches against drupal core (4.7.x, 5.x, and 6.x)
are being
processed for testing at this time. contrib patches may or
may not be
added at a later time
2. in order for a patch to be sent for testing, it must meet
the
following 2 criteria:
a. the filename ends in .patch or .diff
b. the issue the file is attached to has a status of
'code needs
review' or 'ready to be committed'
again, for now, no results will be returned or displayed on
drupal.org.
for those interested in the nuts and bolts of this system,
and/or
who'd like to help with it's further
development/implementation:
the platform for sending/receiving files: htt
p://drupal.org/project/project_issue_file_test
the site that handles the automated testing: http://testing.drupal.org/
|
apartmentl