Testers could goto testing.drupal.org press a button and have a test drupal site setup with the patch they want to test.

The instance would only be accessible to the user who created it to prevent XSS attacks. Once the user leaves or after timeout of inactivity the site would be destroyed.

I made an initial stab at this some time ago and stopped after finding: #329548: Clean up testing.drupal.org server

Comments

boombatower’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev

Waiting for 2.x.

boombatower’s picture

Talk to sun (tha_sun) about using demo module.

boombatower’s picture

Status: Postponed » Active

Workflow:

Drupal.org
 * file patch
 * patch is queued and has test ID assigned
 * "try now" link is visible

link -> qa.drupal.org (redirect) -> dedicated demo client

demo client 
 * start batch process
 * request test information
 * perform setup routines
 * auto-login
 * schedule site for deletion after one hour

What is needed:

* minimal module on qa.drupal.org
  * perform redirect
  * provide test information (simple wrapper around pifr API)
* minimal module on client
  * instead of requesting tests on cron run it will provide a page to trigger
  * wrap pifr client runner with batch API
  * setup demo module
  * auto login

possible module name: pifr_usability

boombatower’s picture

Project: Project Issue File Review » PIFR Demo
Version: 6.x-2.x-dev »
boombatower’s picture

boombatower’s picture

Version: » 6.x-1.x-dev
Assigned: Unassigned » boombatower
Status: Active » Needs review
StatusFileSize
new76.15 KB

Virtually done, just need auto-login.

boombatower’s picture

Status: Needs review » Fixed

Complete.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.