Re: Brain dump: possible 1.7 work packages

On 11.02.2010 09:20, Hans-Emil Skogh wrote:
> In an ideal world every project would have version control coupled with
> continous integration and automated tests. In reality my experience says
> this is far from the case. I don't mean that we shouldn't support a good
> feature just because a minority of the projects would benefit of it
> today, I think that the bisect feature is another good case WHY you
> should have automated tests.

Sure, but reality is different: most companies don't even use version
control, and those who do don't have a simple build script.

> > Standard workflow an iteration:
> > (1) manually track test results, pick next revision to test
> > (2) delete old working copy (or cleanup existing one)
> > (3) c/o new working copy (or update to revision)
> > (4) run build
> > (5) test
> Hmm... I don't see how you can delete the working copy. You would need
> to modify it (by adding the new test that tests the changed behaviour)
> before bisecting it. Otherwise it's just a case of someone not running
> the tests before committing, and that is (hopefully) more easily solved
> by adding the tests to the build step, or pre-commit step.

Wouldn't that be a new 'feature' that CVS had: 'clean copy'. I.e.,
update to a revision and have the working copy match *exactly* that
revision. SVN currently merges when updating to a specific revision
which keeps the local modifications.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2446805
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].