Marcus Martina explains in this blog post how to integrate FitNesse tests into the Jenkins continuous integration system. FitNesse is an open source testing framework that aims to implement integration testing in a collaborative way. It is easy to integrate FitNesse tests automatically with Maven and Jenkins. The post provides the code necessary to do this integration. It also identifies the different Maven plugins that are necessary to achieve this goal and recommends to trigger the execution of the integration tests in an individual build step.
This blog post gives a short tutorial on how to deal with the several issues that prevent the use of functional testing tools (e.g. Fitnesse) with a Silverlight project out of the box. A recent experience with a Silverlight application showed that the approach produces a little overhead, but that this overhead is negligible compared to the benefits of automated functional testing involving the ViewModels.
This article presents GivWenZen. GivWenZen allows a user to use the BDD Given When Then vocabulary and plain text sentences to help a team get the words right and create a ubiquitous language to describe and test a business domain.
This book is primarily aimed at .NET developers interested in starting with TDD and those who already practice unit testing and want to move beyond that into development driven by acceptance testing.
FitNesse is a test framework that allows testers, developers and customers to collaborate to create test cases on a wiki. Teams can take examples of desired software behavior and turn them into automated tests, integrated with narrative requirements documentation. FitNesse runs its own wiki web server. It’s possible to test applications written in Java, .Net, Ruby, Python, C, and PHP using FitNesse.
This video shows how Selenium, integrated into a FitNesse framework can extend 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.