Right now, I'm creating simple regression tests that we can run after
every patch/version update. And, you're right - there isn't much of a
chance of these tests failing. We're automating this because it's
boring to do manually.
As far as the quick win, I have already completed quite a few
This conversation tends to be quite unproductive when it becomes is
or isn't test automation useful. It's a lot like Are books useful?
Books won't solve any problems on their own. There are plenty of
problems that books will not help with a bit. There are /some/
problems where /the right/ books
Hi George,
I appreciate the plugs for the book from Paul and Chris (and it's the
contributions from them and other folks like them that make the book
helpful!)
Does your team do any regression testing? If so, and if you don't have these
tests automated, who is doing the manual regression tests?
Good tips, Chuck. We currently have SharePoint (although we're
getting rid of it in the future...not sure why, though), so I'll need
to figure out how to link the HTML report from there. I'll look into
this...thanks!
On Apr 6, 1:21 pm, Chuck van der Linden sqa...@gmail.com wrote:
write the
You could always define your tests in a wiki and update the results
directly to there!
A good way to get everyone involved in what you are running and what
the results are.
Some more info on my blog: http://watirmelon.wordpress.com/category/wiki/
(shameless plug!)
Cheers,
Alister Scott
Brisbane,
