what is the place of GUI testing in Agile process?
We wanted to find out if there is any recommendations from the side of Agile method where to use the GUI testing. For now, it appears that software testers need to start using GUI tests from the very beginning, even when there is only simple interfaces such as open project dialog, or logging page.
But normally, it doesn't make sense testing just standard file open dialog, so it appears that in Agile the GUI tests are necessary only when some serious GUI appears, e.g. GUI linked to some important functions?
Any ideas about using GUI testing in Agile?
Re: what is the place of GUI testing in Agile process?
How about doing something Manual/Exploratory/Ad Hoc/By the Seat of Your Pants? If you have a task, does it matter how you do it as long as you determine what is available within the GUI to test?
Automation, probably too early and time consuming, but maybe you can generate some guidelines on what needs to be checked and/or tested?
Nothing learns better than experience.
"So as I struggle with this issue I am confronted with the reality that noting is perfect."
Now wasting blog space at QAForums Blogs - The Lookout