Skip to main content
This is a pre-production deployment of Warehouse. Changes made here affect the production instance of PyPI (
Help us improve Python packaging - Donate today!

JIRA data source for corejet.testrunner

Project Description

CoreJet test runner JIRA integration

This package provides a requirements catalogue source for corejet.testrunner that can fetch requirements from JIRA.

To use it, make sure it is installed in the working set of the testrunner. If using Buildout, you can do this with:

recipe = corejet.testrunner
eggs =
    <other packages>
defaults = ['--auto-color', '--auto-progress']

Here is an example command line invocation:

./bin/test -s corejet.core --corejet="jira,url=,username=corejet,password=secret,project=Acme Corp,filter=10151,pointsField=10060,epicField=10061,acceptanceCriteriaField=10088"

The --corejet option must start with jira, followed by a set of parameters that indicate how to connect to JIRA. The parameters are:

URL of JIRA instance
username to use to connect
password to use to connect
Name of project
Numeric id of filter that returns stories
Numeric id of field containing story points
Numeric id of field indicating epic for a story
Numeric id of field containing acceptance criteria (scenarios)

This presumes JIRA is set up with a filter that returns all stories you want to include (e.g. return all valid issues of type Story in the project, if using GreenHopper). The various field ids describe the fields that provide story points, epic/theme (either a string or a reference to another issue), and a field with acceptance criteria.

The first two are standard GreenHopper fields. The acceptance criteria field must be added manually. It should be a plain text field containing scenarios in simple Gherkin syntax, e.g.:

Scenario: First scenario
Given a precondition
  And another precondition
When something happens
  And something else happens
Then a result is expected
  And another result is expected

Scenario: Second scenario
Given another precondition
When something else happens
Then a different result is expected

The parser is relatively forgiving, but note:

  • The parser is case-insensitive
  • Zero or more scenarios may be present
  • Scenarios must start with “Scenario: ” followed by a name
  • The “Given” clause is optional, but must come first in a scenario
  • The “When” clause is required, and must come before the “Then” clause
  • The “Then”” clause is also required
  • An “And” clause can come after any “Given”, “When” or “Then”, but not first.



  • Fix broken package


  • First release [optilude]
Release History

Release History

This version
History Node


History Node


Download Files

Download Files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date (9.2 kB) Copy SHA256 Checksum SHA256 Source May 20, 2011

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting