GreenPepper is a powerful tool that supports implementing collaboration driven methods like Behavior Driven Development or Specification By Example. Due to its smart integration into Atlassian Confluence it is still one of the best tools to evolve a living documentation system mainly if you are already using Atlassian Confluence as your Knowledge Management System. Actually this feature is exclusive for GreenPepper compared with of its competitors. Some of these like JBehave & Cucumber are very developer friendly and not really accepted by non technical experts like Business Analysts/Experts or business Testers. Even the nice reporting features provided by those tools or their extensions/plugins cannot really compete with GreenPepper.
Here are some reasons:
First the testcases are specified in Confluence. Not in the developers environment. Not in Git or SVN. This might be inadequate for the developers but it is very important for non technical experts. They can see the executable specifications anytime, anywhere and independently from any developing environment.
The comfortable editing possibilities of confluences are used to write the feature specifications and the acceptance tests too.
The test reports are directly integrated into the concerned confluence pages. Everything at one place
Normally teams using Confluence are also using Jira. In this case you have a seamless integration between your requirements and your executable specifications, or even better: your living documentation
Another great feature is that you due to confluence you may have all of your documentation types at one place: business/feature documentation (with GreenPepper Tests), technical documentation, system documentation, a.s.o.
And much more other cool features …
A good news is that GreenPepper since last year open source on GitHub. But. Yes. There is a big But.
The Team behind GreenPepper has abondonned the development since some years and they are focusing on other things.
And now the most important good news :).
Since we are using GreenPepper in some of our projects and because we did not find any really convincing alternative we (actually the testIT Team ) have decided by the end of the last year to take over the development of GreenPepper and its modules. One of the major motivations was the missing support of Confluence 5.x.x and Eclipse 4.x. In addition to that it was a good opportunity to refactor the code base and have some smart features we were missing:
Support for Confluence 5.5.x +
Integrated documentation theme
Redesign of the configuration pages based on native confluence components
Support of aliases for method and fixture names with default german translations of the keywords
Jenkins Plugin that persists the results back to confluence
Centralized definition of fixture packages to be imported
Usage of confluence persistence API instead of an own database
And much more…
We are now working on the last tuning tasks and we promise to release the new edition of GreenPepper as a fork of it very soon and may be with a new name !
But anyway open source 🙂
So keep tuned!
Note: if you want to be informed about the Successor of GreenPepper just drop us a message!