Executable requirements, user acceptance testing with Fitnesse

By Robert Bravery

Elevator Pitch

Do your projects fail because they have not met requirements? When delivery pressure mounts, is testing the first thing to be dropped? Do users complain that the app does not do what they expect. I can show you how User Acceptance testing with Fitnesse is one way to address many of these issues.

Description

Most software projects fail because of a lack of communication between developers, business and users. Developers think they understand what to code, Business believe they have communicated the problem and scope correctly to the developers and users cannot use the software because it is not what they asked for nor does it solve their problem.

So how to we improve this situation and save everyone’s sanity as well as improving the bottom line. Well the answer is getting everyone involved in the process. One way is to adopt Automated Acceptance Testing. Often termed as Acceptance Test Driven Development, or referred to as ATDD.

In this talk we will look at how we can write down requirements, and then have those requirement become executable and test them against our system. In and Agile way we will be able to document requirements, test those requirements, and be in a position to produce quality, correct code. T His can all be done with business and users not needing to know any coding nor having to learn any complicated tools.