/
Sakai 11 JIRAs Page

Sakai 11 JIRAs Page

Dec 17, 2021

Overview

The Sakai 11 JIRAs page provides information for testing Sakai 11 JIRA issues. Here you’ll find useful information for locating, testing, and documenting the resolution of Sakai 11 JIRA issues. See the sections below to get started.

How to Test JIRAs

For a step-by-step walkthrough of the JIRA testing process, see the following document: 

Procedure for Testing Sakai 11 JIRAs

Which JIRAs to Test

Use the following filters to find current Sakai 11 JIRAs. Test these Jiras (and the ones that follow) in one of the Master (Trunk) Nightly Testing Environments:

1.)  Test in Trunk for 11 Merge. Priority!

Filter URL: https://jira.sakaiproject.org/issues/?filter=15621

Filter Parameters:  category = Sakai AND "11 status" = Merge AND resolution = Fixed AND status = Resolved ORDER BY priority DESC, key ASC

key summary priority components assignee reporter updated created
Refresh

 

  1a.)  Test in Trunk for 11 Merge. Labels = "qaready"

qaready - Indicates that a test plan or sufficient information is available in the JIRA for a QA tester to verify a fixed issue in Trunk.

Filter Parameters:  category = Sakai AND "11 status" = Merge AND labels = qaready AND resolution = Fixed AND status = Resolved ORDER BY priority DESC, key ASC

key summary priority components assignee reporter updated created
Refresh

  1b.)  Test in Trunk for 11 Merge. Labels = "qatestplan"

labels = qatestplan indicates that a test plan is needed, or at least information on how the JIRA can be verified.

Filter Parameters:  category = Sakai AND "11 status" = Merge AND labels = qatestplan AND resolution = Fixed AND status = Resolved ORDER BY priority DESC, key ASC

key summary priority components assignee reporter updated created
Refresh

 1c.)  Needs Addition Testing in Trunk. Labels = "needstesting"

needstesting - Jiras for which someone has indicated additional testing is needed, usually to confirm it is truly an issue.

Filter Parameters:  category = Sakai AND labels = "needstesting" AND affectedVersion = "11.0 [Tentative]" ORDER BY priority DESC, key ASC

key summary priority components assignee reporter updated created
Refresh

 

Labels Glossary

qaready -  Indicates that a test plan or sufficient information is available in the JIRA for a QA tester to verify a fixed issue in Trunk.

qatestplan - Indicates that a test plan or other information is needed in order to perform QA testing.

needstesting - Jiras for which someone has indicated additional testing is needed, usually to confirm it is truly an issue.

11blocker - a JIRA which is still open (not resolved) and we want to consider if the priority is set correctly. Asking for "another pair of eyes" to assess the relative importance of the Jira.

Searching for JIRAs

**Simplified, Easy-to-Use, Bring-it-on! JIRA Search**

To search for JIRAs:

  1. Select Basic to switch to the simple search view.

  2. Under More, select Component(s), then choose the desired component. (This often corresponds to tool name.)

  3. In the Contains text text field, enter the desired search text.

 

New features in Sakai 11 - **For Reference ONLY. Not for Testing.**

The following represent potentially new functionality in Sakai 11. 

Announcements

NOTE: For reference in building regression script only. Potentially new functionality in Sakai 11. NOT for testing.

type key priority summary assignee reporter status updated created
Refresh

Assignments

NOTE: For reference in building regression script only. NOT for testing.

type key priority summary assignee reporter status updated created
Refresh

 

Chat Room

NOTE: For reference in building regression script only. NOT for testing.

 

CKEditor (WYSIWYG)

NOTE: For reference in building regression script only. NOT for testing.

 

Dashboard

NOTE: For reference in building regression script only. NOT for testing.

 

Dropbox 

NOTE: For reference in building regression script only. NOT for testing.