The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.As discussed before, it would be very useful if an API were developed to allow external modules, such as coder, to perform additional review items. The API would need both server and client side hooks.
Client
The module would need to define some sort of info hook that would tell PIFR how to run it, where to get results from.
Server
The server needs to provide hooks for the external modules to store and retrieve the results for a particular test.
Transfer
The XML-RPC layer needs to support the transfer of arbitrary data.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 522858-abstract-review.patch | 163.75 KB | boombatower |
| #7 | 522858-abstract-review.patch | 162 KB | boombatower |
| #6 | 522858-abstract-review.patch | 110.26 KB | boombatower |
| #5 | 522858-abstract-review.patch | 60.15 KB | boombatower |
| #4 | 522858-abstract-review.patch | 53.48 KB | boombatower |
Comments
Comment #1
boombatower commentedInstead of just adding an API for external module reviews PIFR should implement the SimpleTest review through the API as well.
Comment #2
boombatower commentedFairly far along. (end of night)
Comment #3
boombatower commentedCompleted client review process revamp (classes).
Comment #4
boombatower commentedDrupal 6 testing is now supported by review backend.
Comment #5
boombatower commentedUpdate a few remaining areas, including pifr_client.php so that you can just pick a few types.
Comment #6
boombatower commentedFinalizing things and implementing on server side.
Comment #7
boombatower commentedRe-factored some things.
Client confirmation with multiple environments seems to work well..except test doesn't get marked as result.
Last area to fix is regular pifr.next() (non-confirmation) test information array generation.
Comment #8
boombatower commentedCommitting this..a few rough edges, but overall good.