InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

GreenPepper aims to Improve Collaborative Testing

Posted by Deborah Hartmann Preuss on Mar 05, 2007

Sections
Process & Practices,
Development
Topics
Artifacts & Tools ,
Agile ,
Agile Techniques
Tags
Fit / Fitnesse ,
Testing ,
TDD
Pyxis Technologies officially launched their testing product GreenPepper last July, at Agile2006.  Expanding on the kind of features offered by FitNesse, it is a platform intended to improve collaboration between business experts and software developers. Now, having taken the time to respond to feedback, Pyxis is offering a more complete product with their GreenPepper 1.1 Release.
We took the last 6 months to enhance the product based on comments, create the documentation, create an eclipse plugin to ease development, create a maven plugin, review our marketing message, etc. We released version 1.1 at the end of January. The next version is planned for the end of April and contains further polishing but also includes support for the .NET platform.
GreenPepper allows Agile teams to collaboratively write executable specifications, by enabling Story Driven Development across the team. One of the difficulties novices experience when doing this with Fitnesse is: how to organise their stories and tests. With GreenPepper, tracing requirements (stories) to executable specification documents (pages) is facilitated, allowing developers to focus more on the software and less on the requirements tool.  GreenPepper promises to deliver "optimal investment in documentation by easily turning it into executable tests."

One of the guiding principles of this product is the idea Ron Jeffries spoke about in his InfoQ interview: Running Tested Features
Our product allows teams to effectively implement the Agile principle of Working Software as the primary measure of progression and to easily track running tested features during iterations. For more details on the running tested features metric, have a look at Ron Jeffries' original article.
The commercial edition of GreenPepper offers tooling built on top of Atlassian Confluence, Atlassian Jira, Eclipse and Maven.



There are both free and commercial versions, and pricing for the GreenPepper Server is tiered, in four editions that allow for a different number of named users. Currently, GreenPepper supports applications developed in Java or Ruby. Pyxis invites continued feedback on their product, in order to create a toolset that reflects the needs of the development and business communities.
link typo by Matt Spendlove Posted
  1. Back to top

    link typo

    by Matt Spendlove

    FYI - your link is bust to Green Pepper, has a typo... Should be :

    www.greenpeppersoftware.com/

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.