...

The Testing Process in Jira

Outlined below is a brief overview of the OLE testing process. The outline below is more of a summary than a detailed exploration, and is meant to help give a general picture of the OLE testing workflow, and how it fits into the larger scheme of the OLE development cycle.

Story Development

1. A Story issue is handed off for testing, with the Functional Specification document attached and complete Acceptance Criteria in place.
2. The Story is broken down into Tasks by the development team.
3. Code is written and submitted one Task at a time by the developers.
4. The code for each Task is checked individually by the development team.
5. Completed Tasks are moved to "Testing" status, and the related code is imported into the OLE Test Environment in bi-weekly updates.
6. The testers review the Release Documentation on the Kuali wiki to determine if a Task belonging to one of their Stories is ready for testing.
   1. OLE Releases are divided first into Milestones. A Milestone Release is the release of a new numbered version of the OLE software package, and represents the implementation of a large bundle of new functions and features.
      1. The Demo Environment and official download link are updated only on Milestone releases.
      2. The current Milestone Release is OLE-0.8.0.
   2. OLE Milestone Releases are subdivided into Iterations. Iterations are marked with a letter, and are bi-weekly, internal updates to the OLE application for testing purposes. Each Iteration marks the implementation of a large grouping of Tasks and newly resolved Bug/Defect issues.
      1. The Test Environment is updated with each Iteration.
      2. The current Iteration is OLE 0.8.0-H. (8/20/2012)

User Testing

Testing Outcome

...