Shell scripts to automate trac ticket testing

[Denis-de-Bernardy]

I've been moving/editing tickets around in the past couple of weeks to trim the 2.8 todo list.

There are only so many patches left as needs-testing:

​http://core.trac.wordpress.org/report/16

And quite a few commit candidates:

​http://core.trac.wordpress.org/report/9

Very few tickets remain in 2.8 without an actual patch -- only those that seemed major enough to require some kind of patch before 2.8 gets shipped.

In order to speed up testing, I've developed a few shell scripts. They'd be good additions to the main wiki page.

Usage (always in a wp folder):

# svn revert and cleanup
wpreset

# apply http://core.trac.wordpress.org/attachment/ticket/123/456.diff
wppatch http://core.trac.wordpress.org/attachment/ticket/123/456.diff

# reset and apply http://core.trac.wordpress.org/attachment/ticket/123/456.diff
wptest http://core.trac.wordpress.org/attachment/ticket/123/456.diff

In case it's useful to anyone...

[Denis-de-Bernardy]

Only 18 tickets, as I write, in 2.8 that actually need a patch:

​http://core.trac.wordpress.org/query?status=assigned&status=new&status=reopened&group=severity&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&milestone=2.8&keywords=%7Eneeds-patch

Maybe we'll release end of May after all... :-)

[Denis-de-Bernardy]

2.7.2 milestone can be closed, too... all of the remaining tickets have been moved to 2.8 or Future depending on severity and patch presence.

[filosofo]

Thanks; I think I'll use wppatch.

I just need a shell script that posts "itching to close as invalid" to all open tickets, and I'll be set. :)

[Denis-de-Bernardy]

I've given a slight update to wpreset since. Will create a page on my site in a week or so with their final versions.