|
Size: 5961
Comment: Implemented profile change tests
|
← Revision 14 as of 2012-05-30 21:07:27 ⇥
Size: 6012
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 24: | Line 24: |
| ||User is able to create a new tab || || | ||User is able to create a new tab ||Yes|| |
| Line 26: | Line 26: |
| ||User is able to delete the new tab||Yes|| | |
| Line 33: | Line 34: |
| ||User can update profile email address ||Yes|| ||User can update profile "about me" information ||Yes|| ||User can update profile "status" information ||Yes|| |
||User can update profile email address ||Yes || ||User can update profile "about me" information ||Yes || ||User can update profile "status" information ||Yes || |
| Line 37: | Line 38: |
| ||User profile changes are preserved across sessions ||Yes|| | ||User profile changes are preserved across sessions ||Yes || |
Rave is evaluating the use of JBehave to help automate and improve quality assurance testing. The test code is inside the rave-integration-tests module and documented on the website.
Basic Setup |
|
Test |
Implemented |
User is able to compile the project with an empty Maven repository mvn install -Dmaven.repo.local=/tmp/cleanrepo |
|
User is able to start the compiled portal using mvn cargo:start (from SVN checkout) |
|
User is able to start the portal zip binary release using the bundled Tomcat startup script (from packaged download)) |
|
User is able to start 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/ |
Yes |
Default Accounts |
|
Test |
Implemented |
User is able to log in with default accounts: canonical, john.doe, jane.doe |
Yes |
User is able to log in with default OpenID account |
Yes |
User is able to modify column layout |
|
User is able to switch to one-column layout |
|
User is able to switch to two-column layout |
|
User is able to switch to three-column layout |
|
User is able to switch to four-column layout |
|
User is able to switch to column layout with lesser number of columns (from 4 to 1) |
|
User is able to move gadgets from one column to another |
|
User is able to move gadgets from one column to another |
|
User is able to move gadgets into a newly created column |
|
User is able to create a new tab |
Yes |
User is able to add gadgets to the new tab |
|
User is able to delete the new tab |
Yes |
User is able to log out. |
Yes |
"Remember me" feature works for user |
|
User changes are preserved across sessions |
|
User Profile Information |
|
Test |
Implemented |
User can update profile email address |
Yes |
User can update profile "about me" information |
Yes |
User can update profile "status" information |
Yes |
Password and user name reminder features work |
|
User profile changes are preserved across sessions |
Yes |
User Administration |
|
Test |
Implemented |
"Canonical" user has access to administration interface |
Yes |
Administrator can add new users |
|
User search feature works correctly for known users |
Yes |
User search feature works correctly for missing users |
|
Administrator can return user display to initial state after searches |
|
Administrator can grant administrator privileges to other users |
|
Administrator can remove administrator privileges to other users |
|
Administrator can enable and disable a user account |
|
Administrator can lock and unlock a user account |
|
Administrator can expire and unexpire a user account |
|
Administrator can delete a user account |
Yes |
Widget Administration |
|
Test |
Implemented |
Administrator can list all widgets |
|
Unfiltered search features work correctly |
|
Filtered search features (by type and by status) work correctly |
|
Search filters handle empty inputs and empty returns correctly |
|
Search results can be cleared (widget page returns to original state) |
|
Search results can be cleared (widget page returns to original state) |
|
Administrator can update widget metadata (title, location, description, etc) |
|
Administrator can update widget status (published, preview) |
|
Administrator can disable and re-enable widgets |
|
Rave correctly handles error conditions: widget type setting is incorrect |
|
Rave correctly handles error conditions: URL location is incorrect |
|
Preference Administration |
|
Test |
Implemented |
Administrator and update and verify preference settings |
|
New Account Creation |
|
Test |
Implemented |
New users can successfully create accounts |
Yes |
New users must provide required information |
|
New user applications must provide unique user names |
|
New user applications must provide unique email addresses |
|
New user applications must provide matching passwords |
|
New account applications must provide user names of appropriate length and format (no spaces, alphanumeric characters only, etc) |
|
New account applicants must provide passwords of minimal length and strength |
|
New user account forms are not subject to SQL injection and other common attacks |
|
Widget Store Usage |
|
Test |
Implemented |
Widget Store Administration |
|
Test |
Implemented |
Non-Default URLs |
|
Test |
Implemented |
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 |
User is able to login with the demo LDAP accounts johnldap, janeldap |
Yes |
Advanced Setup: MySQL |
|
Test |
Implemented |
User is able to reproduce all standard tests |
|
Advanced Setup: HTTPS |
|
Test |
Implemented |
Following standard Tomcat HTTPS/SSL set up, Rave login page can be accessed via HTTPS |
|