When your integration nears completion, consider running through these common test paths. In each case, we identify the goal of the test and provide instructions for common solutions. These are intended to be used after your integration is functional; they target issues that may not be easily noticable.

User Tests

Process Login
Follow these steps:

1. View a page without a having ticket (not logged in).
2. Click the EasyEdit button.

Expected: A dialog appears with customized text and a submit button that, when clicked, takes you to your normal sign in process.
Possible Failure: If the dialog has incorrect text or does not take to you the sign in process, it may be a problem with your customization of the login dialog.

Wait for Expired Ticket
Follow these steps:

1. Generate a ticket for a user.
2. View a page with an editable content cell.
   
3. Wait more than 10 hours, at which point the ticket will expire on our system.
4. Click the EasyEdit button

Expected: The Client Application will request a new ticket automatically and ask the user to try the action again. Clicking EasyEdit again will act normally.
Possible Failure: If the message continues to appear, it may be a problem with the WPCAPI.generateTicket method.

Edit Locked Page
Follow these steps:

1. Sign in as a moderator.
2. View a page with a content cell.
3. Click the "content tools" link to acquire the content tools menu.
4. Click the "lock content" link.
5. Enter a reason for locking the content and submit the dialog.
6. Click the EasyEdit button.
7. Edit some content.
8. Save the content.
9. Sign out.
10. Sign in as a registered user.
11. Click the EasyEdit button.

Expected: After attempting to load the editor, the editor closes and presents a tooltip explaining that the content has been locked.
Possible Failure: If the lock action is not available or fails, or if the registered user is able to edit the content, it may be a problem with how your user roles are set when you authenticate your users.

Click Username
Follow these steps:

1. Sign in to the site.
2. Click the EasyEdit button.
3. Edit some content.
4. Save the content.
5. Click the "content history" link at the bottom of the cell.
6. Click your username in the Content History lightbox for your recent revision.

Expected: Your username is linked and takes you to a page about you.
Possible Failure: If the username is not linked or the link takes you to an unexpected page, it may be a problem with how you set the profileUrl as a parameter to UserService.login.

Style Tests

Check For Style Customizations
Follow these steps:

1. Sign in to the site.
2. Click the EasyEdit button.
3. View the toolbar's title bar, background, and border.
4. Click the Add Photo button in the toolbar.
5. View the Add Photo and Cancel button.
6. Click the Search Yahoo Images link.
7. Search for an image, e.g., "lily".
8. Click on one of the results.
9. View the background color of the result.
10. Cancel the dialog.
11. Cancel the editor.
12. Click the "content history" link.
13. View the table header and alternate row color.
14. Mouse over a link.
15. View the link color.

Expected: All colors fit your brand's style guide.
Possible Failure: Some of these items may be incorrectly colored or styled with the Interface Customization methods in the client application.

Add Wide Content
Follow these steps:

1. Sign into the site.
2. Click the EasyEdit button.
3. Enter a long string of unbroken characters, e.g., "WWWWW....."
4. Keep going beyond the normal bounds of the content space.
5. Save the page.
   

Expected: Your site retains its structure and the extra content is handled gracefully.
Possible Failure: Content can be of any size as your users add to it, be it with images, tables, or long strings of unbroken text. You can handle this by setting an overflow to the content area. Learn more about content overflow in our page on user-generated content styles.

Check the Table Borders
Follow these steps:

1. Sign into the site.
2. Click the EasyEdit button.
3. In the Toolbar, click the Add Table button.
4. Add the table.
5. Save the content.

Expected: The colors of the user-generated table borders should conform to your brand.
Possible Failure: Border colors are inherited from your site's CSS. If you do not set the border colors for the location you import the cell, they might appear incorrect. Learn more about table border colors in our page on user-generated content styles.

User-Generated Page Tests

Rename User-Generated Page
Follow these steps:

1. Sign in as a moderator.
2. Navigate to a user-generated page.
3. Click the "content tools" link.
4. Click the "rename content" link.
5. Enter an explanation and then rename the page.

Expected: You are taken to the new page and the new page name appears on the page.
Possible Failure: The user-generated cell's display name may be used in your URL, in which case your URL may have been updated. If there is an error in this, it may be a problem with your WPCAPI.generateCellURL method override. Learn more about overriding methods in our page on function overriding.

Cache Tests

Edit Cached Content
Follow these steps:

1. Sign into your site.
2. Click the EasyEdit button.
3. Edit the content.
4. Save the page.
5. Reload the page in your browser.

Expected: Your new content is visible.
Possible Failure: If you have implemented your own caching on our content or if your pages do not request the content anew on every request, you must tell us about your caching or the new content will not be retrieved by the client application.