Code is written and submitted one Enhancement (PP) at a time by the developers.
The code is given an initial review by the development team.
Completed Enhancements (PP) are moved to "TestingQA Review" status, and the related code is imported into the OLE Test Environment as needed.

Code Promotion

The testers review the Release Documentation on the Kuali wiki to determine if a Task an Enhancement or Bug/Defect belonging to one of their Stories Test Cases is ready for testing.
- OLE Releases are divided into release versions. A major release is a new numbered version of the OLE software package, and represents the implementation of a large bundle of new functions and features. A minor release is a bundle of updates and bug fixes released as needed, and marked with a tag rather than a major version number.
  - The Demo Environment and official download link are updated only for major release versions (e.g., OLE 0.8, OLE 1.0, OLE 1.5, OLE 2.0, and so on).
  - The Test Environment is updated with minor release versions (e.g. r16094, r16528). Updates to the Test Environment occur as needed, when there is a sufficiently stable working version of the code that functional testing can begin.

...

Results are gathered from testing, and a determination is made as to whether the Test Case should pass or fail.
- Pass
  - If the tester is able to successfully execute all testing steps necessary to fulfill the purpose of the Test Case, the test can be considered passed.
- Fail
  - If the tester is unable to successfully execute all testing steps required by the Test Case, the test can be considered failed.
  - If the tester is able to execute all necessary steps, but the outcome does not satisfy the Acceptance Criteria statement on which the Test Case is based, then the test can be considered failed.
- Feedback
  - A comment indicating that a test has passed is helpful when reviewing the Test Case's history later.
  - If a Test Case fails, a comment explaining the reasons for failure is necessary for creating an adequate Bug/Defect, or for giving an adequate explanation for the developers in the case that an existing Bug/Defect requires additional work.
If the test passes, it is automatically assigned to the QA Analyst (Jain).
If the test fails, it is automatically assigned to the QA Manager (Rich).
- In the case of failure, the Task or a Bug/Defect associated with being tested by the failing Test Case will be returned to an "in development" statusthe developers.

Center

Versions Compared