Comments on: Top 10 Tips for Agile Software Development Testing!

By: moderni obrazy

moderni obrazy — Thu, 22 Jul 2010 09:14:48 +0000

Thank you for these tips. Surely they look very good. Thumbs UP

By: Vinayak Savant

Vinayak Savant — Thu, 15 Oct 2009 11:59:41 +0000

Seems good information but not great.I don’t agree on 4th n 10th points.
I want to addd something,Test Automation Makes Sense when.

Let’s start with the tests that ideally are automated. These include:

* Regression and confirmation. Rerunning a test against a new release to ensure that behavior remains unbroken—or to confirm that a bug fix did indeed fix the underlying problem—is a perfect fit for automated testing. The business case for test automation outlined in Software Test Automation by Mark Fewster and Dorothy Graham is built around this kind of testing.

* Monkey (or random). Tests that fire large amounts or long sequences of data, transactions, or other inputs at a system in a random search for errors are easily and profitably automated

* Load, volume, and capacity. Sometimes, systems must support tremendous loads. On one project, we had to test how the system would respond to 50,000 simultaneous users, which ruled out manual testing! Two Linux systems running custom load-generating programs filled the bill.

* Performance and reliability. With the rise of Web-based systems, more and more automated testing is aimed at looking for slow or flaky behavior on Web systems.

* Structural, especially API-based unit, component, and integration. Most structural testing involves harnesses of some sort, which brings you most of the way into automation. Again, the article I wrote with Greg Kubaczkowski, “Mission Made Possible” (STQE magazine, July/Aug. 2002), provides an example.

Other tests that are well-suited for automation exist, such as the static testing of complexity and code standards compliance that I mentioned in the previous article. In general, automated tests have higher upfront costs—tools, test development, environments, and so forth—and lower costs to repeat the test.

By: Ashley

Ashley — Tue, 13 Oct 2009 11:11:00 +0000

I am really in fond of Agile Development and obviously I love this tips too.

By: Globals

Globals — Sat, 03 Oct 2009 04:30:41 +0000

all good things

By: lilikindsli

lilikindsli — Wed, 30 Sep 2009 22:48:37 +0000

namU0O I want to say – thank you for this!

By: Ray Claridge

Ray Claridge — Wed, 09 Sep 2009 18:11:43 +0000

Hi -e
I’m not saying you shouldn’t automate, I’m just saying don’t rely on it for all tasks. I’ve known testers to write automation tests, that are difficult to maintain and have no payback value in terms of cost saving. The whole point of automation is to save money, not because the tester doesn’t like running the same tests manually.

See my thoughts on the subject over on http://www.testertroubles.com/2008/12/when-to-automate.html

By: -e

-e — Wed, 09 Sep 2009 12:14:45 +0000

4 and 6 are in conflict. And 4 is the one that’s wrong. You can’t get a regression test every iteration without having automated tests. Well, you can, but you’ll be wasting a lot of time…