program selection system

The biggest issue I see for functional testing is maintenance. I haven’t seen a way of building functional tests that is not staggeringly costly to maintain, both in terms of cost and in time and energy spent by developers on automating them.

i) What do you see as the biggest issue for Functional Testing Tools on Agile projects?

The biggest issue I see for Functional Testing Tools for Agile projects is the lack of a good, centralized repository of information for selecting the appropriate tool for a given project/technology/customer/etc. There are many good Agile FTTs out there, both open source and proprietary, but no standard matrix of features by which one can compare and contrast the existing tools so as to identify the best tool for a particular purpose.

ii) What do you hope to contribute?

What do you see as the biggest issue for Functional Testing Tools on Agile projects? Separation from the development code and ongoing maintenance. ii) What do you hope to contribute? I can speak to my 6+ years in Gap Inc Direct moving from a standard waterfall methodology and black box testing to where we are now. I’ve lead the department through a move to Agile as well as revamping functional automation using Ruby and Watir in an enterprise environment, and potentially interesting new ideas about developer collaboration. iii) What do you hope to get?

i) What do you see as the biggest issue for Functional Testing Tools on Agile projects?

How to make tools fit the way testers approach testing, rather than forcing testers to adopt the tool’s approach.

ii) What do you hope to contribute?

Attention to how the decisions we make about testing tools affect the tester’s experience. What does each decision allow or force the tester to do? How does it help or hinder the tester in designing, executing, and interpreting tests? How does it help or hinder in understanding and satisfying stakeholders’ information needs?