Testing Userpoints for version 6

There are a lot of changes that we have in store for userpoints and we are planning to get them all in before we release an official stable 6 version of UP. I, however, got a nice whipping when I released version 5.3 and I do not want a repeat of that. 5.3 was released with several tiny, stupid bugs that could have been easily avoided if I had the time to test the module properly. Unfortunately I nor anyone else had this time. Fortunately we have a new weapon. Simpletest.

I have already begun writing several tests of Userpoints and I'll be checking them off this list as I complete them. I'd like to get all of these in before any major work to the API is performed as it is currently stable and I'd like to keep it that way. My lists of tests is below, please free to add to them and, better yet, write a test.

It looks daunting but many of these tests are only a few lines and a few of them are a single line.

API tests

• Points
• Call with only points are granted to logged in user
• Call with points matches transaction table
• Call with points matches transaction & updates summary table
• Negative points caused summary table to decrease
• Transaction table and cache table stays in sync through multiple point add/deletes
• Points Array
• Call with no points fails
• Call with non numeric point values fail
• Call with only points are granted to logged in user
• Call with uid & points are granted to the appropriate user
• Call with uid & points for a non-existent user fails
• Call with a tid that is non-existent fails
• Call with points & description, description is set correctly
• Call with points & event, event is set correctly
• Call with points & reference, reference is set correctly
• Points in transaction table match points in summary table
• All
• Summary tables sums to non-moderated points in transaction table
• userpoints_get_current_points
• Called with no arguments returns current user
• Called with uid returns points for default tid
• userpoints_get_max_points
• Called with no arguments returns current user
• Returns same number as highest point level according to transaction table
• userpoints_get_default_expiry_date
• Returns a valid unix timestamp
• Moderation
• Call with invalid moderation status fails
• Call with points & moderation and set to moderation correctly
• Call with points & moderation does not modify summary table

UI and API tests

• userpoints_get_default_expiry_date
• Returns a valid unix timestamp
• userpoints_get_categories
• returns an array
• userpoints_get_default_tid
• returns a valid term id
• userpoints_get_default_vid
• returns a valid vocabulary id
• Expiration
• Points added with an invalid expirydate (non-timestamp) fails
• Expirydate given via API matches transaction table
• Points expire correctly (add points to expire in 1 sec. then call expiration
• Correcting entry is added to transaction table & summary table is updated
• Permissions
• User without admin userpoints permissions can not modify points
• User with admin userpoints permissions can modify points