uP2.5 QA

Owned by Andrew Petro
Last updated: May 17, 2005Version comment
4 min read

This page is for discussing QA to be applied to the uPortal 2.5 release.

Unit tests

Before release we should run our unit tests using our ant "runtests" task and ensure that all tests are passing.

What to check

RC2?

final?

runtests Ant target passes all tests

OK

?

User acceptance tests

A suggestion on how far to go with this

User acceptance tests for uPortal 2.5.0 will be a slightly more formal version of the "try it out in a web browser" approach. For 2.5 we won't be creating test scripts that someone unfamiliar with uPortal could be expected to follow. ("Click the third tab. Click the ...") For uP 2.5.0 UAT scripts will be more like checklists of things to verify.

What to check:

Portlet support

What to check

RC2?

final?

Demonstration portlets in the "admin" layout all render.

OK

 

Consumption of the WSRP4j test WSRP producer

FAIL

 

The modified WSRP4j proxyportlet has not yet been verified to work in HEAD. Attempts to use it have yielded stack traces in the channel. See the associated JIRA issue.

JRE support

What to check

RC2?

final?

Compiles and runs under JRE 1.4

OK

?

Compiles and runs under JRE 1.5

?

?

Layouts

Simple layouts

Thing to check

RC2?

final?

New users properly receive a template layout

?

?

Users with a template layout which they have not modified which is changed in the template user see the changed layout on next login

?

?

Users can change layouts by Moving existing tabs

?

?

Moving a channel from one tab to another

?

?

Deleting a tab

?

?

Adding a new tab

?

?

Adding a channel to an existing tab

?

?

Subscribe-time parameter setting

?

?

Aggregated layouts

DLM

  • The "student" user when logging in for the first time sees three tabs in this order, "Real Entertainment", "Useful News", and, "Main Student Tab". The first two are from two different default fragments. The third is owned by the "student" user.
  • Users receiving the "Real Entertainment" fragment tab can not delete the, "Number Guessing Game", channel at the top of the left column.
  • Users receiving the "Real Entertainment" fragment tab can not add a channel above the, "Number Guessing Game", channel but can add channels below it.
  • Users receiving the "Real Entertainment" and "Useful News" tabs can move the entertainment tab without restriction since that fragment has the highest precedence of the two default included fragments.
  • Users receiving the "Useful News" tab can't move their own tabs to the left of the news tab since that fragment has locked that tab in place and it has higher precedence than a user's own layout elements.
  • Users receiving the "Real Entertainment" tab can't rename the entertainment tab since the fragment restricts edits of the tabs attributes.
  • Users receiving the "Useful News" tab can change the name of the news tab since that fragment does not lock the tab's name.
  • When the "news-lo" user (password of 'news-lo') who owns the fragment containing the "Useful News" tab selects that tab in their preferences area, un-checks the "Edit Properties" check box, and presses the "Set Actions" button then when users log in who receive the "Useful News" tab but have previously renamed that tab their name change will now be overriden and the name will have returned to "Useful News".
  • Users receiving the "Real Entertainment" tab see column widths for the columns on that tab of 40% for the left column and 60% for the right column.
  • When the "ent-lo" user (passworkd of 'ent-lo') who owns the fragment containing the "Real Entertainment" tab changes the column widths and presses the "Save Widths" button, then users who receive the "Real Entertainment" tab should see the column width changes the next time that they log in provided that they have not overridden them with their own values.
  • When a new fragments is added to dlm.xml with a specific, not-yet-logged-on user id, and the web server restarted, and the password configured for that user using md5passwd, then when that user logs in they should have an empty default layout. (ie: no tabs appear.) The following fragment declaration granting access to "Students" can be used as a sample. Remember to run, "ant md5passwd -Dusername=test-lo", to set up a password for this user otherwise they won't be able to log in. Also note that the definition must be in dlm.xml and the web server bounced before they log in. Otherwise they are treated as a regular user and get the default user template layout rather than the default fragment user template layout identified in dlm.xml.
<dlm:fragment name='Test' ownerID='test-lo' precedence='80'>
   <dlm:audience evaluatorFactory='org.jasig.portal.layout.dlm.providers.GroupMembershipEvaluatorFactory'>
     <attribute mode='memberOf' name='Students'/>
   </dlm:audience>

Helpful Error Reporting

Error reporting for the following configuration options must be helpful enough the user shouldn't have to email the mailing list to find out what is wrong. Also, ant should fail-fast and report an error to the user. Helpful errors shouldn't hide stack traces. These error messages and stack traces should be shown on the ant console and shouldn't require the user to find the portal.log.

  • incorrect db connection configuration (username,password or connection)
  • missing jar for jdbc connection
  • database server not responding
  • malformed xml in a chanpub file
  • missing jars that are required for running on jdk 1.4