Re: Breaking merge_tests.py into 3 parts

2010-05-27 Thread Paul Burba
On Wed, May 26, 2010 at 3:45 PM, Stefan Sperling wrote: > On Wed, May 26, 2010 at 01:42:38PM -0500, Hyrum K. Wright wrote: >> The common complaint is that by renumbering the tests, we break historical >> comments such as "fixes bar_test FOO".  But those comments are often >> versioned, so a little

Re: Breaking merge_tests.py into 3 parts

2010-05-26 Thread Stefan Sperling
On Wed, May 26, 2010 at 01:42:38PM -0500, Hyrum K. Wright wrote: > The common complaint is that by renumbering the tests, we break historical > comments such as "fixes bar_test FOO". But those comments are often > versioned, so a little archaeology can divine the answer. I don't think > such conc

Re: Breaking merge_tests.py into 3 parts

2010-05-26 Thread C. Michael Pilato
Paul Burba wrote: > Frequently I want to test just the subset of merge_tests.py related to > --reintegrate as a quick sanity check during development for that > feature. To make this a bit easier I'd like to break merge_tests.py > into three separate tests: > > 1) merge_reintegrate_tests.py - A

Re: Breaking merge_tests.py into 3 parts

2010-05-26 Thread Hyrum K. Wright
On Wed, May 26, 2010 at 1:17 PM, Paul Burba wrote: > Frequently I want to test just the subset of merge_tests.py related to > --reintegrate as a quick sanity check during development for that > feature. To make this a bit easier I'd like to break merge_tests.py > into three separate tests: > >