Published August 19th, 2010 Under Uncategorized | Leave a Comment
FitNesse, BDD/ATDD based tools (like Cucumber) and various keywords based tools each have their followers when it comes to automated testing at the system or acceptance level. But few have tried each type and many are wondering which one best suits their organisation, project or product. The concept of Domain Specific Test Languages (DSTL) is a great improvement over record & playback based approaches to automated testing and promises easy to read & write tests in the language of the business and low maintenance effort. This interactive session first presents DSTLs and how they fit in an Agile process & team and then considers how each type of tool supports this effective approach to automated testing. The tools will be compared using one non-trivial test case, to illustrate some of their strengths and limitations
Tools like FitNesse allows test automation to happen quickly and broadly. However, many companies can’t support it in their infrastructure. Dawn Cannan got around this problem by helping create SeleNesse, a Selenium-FitNesse plugin. She also paired with developers in the Java space and the .NET space to bring this plugin to both domains.
This demonstration describes how Selenium integrated with FitNesse extends an organization’s ability to create more automated test cases without the need for Selenium programming while expanding the ability to test across all popular browsers. With FitNesse, QA managers, Product Managers and Testers can easily create wiki-based test stories that execute across multiple browsers.
Video producer: San Francisco Selenium Meetup Group
* Selenium Home Page
* FitNesse Home Page
* FitNesse: A Tester’s Perspective
* Functional testing for Web applications
* In pursuit of code quality: Programmatic testing with Selenium and TestNG
* Data-Driven Testing with FitNesse
* Test Driven .NET Development With FitNesse: Second Edition
* Functional Testing Tools Directory
FitNesse and FIT are arguably the most popular framework for automated agile acceptance testing, due to its unique power to serve as team collaboration medium, system documentation and test automation tool in one simple open-source solution. In this interactive clinic, David Evans and Gojko Adzic discuss some of the common pitfalls faced by testers and teams in getting to grips with Fitnesse. We will show examples of good and bad acceptance tests, illustrating how different styles of fixtures lend themselves to different types of tests. We also highlight some of the features of Fitnesse that allow you to keep your tests expressive, useful and easy to maintain.
Test-Driven Development (TDD) and Behaviour-Driven Development (BDD) are powerful techniques, helping developers write better designed, more maintainable and more reliable code, and stay focused on the real user requirements. But how does the rest of the team fit in to the picture? In this talk, John Smart, creator of the Java Power Tools Bootcamp, looks at how BDD techniques, and tools such as easyb and FitNesse, can also act as drivers for the overall development process, and also as communication tools, giving testers and end-users clear and unambiguous feedback on what is being developed and where it is at in terms of delivery and schedule.
Agile communities consider stories “done” when the acceptance tests (also called story tests) are shown to the customer. Originally, this was a manual process, but in recent years, several frameworks have been created to automate this process, providing acceptance testing all the benefits of automated unit testing. One of the most popular of these if called FIT, created by Ward Cunningham.
This tutorial presents the usage of scenarios to approach tests from different levels of abstraction.
A tutorial on the data types in Slim tables.
A quick demonstration of the comparison operators used in Slim Tables.
In this video Uncle Bob shows how he set up Hudson to be the continuous integration server for FitNesse.keep looking »