QA for 2.5.2
Regression Testing \
Regression Testing is our #1 priority for 2.5.1 testing since 90% of individual fixes underwent testing prior to being merged. _* The usual test plans can be found off the Test Conditions and Scripts page.
Newer Test Conditions
In addition, rSmart has contributed some alternate test scripts. When these are available, they will be listed under the component in the Regression Testing section of this page.
Important Notes:
- For these scripts, please review the manual dependencies when they are listed.
- The scripts assume that you have certain sites with certain users and the navigation may be a bit off. You should be able to look past the parts that specify to use X site and B user to get the general gist of the functionality.
- Some have not been updated fully for generic Sakai so the portal navigation might be a little off.
- Most test data can be found in a zip file on the New Test Plans page.
Please feel free to update conditions that are not correct.
When testing remember to
- File any new bugs you find it JIRA
- It is also helpful if you test against a 2.5.0 instance as this helps us determine if this is a recent regression.
Test Servers to use (links to the servers can be found at Test Instances)
-
-
- QA1-NL
- QA2-US
- QA1-ZA
- QA1-OSP
-
- Jira Verification
Regression Testing
= Regression completed.
= in progress / assigned out. Please indicate this in the completed field when starting a component so others know you are testing.
= problem. Any bugs should be tested against a 2.5.0 instance (like QA3-US) to determine if it is a regression from the previous release.
| Component | Completed | |
|---|---|---|
| Accessibility | (SM) |
|
| Announcements | (UM) |
|
| Assignments Alternate Test Plans |
(NS) |
|
| Authz (SVN module) | N/A |
|
| Blog Alternate Test Plan |
(NS) |
|
| Build (Maven) | QA Admins / RM |
|
| Calendar Summary | (NS) |
|
| Chat Room | (NS) |
|
| Content (SVN module) | N/A | |
| Course Management (SVN module) | N/A | |
| Database | N/A | |
| Email (SVN module) | N/A |
|
| Email Archive Alternate Test Conditions |
UM, Indiana, UCT |
|
| Entity (SVN module) | N/A | |
| Entity Broker | N/A | |
| Event (SVN module) | N/A | |
| Forums Alternate Test Conditions |
(NS) RC1 RC2 |
|
| Gateway | |
|
| Gradebook | (NS) |
|
| Help | (UM) |
|
| Home | (NS) |
|
| Install/Upgrade | QA Admins - inprogress |
|
| Internationalization | |
|
| JCR (SVN Module) | N/A | |
| Mailtool | (UM) |
|
| Memory (Admin Site Management) | (UM) |
|
| Message (SVN module) | N/A | |
| Messages / MC Alternate Test Conditions |
(NS) |
|
| Metaobj (testing done under forms) |
N/A |
|
| MOTD (Admin Site Management) | (UM) |
|
| OSP: Forms Alternate Test Conditions |
(IU/SV) |
|
| OSP: Other | (IU/SV) |
|
| OSP: Portfolios | (IU/SV) |
|
| OSP: Wizards - General | (IU/SV) |
|
| OSP: Wizards - Hierarchy | (IU/SV) |
|
| OSP: Wizards - Matrix | (IU/SV) |
|
| OSP: Wizards - Sequential | (IU/SV) |
|
| Podcasts Alternate Test Conditions |
(NS) |
|
| Polls |
(UM) |
|
| Portal | ||
| Providers | N/A | |
| Quartz Scheduler | (IU) |
|
| Reset Password | (NS) |
|
| Resources | (NS) |
|
| Rwiki | (NS) |
|
| Samigo: Grading | (UM) |
|
| Schedule | (WC) |
|
| Search | (UM) |
|
| Section Info | (NS) |
|
| Site (SVN Module) | N/A | |
| Site Info Alternate Test Conditions |
(NS) |
|
| Sites (Gateway) | ||
| Skins (CSS) | ||
| Syllabus | (UM) |
|
| User (SVN module) | N/A | |
| Web Content | (NS) |
|
| Web Services | |
|
| WebDAV | (NS) (UM/NS) |
Jira Verification
- Sakai 2.5.1 QA Awaiting Verification (
0 issues) - Sakai 2.5.1 QA Verified (
0 issues)
Note: Security issues are not included in the above filters.
Workflow
Since this is a maintenance release, the verification workflow is slightly different than for a major release. Rather than closing an issue when you verify it, you will be setting the "2.5.x Status" field to Closed. (The regular Status and Resolution fields are for tracking work in trunk for the next major release.)
- Pick an issue from the list of 2.5.1 issues awaiting verification. (If it looks like it will take some time and effort to verify the issue, then you might want to add a comment indicating that you are currently working on verfiying it, so that some else doesn't start duplicating your effort.)
- Verify the fix for the issue works. (Try it on different QA servers, with differnt web browsers, etc.)
- Fix is OKAY
- Add a comment describing what you did to verify the issue.
- Set the "2.5.x Status" field to Closed.
- Fix is NOT OKAY
- Reopen the issue.
- Assign the issue to the appropiate developer to revisit, or if that's not clear, assign it to Peter Knoop.
- Add a comment describing what is wrong and how to reproduce the problem.
- Set the "2.5.x Status" field to None.
- Remove 2.5.1-rc01 (and any other relevant values) from the Fix Version list.
- Fix is OKAY
Jira Version Reports
A good starting point to see what issues are fixed in a particular tag: