How to Verify Jiras

Owned by Andrea Schmidt, created
Last updated: Jun 25, 2023
4 min read

Keep in mind that once something has been set to "resolved", it will not be on the server until after the restart. The server list has the restart times at the bottom: http://nightly2.sakaiproject.org/

Most Jiras are verified on Trunk (master) on MySql, but sometimes a Jira indicates it needs to be tested for Oracle:

Image of the different trunk versions

Test Plan Passes

There are different sections in each Jira. The right side of the Jira gives the status of the Jira, (Resolved, Open, Closed, etc.), the versions affected and the version(s) for the fix. Currently, 23.0 [Tentative] is the “trunk” version.

Image of the right side of Jira which contains the status, Fix versions, etc.

 

This particular Jira has been resolved on 23.0 [Tentative], or “trunk”, as indicated by the Fix versions. Since the Jira has the Resolved status, it is ready for testing on trunk.

If the test plan passes you will need to enter a comment, indicating the server and the build where you tested.

 

 

 

 

 

 

 

The left side of the Jira has the test plan, general information regarding the bug or feature, and the Comments area.

There are 3 tabs: General, Testing and Release Notes.

To verify the Jira:

  • Read the test plan carefully and follow the instructions. Sometimes there are additional comments about changes or previous testing, and it’s important to read them incase something changed and the test plan was not updated. The General tab also has more information about the bug or feature, which may be helpful in understanding the issue.

  • If you were able to successfully complete the test plan with the expected results, then the Jira can be set to “Tested” which will then display a status of “Verified” after the change has been saved.

  • You can also add a screenshot if needed, (if something changed in the UI, for example), by clicking on the Attach link at the top and uploading your image.

  • Add a comment indicating which server and build you tested. This information is found under the icon at the bottom of all Sakai pages.

If the test plan passes and the Jira has been verified, once it is merged, the status for the other versions, (e.g. 22), will change from "Please merge" to "Merged".

Test Plan Fails

If the test plan fails, and the Jira has not been closed or merged to another branch, open the Resolved drop-down and select Reopen. Also include the server, (example for trunk/master: https://trunk-mysql.nightly.sakaiproject.org/) and the  build info in your comment.

Include a detailed comment indicating what failed and screenshots, if applicable. The more information you can give the developer, the better.

Do not reopen a Jira that has been merged to another server. If there is an issue after a Jira has been “Closed” on trunk, or been merged to another server, create a new Jira and link it to this Jira.

Verifying Jiras on other branches (servers)

Once the status is set to "Merged" for another version, this Jira needs to be tested on the server(s) with the merge, and if that works correctly, then you would set the status to "Verified" for that server:

  • Enter your comment indicating which server you tested, (e.g. for the 22 Status)

  • Click on “Merged” beside the server version, (e.g. for the 22 Status)

  • Select “Verified” from the drop-down

If the test plan failed on that server:

  • Include a detailed comment indicating what failed and screenshots, if applicable, and the server information. The more information you can give the developer, the better.

  • Add any supporting screenshots, if applicable.