fit

Automated Functional Testing on the TransCanada Alberta Gas Accounting Program of Projects

room: Conference E, M — time: Thursday 16:00-17:30
Average Rating: -

This experience report will talk to Automated Functional Testing on the TransCanada Pipelines Alberta Gas Accounting program of projects. We feel that the story around Functional Testing is a compelling one to an audience of agile practitioners: 621 FIT Functional Tests scripts produced in the last module (over 23 months), Business is sold on the benefits of the approach to Automated Functional Testing; All future projects include automated functional testing; Business Analysts (not Developers, not Quality Assurance) write the FIT test scripts.

Other highlights:

Test Driven Development for Data Management projects using FIT4Data

room: Sheraton Hall B, LC — time: Friday 08:30-10:00
Average Rating: -

The tools and techniques needed to do Test Driven Development are extremely well documented for Object Oriented languages, but how do we do TDD data management and business intelligence projects using 4th generation ETL languages like Ab Initio?

In this talk, I will show you how to do TDD when transforming data is the sole aim of the project. The talk will be divided into two parts. First, the theory of TDD in data management applications and, second, the application of the practices using FIT4Data.

Style and Taste in Writing FIT Documents

room: Norfolk, M — time: Friday 08:30-10:00
Average Rating: -

FIT is a framework that comes in various guises (Fit, Fitnesse, Fitlibrary), and can be used in different ways. The core principle behind writing FIT documents is to promote better communication between the stakeholders of a system. In principle, using FIT is a good thing, but in practice we find that some teams struggle to use FIT documents effectively. In this tutorial we will introduce some concrete examples of poor FIT style, and get the participants to refactor these examples to improve them.

By attending this session, you will:

FitNesse Demo

Average Rating: -

FitNesse out of the box does not seem to work for teams! In this demo I’ll show how to set up FitNesse so that development teams can do the following:

  • Organize their Stories, Acceptance Criteria and Acceptance Test better
  • Create different levels of test suites to give feedback at different levels
  • Version control the FitNesse wiki with their source code
  • Inline editing of their FitNesse pages, with out having to worry about Wiki syntax
  • Integrate FitNesse with their builds, so that they can run their acceptance tests as part of their Continuous Integration loops
Syndicate content