Verification Results for 0.20
|
Basic Setup |
|
Test |
Implemented JPA |
Implemented MongoDB |
User is able to compile the project with an empty Maven repository mvn install -Dmaven.repo.local=/tmp/cleanrepo_ _ |
MF |
|
User is able to start and stop the portal zip binary release using the bundled Tomcat startup script (from packaged download)) |
|
|
User is able to start and stop the portal tar.gz binary release using the bundled Tomcat startup script (from packaged download) |
|
|
User is able to load the login page by pointing a browser to http://localhost:8080/__ |
MF |
MF |
|
Default Accounts |
|
Test_ _ |
Implemented JPA_ _ |
Implemented MongoDB |
User is able to log in with default accounts: canonical, john.doe, jane.doe |
MF |
MF |
User is able to log in with default OpenID account |
MF |
MF |
User is able to modify column layout |
MF |
MF |
User is able to switch to one-column layout |
MF |
MF |
User is able to switch to two-column layout |
MF |
MF |
User is able to switch to three-column layout |
MF |
MF |
User is able to switch to four-column layout |
MF |
MF |
User is able to switch to column layout with lesser number of columns (from 4 to 1) |
MF |
MF |
User is able to move gadgets from one column to another |
MF |
MF |
User is able to move gadgets into a newly created column |
MF |
MF |
User is able to create a new tab |
MF |
MF |
User is able to add gadgets to the new tab |
MF |
MF |
User is able to delete the new tab |
MF |
MF |
User is able to log out. |
MF |
MF |
"Remember me" feature works for user |
MF |
MF |
User changes are preserved across sessions |
MF |
MF |
|
User Profile Information |
|
Test |
Implemented JPA |
Implemented MongoDB |
User can update profile email address |
MF |
MF |
User can update profile "about me" information |
MF |
MF |
User can update profile "status" information |
|
|
Password and user name reminder features work |
|
|
User profile changes are preserved across sessions |
MF |
MF |
|
User Administration |
|
Test |
Implemented JPA |
Implemented MongoDB |
"Canonical" user has access to administration interface |
MF |
MF |
Administrator can add new users |
MF |
MF |
User search feature works correctly for known users |
MF |
MF |
User search feature works correctly for missing users |
MF |
MF |
Administrator can return user display to initial state after searches |
MF |
MF |
Administrator can grant administrator privileges to other users |
MF |
MF |
Administrator can remove administrator privileges to other users |
MF |
NO |
Administrator can enable and disable a user account |
MF |
MF |
Administrator can lock and unlock a user account |
MF |
MF |
Administrator can expire and unexpire a user account |
MF |
MF |
Administrator can delete a user account |
MF |
MF |
|
Widget Administration |
|
Test |
Implemented JPA |
Implemented MongoDB |
Administrator can list all widgets |
MF |
MF |
Unfiltered search features work correctly |
MF |
MF |
Filtered search features (by type and by status) work correctly |
MF |
MF |
Search filters handle empty inputs and empty returns correctly |
MF |
MF |
Search results can be cleared (widget page returns to original state) |
MF |
MF |
Administrator can update widget metadata (title, location, description, etc) |
MF |
MF |
Administrator can update widget status (published, preview) |
MF |
MF |
Administrator can disable and re-enable widgets |
MF |
MF |
Rave correctly handles error conditions: widget type setting is incorrect |
|
|
Rave correctly handles error conditions: URL location is incorrect |
OpenSocial: yes, Wookie: renders page inside widget |
|
|
Preference Administration |
|
Test |
Implemented JPA |
Implemented MongoDB |
Administrator and update and verify preference settings |
|
|
|
New Account Creation |
|
Test |
Implemented JPA |
Implemented MongoDB |
New users can successfully create accounts |
MF |
MF |
New users must provide required information |
MF |
MF |
New user applications must provide unique user names |
MF |
MF |
New user applications must provide unique email addresses |
MF |
MF |
New user applications must provide matching passwords |
MF |
MF |
New account applications must provide user names of appropriate length and format (no spaces, alphanumeric characters only, etc) |
MF |
MF |
New account applicants must provide passwords of minimal length and strength |
MF |
MF |
New user account forms are not subject to SQL injection and other common attacks |
MF |
NA |
|
Widget Store Usage |
|
Test |
Implemented JPA |
Implemented MongoDB |
User can add new widget |
|
|
Widget store can contain mutliple widget types (W3C, OpenSocial) |
MF |
MF |
|
Widget Store Administration |
|
Test |
Implemented JPA |
Implemented MongoDB |
Admin can enable new widget |
|
|
If preference is set to default published, the widget is immediately published |
|
|
|
Non-Default URLs |
|
Test |
Implemented JPA |
Implemented MongoDB |
User can access Rave from URL with IP or DNS (instead of localhost) |
|
|
Rave correctly renders widgets when accessed with URL other than localhost |
|
|
Rave tab and header navigation links work correctly with URL other than localhost |
|
|
|
Advanced Setup: LDAP |
|
Test |
Implemented JPA |
Implemented MongoDB |
User is able to login with the demo LDAP accounts johnldap, janeldap |
MF |
MF |
Advanced Setup: MySQL |
|
Test |
Implemented JPA |
User is able to reproduce all standard tests |
|
|
Advanced Setup: HTTPS |
|
Test |
Implemented JPA |
Implemented MongoDB |
Following standard Tomcat HTTPS/SSL set up, Rave login page can be accessed via HTTPS |
|
|