[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: [TSVN] Regression Testing of TSVN

From: Greg Stevenson <greg_at_magictogo.com>
Date: 2005-09-06 23:25:03 CEST

Yes, this is classic. I try to be very aware of this and still break
tests all the time. A robust set of tests will minimize this. (For
example, Locating "commit" in the main menu or submenu and issuing a
click as opposed to just clicking the nth item in a menu.) I'm sure we
can come up with a process that will be satisfactory to most. I'm loathe
to put anything else on your plate like also managing tests. I would
suggest holding failed tests until they can be checked and confirmed or
some variation like warnings vs certain failures. Likewise, people need
to be made aware that passing does not guarantee that its bug free. I'm
more concerned with cases like, copy used to work and suddenly it
doesn't. That is where this tool is useful.
--Greg

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn@gmail.com]
Sent: Tuesday, September 06, 2005 9:34 AM
To: dev@tortoisesvn.tigris.org
Subject: Re: [TSVN] Regression Testing of TSVN

Greg Stevenson wrote:

> I would be willing to create an automated test suite to run against
> the
> nightly builds. The rub here is that there are no open source tools to

> do this. Regression testing TSVN would require a functional testing
tool
> that can manipulate the UI. Go to OpensourceTesting.org, etc. and you
> will find this is not an area well served by open source. Thus I would

> probably be using TestComplete, which I prefer over any other testing
> tool for windows and have a license for. I have no problem making the
> test suite itself "open source" and available but others would have to

> buy the product if they wanted to run the suite on an ongoing basis.
The
> nightly test results could also be published as XML. Anyone who wants
> can contribute to the higher lever aspects of the test plan,
procedures,
> cases, etc. And I will become responsible for turning the test cases
> into executable scripts in a test suite.
>
> Comments???

The idea of having regression tests is very good. I see only one
problem: since I don't have the test suite and I'm the one doing most of

the changes in TSVN, those tests will fail more often than not. Because
I can't adjust the tests or write new ones myself, the tests will fail
every time I make a change in TSVN which also changes the UI a little.
And if you get too many error messages, you start to ignore them...

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Sep 6 23:25:26 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.