Page History

...

These are the main things you need to know to test (well, almost!). Your Testing Coordinator or QA Lead may have additional instructions for you and as things change during QA. You may also see instructions that modify or change what is state here on our email list service. (For additional information on the Roles and Responsibilities of our QA Team members please see: QA Team Roles and Responsibilities.

1. Test Kuali Financial System (KFS)

...

Jira is an issue management tool designed principally for software projects. It is built an sold by Atlassian. The Kuali software projects use Jira for managing bugs, tasks and project issues. Each software project may have one or more Jira projects or spaces to manage their issues. To access a list of the the Kuali Jira home page and a list of all Kuali's Jira projects click here: https://test.kuali.org/jira/secure/BrowseProjects.jspa^{Image Removed}.

Where should I go to test KFS?

...

To set the Kuali Coeus project as the default the first time you log into Contour:

• Sign into Contour https://contour.kuali.org/^{Image Removed}
• Click on "Change Project" button in upper left
• Select "Kuali Coeus" from the pop-up box

To find the test scripts assigned to you:

• Sign into Contour https://contour.kuali.org/^{Image Removed}
• Click on "Reports" button in upper right
• Under the Global Reports tab, click on "!KFS - Testing Assignments & Status (by Team and Tester)"
• Choose your output, HTML or PDF
• Click "Run Report" button at the bottom
• This list is sorted by team, so scroll down to your team to see your list of scripts to test.
• Click on the blue ID link to pull up the script.

...

As indicated above, there are some more cases of course. If we use QA Workflow this way, an appropriately set list of issue filters will clearly indicate the state of our issues list.
Issue Status - Description Next Step(s) Filter Status Page Category
New - Requires QA Review

• A new issue has been reported. A QA Lead or other designated person, assigns themselves the issue, marks it as in "QA Review" and runs the issue through the Issue Review Process.
  "Requires Review" is the initial default for QA Workflow. "Requires Review" should only be set for new bugs that have never been looked at. If you open and review this field should be set to something else when you are done looking at it. Unless you decide that you are not going to complete the review and you are going to leave it for someone else. Even then, though, it would be better to assign it to the QA Lead who will review the issue and set QA Workflow = QA Review. QA Workflow = Requires Review

Fix For = (blank)
New - Requires QA Review
In QA Review

• Issue is being reviewed by a QA Lead or other QA team member. A QA Lead must review the issue (see QA Review Process described in the QA FAQ) to ensure it is actionable for development. NOTE: The reviewer must make certain that both the Fix Version and the QA Workflow field are set correctly.
  QA Review indicates that the bug is under review by a QA Lead. QA Workflow = QA Review

Fix For = (blank)
OR
Fix For = (a future release)
In QA Review
Subcommittee / SME / FC Review

• Requires SME functional discussion and decision. SME group for the appropriate module reviews issue. This may be to determine if the issue should be included the release currently under development (or a future release) or to resolve some functional questions that require input from the SME group. QA Workflow = Subcommittee / SME / FC Review

Fix For = Unknown
OR
Fix For = Unscheduled Release Subcommittee / SME / FC Review
Ready For Development

• The issue has been reviewed by QA and cleared for development work. The issue is reviewed by someone from development (usually the DM). If it is cleared for work, it is moved to the appropriate Development Project to be assigned to the developer who will work on the issue. If there are questions, it is marked as having "Questions From Development".
  Fix - The issue is ready to be addressed by the developers. QA Workflow = Ready for Development

Fix For = (the release currently in development) Ready for Development
Questions From Development - The review by Development identified questions that must be answered before the issue can be assigned. A QA or functional lead assigns themselves the issue and takes responsibility for resolving any open questions the developer may have. After answering the questions QA Workflow field can be set back to "Ready for Development" if that is appropriate or it may require SME Review as appropriate. QA Workflow = Questions From Development Questions From Development
In Development

• The issue has been accepted by Development for assignment and resolution. These issues reside in the Development project. The developer works to resolve the issue. When work is completed, the issue is set to "Resolved" indicating that the issue is fixed and ready for retesting by the reporter. NOTE: If the developer finds they cannot reproduce the issue at this time, they should assign the issue back to the reporter of the issue for final closing. QA Workflow = Ready For Development In Development
  Hindered - Functional
• There is a functional question about an in-progress issue that is preventing further work. These issues reside in the Development project. A QA or functional resource must address any question delaying work on the issue. Once the assignee is satisfied, they can mark the issue as "Unhindered.". Proceed? = Hindered Functional

Fix For = (the release currently in development) Technical Review (Development, Technical Committee(s))
Resolved Issues - Retest Required

• A fix for issue has been provided and the issue now requires retesting by the person who reported the issue. The issue is retested following the steps as originally written. Responsibility for retesting is usually conducted by the person who found and reported it but may also be conducted by a QA Lead or other designated person. The issue will then be either Closed or Reopened. Status = Resolved

Fix For = (the release currently in development) Resolved Issues - Retest Required
Closed - Fixed

• The fix supplied for the issue was tested and confirmed. The reported issue is no longer present. Nothing to do - end of issue. QA Workflow = QA Review Closed
  Closed - Duplicate
• This issue was already reported. Close any duplicates and leave the best written JIRA Open. Link duplicate JIRAs to open issue. QA Workflow = QA Review Closed
  Closed - Cannot Reproduce
• The issue was closed after it could not be recreated and confirmed. Nothing to do - end of issue. QA Workflow = QA Review Closed
  Closed - Won't Fix
• The issue will not be fixed because it was determined the behavior was "as designed" or some other technical reason. Nothing to do - end of issue. QA Workflow = QA Review Closed
  Reopened
• The issue has been reopened. Depends on where the issue was reopened and who reopens it. If the issue is in the QA project, it will go through the review process. If it is in a development project, it is the responsibility of the assigned developer to respond. (depends where opened)
  Deferred / Postponed
• The issue will not be fixed in the Release currently under development but will be considered for a future release. During QA, it does not matter if you set QA Workflow to QA Review or to one of the other review types, but it should never be left at "Requires Review". Always indicate the next step. Issues that are set to Unscheduled Release may require action in one or more of the additional review types - so set it. Picking one makes the next step clear. You can also set it to QA Review and set the Fix Version if that is clear. You can always review it again update any QA fields. QA Workflow = QA Review
  OR
  QA Workflow = Subcommittee / SME / FC Review

Fix For = (a future release)
OR
Fix For = Unscheduled Release In QA Review
Deferred to Future Release

• The issue will not be fixed in the Release currently under development but will be considered for a future release. After the successful release of the current version under development, these issues must be re-reviewed for inclusion in the subsequent release. QA Workflow = Subcommittee / SME / FC Review

Fix For = (any of the Unreleased Release Versions)
OR
Fix For = Unscheduled Release