| Anchor | ||||
|---|---|---|---|---|
|
| Center |
|---|
...
This section provides a detailed introduction of the four most common types of Jira issues involved in QA Testing: the StoryBug/Defect, the TaskEnhancement (PP), the Bug/DefectEnhancement, and the Test Case.
...
Bug/Defect
The Story is the OLE Jira Bug/Defect issue type that serves as the master task for a given piece of functionality. Th Kuali design philosophy means that any major function requested in our software, like the ability to create a purchase order, starts out as a story that a user has told us; for example, "I work in acquisitions, and I need the software to enable me to place an order with a vendor." The sum of the Story issues in the OLE Jira project describe the full functionality that we want to offer with OLEa "to do" for developers. In this case, the "to do" is to notify programmers that an already-established, previously tested piece of functionality is no longer working.
...
Enhancement (PP)
The Task is an Enhancement (PP) is the main OLE Jira issue type that serves as a "to do" item in developing a piece of functionality. The development team reviews the Stories and the functional specifications attached to them, and then determines what Tasks need to be accomplished in order to establish the requested functionality. Breaking up Stories into Tasks allows for faster and more incremental developmentused for the development of new features, and appear on the Project Plan for each OLE release. Enhancement (PP) issues are the main focus of development, and will generally contain the Functional Specification documents used to develop Test Cases.
Bug/Defect
...
Enhancement
The Enhancement is the OLE Jira issue type that allows users to suggest improvements of OLE environments. Enhancements will be considered by the appropriate SME team and/or Functional Council who will then determine any actions to be taken and for which release.
...
The Test Case is the basic OLETS issue type. Test Cases tend to represent one item from the Acceptance Criteria of a Functional Specification document. Alternately, a Test Case can represent one Bug/Defect item which is ready for testing.At At the time of testing, a Test Case should include a descriptive statement of what is to be tested (purpose statement), as well as a set of general instructions (steps) for how the test should run. By the time the Test Case is ready for review by the QA team, it should also include a Selenium script recording all the steps undertaken during testing of the issue.Test Cases will relate to the Story containing the relevant functional specifications, and to either a Task or a Bug/Defect establishing the functionality to be tested Each Test Case will have a "Parent Jira" field with the Enhancement (PP) containing the specification from which the test was drawn.
Review of Issue Types
The table above provides a brief summary of all the information provided in this section. See the article on Linking in Jira below for an expanded version of this table with a review of the above issue types and their relationship to Test Cases.Top of Page
Top of Section
| Center |
|---|