program selection system

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

The gap between approachability (by a non-programmer) and ability (of the tools). There’s a horde of developer-oriented testing tools that are excellent for test automation but those tools aren’t too suitable for shared use between developers, non-programming testers and especially customers. On the other hand, there’s a bunch of tools that aim to be fool-proof but they frequently fall short on the power aspect - you can’t do much with those tools.

ii) What do you hope to contribute?

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

Many tools are big and try to do everything (interact with the SUT, have fancy user interface for creating test cases, integration to CI, …). I see that as a problem because implementing such tools is a big task, it’s hard (or impossible) to get all features done so that they’d work well in different situations, and then if you are able to create a wonderful tool e.g. for web testing you can’t (at least easily) use it for anything else.

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

Finding a way to integrate the traditional testing roles into an agile process while maintaining the values of a single point of truth for your code and tests and the ability to refactor and regression test in the future after the project has completed.

ii) What do you hope to contribute?

I can share some experiences from previous projects where the above caused us some real issues and discuss some approaches we are trialling on our current projects

iii) What do you hope to get?

i) What do you see as the biggest issue for Functional Testing Tools on Agile projects? How can we create tools that are easy-to-use but powerful, attractive to the “right” users, and whose cost of using them is low?

ii) What do you hope to contribute? I’ve got experience using test automation with a variety of teams over the past 20 years.

I think there’s some leverage to be had in formal specification approaches that tools haven’t really supported yet.

I’ve got experience implementing compilers and other such tools, that might be applicable to new tools.

i) What do you see as the biggest issue for Functional Testing Tools on Agile projects? The biggest issue of functional testing tools is that they support old-fashioned testing approach where the values are to :
- use tests for finding defects
- test within dedicated testing campaigns
- specialize testing jobs

Modern functional test automation tools should support modern testing values needed for agile development:
- use tests to specify what the software should do in a test-first fashion
- continuously test the software

What do you see as the biggest issue for Functional Testing Tools on Agile Projects

Is there is a need to have a functional test tool on non UI components such as web services, or various APIs that would serve to both customers, developers, quality engineers and testers? Should there be one tool that fits all needs or should there be multiple? Are there tools that are easily re factored depending on the implementation of web services - should there be? I always find myself writing the frameworks to do that myself.

What do you hope to contribute?

i) What do you see as the biggest issue for Functional Testing Tools on Agile projects?
The ability to support a “Narrative Testing” (similar to Story Test Driven) approach — direct manipulation of the AUT UI using customer understandable and business domain grounded test language.

ii) What do you hope to contribute?
* Facilitate discussion oriented around the Narrative Testing approach.
* Demonstrate the open source StoryTestIQ Narrative Testing framework (I’m a creator and developer of this tool).

iii) What do you hope to get?

i) What do you see as the biggest issue for Functional Testing Tools on Agile projects? - Having tools that are easy to use for everyone to create and manage tests. ii) What do you hope to contribute? - Discuss what possibilities just open sourced ATDD tool Robot framework gives for ATDD testing. iii) What do you hope to get? - Discuss with people where FTT is going in agile projects.

i) What do you see as the biggest issue for Functional Testing Tools on Agile projects?
The efficient inclusion of the mind of a tester.

ii) What do you hope to contribute?
Imagination / intuition. Questions / experience.

iii) What do you hope to get?
An extension to my current imaginings. Perspective.

Automated functional testing has both: - lots of charm especially for business stakeholders - many many problems in doing it right

Some of the common problems: - Providing a realistic test environment for todays complex system is non-trivial and beyond what most testers can do. There needs to be massive involvement from software development and deployment experts.