[wp-unit-tests] [WordPress Unit Tests] #124: "Try" functionality

[WordPress Trac]

#124: "Try" functionality
----------------------------+------------------
 Reporter:  kurtpayne       |       Owner:
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:
Component:  Test Framework  |  Resolution:
 Keywords:                  |
----------------------------+------------------

Comment (by kurtpayne):

 Replying to [comment:2 nbachiyski]:
 > What's the workflow you envision? I want to test a patch from a ticket,
 but I already have a bunch of local modifications?
 This does a clean svn fetch of the unit tests into a temp folder and uses
 a separate database.  Your local modifications shouldn't be a problem.

 > It would be even more awesome if we hook this to the Jenkins install
 you're running. Choose a patch and just say: "try it on the test server".

 I can work on this.

 > This way I won't need to do anything locally. And on the test server we
 can always keep a clean copy ready.

 I think I'd always want to do a fresh checkout.  If a patch is poisoned
 and does local file writes, then the next time the "try" script is run,
 the checkout won't be clean.

-- 
Ticket URL: <http://unit-test.trac.wordpress.org/ticket/124#comment:3>
WordPress Unit Tests <http://unit-test.trac.wordpress.org>
My example project