There are plenty of ways you can contribute to Jubula, as well as to the community itself. Just contact us via the button on the right with your ideas, suggestions and wishes.
The easiest way is to send us a link to content you’ve produced about testing with Jubula – a blog entry, for example. We’ll check the content then post the link in our resources for other users to benefit from.
Maybe you’ve designed a beautiful module for your tests, or found an ingenious way to automate a workflow. Send us a short mail with the details, and we’ll contact you to discuss how to get your example integrated into our resources.
How are you testing with Jubula? What effects has testing had on your quality and on your development process? What did you learn along the way? Send us your story and whether you agree with its publication online – and receive a set of planning poker as a thank you!
Of course, one of the best ways to contribute is with code. If you’ve done some development work on Jubula code, then you can (and should!) enter a patch to have it added to our builds so that everyone can benefit from it. Simply enter an enhancement in the Jubula Bugzilla with your patch attached – and if you don’t know what that entails, then contact us for assistance!
If you'd prefer the Jubula team to write your extension for you, or if there's a particular feature you'd like implemented, or a bug you want to be fixed with the highest priority (including a patch release for your team), then you can sponsor the development. We'll work with you on your requirements, make suggestions, and calculate the effort and the sponsorship amount. Contact us for more information.