internal rss (rd)

• Anywhere you have the option to get an rss feed (look for the orange icon) you should now have a blue icon for internal rss. Click it to add this to your internal rss (you should be able to get an rss feed from a single conversation, from a tag, or for a user)
  
• Go to your 'my page' and under the 'my feeds' tab and you should have conversations related to that rss feed (conversation, tag, user). The 'Manage' tab should allow you to manage (delete) this rss feed

report abuse (mcr)

• Create a new interest group - invite one of your test users
• Go to the admin 'settings' page, and set the 'Interest group for abuse' setting to your new interest group
• Conversation (wiki, conv, poll, event, etc) 'show' views should now have a new 'warning' (abuse) icon
• For the given conversation, click the 'abuse' icon - you should get a pop-up asking you to confirm. Confirm, and a flash notice should tell you that the abuse was reported.
• The members of your interest group should receive an email indicating that an abuse was reported, and link to the conversation, and tell you who reported the abuse

versioning (dth)
        create a conversation, save it
        view the conversation, see that nothing about versions shows up
        edit the conversation, change some text
        view the conversation, see that it shows "2 Versions"
        revert to the older version, ensure that a new version got added
        !!repeat process for wikis
       
security (dth)
        create a conversation, should see 3 options:
                *this conversation should be publicly visible
                *this conversation should be visible to hub members only
                *this conversation should be visible to the following groups:
        confirm that groups dropdown only contains groups that are private
        click hub members only radio button; tag textbox should get "ngeneraLock" in it (if not already there)
        click should be publicly visible; tag should be gone
        reclick hub members only; confirm tag goes back
        click dropdown and add a group, confirm tag gets added
        add another group, confirm tag gets added
        click publicly visible, confirm tags removed
        click groups button, confirm groups added back
        click [X?] next to a group, confirm only that group removed
        save conversation, confirm tags are preserved

do exchanges with facebook avatar and hub avatar (jb)

        Update your avatar file base
        Sync your user with your facebook profile including the avatar
        check the avatar is now facebook
        Upload a new file and check file is now updated
        Log out and log back in, verify uploaded file is still the avatar.

various storage service entries(jb):

        Create interest group with an avatar
        Update interest group avatar in admin screen
        Create flipper in admin screen with picture
        Update flipper in admin screen with a new picture
        Attach files to a conversation, include pictures and normal files
        Edit the conversation and expand "Attach Documents or Images" and then expand "Existing Documents"
        Verify the file appears, and a thumbnail to the picture appears.
        Update the image and file, verify that it changes within the conversation

trust based security (mcr):

• You need 3 users in this scenario (3 different browsers works well here, I use IE, FF and Chrome)
• Create a conversation/wiki/poll/event in a private interest group of which you are a member
• Ensure that your other 'test' user can not access the conversation
• Share this conversation with this user by editing the conversation and clicking the share tab and added them (not as a share only yet)
• See that this user can view the conversation. If it's a wiki, see that the test user can edit the wiki as well
• ensure that some other member of the private interest group can see this conversation still.
• Now edit the conversation to make it a 'share only' relationship with your test user
• Ensure that your test user can see the conversation
• Ensure that the 3rd user, who is a member of your private interest group can NOT see the conversation
• Now edit the conversation to remove the test user from the conversation
• The test user should no longer have access to the conversation, but the other members of the interest group should be able to see the conversation again.

email changes (dth) -

• send out emails from the hub to notify people of things, confirm that it comes from xxx@ngenplatform.com.
• send an email to the hub (staging@ngenplatform.com) and confirm a conv is created
• reply to a reply in email and see that it gets posted

User Banning (ar)

• A user can be banned from logging in through the user service by setting the value service_user.users.banned = 1 for a specific user. One this has been set and the user tries to login again they should encounter a http 403 Forbidden message.
• Note that this will only work if the user logs out and tries to log in again or when starting a new session. If a user is already logged in and then banned in the database the user will still be able to browse on the hubs. This will be taken care of in a future release.