ACCOUNTS
USER APPLICATION
Go to http://bokken.cnx.rice.edu/ and click the "Join" link at the top right. Verify that you get the "Request a Connexions Account" screen.
Click the "New Author or Instructor?" link at the bottom of the left-hand sidebar and verify that it takes you to the same page.
Click "Continue" without filling anything in. Verify that orange error boxes appear around the First Name, Last Name, and Email fields, saying that "Input is required but no input given".
Enter sample data for all fields, using data similar to but not exactly like the examples. Use your own email address, and make the middle name "TEST". Click Continue. Verify that nothing is obviously wrong with the list of suggested and unavailable usernames.
Enter your own existing username in the username field and click "Continue". Verify that you get the error "This member id is invalid or already in use".
Retype the originally-suggested username in the username field. Select some answers to the survey questions and click "Continue."
Click "Request Account" without checking the checkbox. Verify that you get a "You must agree to the license to proceed." error.
Click the checkbox and choose "Request Account". Verify that you get the "Account Request Complete" screen.
Check your email and click the URL provided, or copy it and paste it into the address bar. Verify that you get the "Set your password" page.
Click "Set my password" and verify that you get a "Your password must contain at least five characters" error.
Enter two valid, but different passwords (e.g., "asdfg" and "asdfh"). Verify that you get an error message saying that the passwords did not match.
Enter the correct username and two matching valid passwords. Click "Set my password." Verify that you get the "Password Created" screen, with a message that "Your password has been set successfully. You may now log in with your new password."
Enter the correct username and password for the new account and verify that you are logged in.
Tell Jenn the username you used, and have her check that the survey results made it in.
PASSWORD RESET
If you are logged in, click "Log out" at the top right of the personal toolbar.
Click "Forgot your password?" on the left sidebar. Enter the username of your account (or a test account that has your email address) and click "Start Password Reset". Verify that you get the "Password reset confirmation sent" page.
After a few minutes, check your email, follow the URL, and verify that you get the "Set your password" page.
Click "Reset my password" and verify that you get a "Your password must contain at least five characters" error.
Enter a reasonable, valid password in one of the password fields and leave the other password field blank. Click "Reset my password" and verify that you get the same error.
Enter the correct username and two matching valid passwords. Click "Reset my password." Verify that you get the "Password Reset" screen.
Enter your username and your new password and click "Log in". Verify that you are logged in correctly. If you wish, go to the "My Account" link in the personal toolbar and change your password back to what it was before.
PREFERENCES
Log into the system (http://bokken.cnx.rice.edu/). Click "My Account" near the top right. Verify that you get the "My Account" page.
Click "Personal Preferences", and verify that you get a preferences screen with personal information fields.
Change each field to something new and distinctive (e.g., add titles, add or remove your middle name, use different versions of your first name, etc.).
Log out of the system by clicking the "Log out" button near the top right, then log in again. Click the "My Account" link, then "Personal Preferences", and verify that your new information is still there.
PASSWORD CHANGE
[Go to My Account, then the password-change link. Do all the same tests as above under password reset: only one password, too-short password, no password at all, then enter a valid password, submit, and log out and back in with it.]
CONTENT VIEWING
BROWSE INTERFACE (informal)
Browse around at http://bokken.cnx.rice.edu/content/ and try all the options you can find. Tell Jenn to do a scripted test of all the alphabetical browse links.
SEARCH
RESULTS
Go to the Connexions front page (http://bokken.cnx.rice.edu/) and make sure that you are logged out of the system. Enter "zzyyxx" in the search box at the top of the search page. Verify that no results are found and that nothing breaks because of it.
Enter a general, well-represented search term (e.g., DSP, image, music). Verify that you get results (e.g., there should be well over 100 results from "DSP").
WEIGHTINGS (test server only)
Decide on (or invent) an obscure word or string that doesn't appear in the Connexions repository. Verify its absence by searching for it at http://bokken.cnx.rice.edu/content/search, and verifying that there are no results.
Log into the system, and enter a workgroup. Create modules and/or add modules to the workgroup until you have four modules you have permission to publish; a mixture of preexisting and new modules is ideal.
Edit the modules so that one of them has the test word in its title, one has it as a keyword, and one has it in its text. Publish all four modules. Then enter the test word in the search box at the top right of any Connexions page, and verify that the four modules are returned in that order (title, keyword, text).
Choose a five-digit module number and search for it in the search interface. Verify that it only returns the single module. If anything else is returned, choose another module number, until you find one that only returns itself.
Return to the workgroup you were just using, and add or create four courses that you can edit.
Add your five-digit test module to one of the courses. On another of the courses, edit the course title so that it includes the five-digit module id. Add the module id to another of the courses as the course's institution. Finally, add the id to one of the courses's abstracts. Publish the courses, then search for the test module id. Verify that the five courses are returned, in the above order (added module, title, institution, abstract).
MATCHING (informal/incomplete)
%%%%% Since the numerical weights of search results are no longer displayed, this has gotten harder to do, but try running each of the searches below and note anything unusual you find. In general, module results should be sorted by the presence of the search term in the title, then the authors and keywords, then the abstract, and finally the text. Course results should sort by module IDs? they contain, then by title, keywords/institutions/authors, and then by abstracts.
Firstname search for modules Lastname search for modules Email username search for modules Personid search for modules Moduleid search for modules Title search for modules Keyword search for modules
ADD-TO-WORKGROUP
Enter an existing workgroup you can use for testing. (http://bokken.cnx.rice.edu/, then log in and select a workgroup from the left-hand sidebar.)
Click the "Search for published content" button above the item listing. Verify that you are sent to the general Connexions search page.
Enter a search term in the search box and click "Search". Click the empty checkbox at the top of the first column and verify that all the boxes become checked. [BUG: At least one tester thought it was a bug that the top box didn't become checked with the rest.]
Verify that the name of the workgroup you were most recently using appears in the select box after "Add selected objects to:".
Pull down the select box and verify that all your workgroups, plus your personal workspace, appear in the list. Click "Add". Verify that you are taken back to the correct workgroup's main page, and that the modules have appeared in the workgroup.
Search for a term that returns only one item; a collection ID like col10040 is a good bet. Verify that, when only one search result is returned, the checkbox next to it is automatically checked for you.
Tell Jenn to run her automated unicode and punctuation search tests.
SIMILARITY (incomplete)
Go to a random module (http://bokken.cnx.rice.edu/content/randomContent; try again if you get a course). Verify that it has a "Similar Content" section in its sidebar.
Click one of the objects listed as similar, then do the same on the resulting object; do this several times to navigate through the "web" of similarities.
On a module that has a "More" link in its similarity section, click that link and verify that it goes to a larger list of similar objects.
Do a basic search from the main search box, and click the "Similar Content" link in one of the results. Keep clicking "Similar Content" links in the results a few times to make sure nothing breaks.
From the similar content page, enter a search term and search for similar content. Verify that you stay on the similar content listing, and don't go back to the main search system.
SITE DESIGN (informal)
Hit the tech blog's RSS.
Read the "more news" link Click one of the "recently revised" object links
AUTHOR INTERFACE
WORKGROUPS
Log in to the author interface (http://bokken.cnx.rice.edu/). Click a group workspace name in the left sidebar. Verify that in the group workspace, you have Contents, Properties, and Members tabs (and only those tabs).
CREATION (automated!) (but then make sure the new module has a CC v2.0 license)
DELETION
Enter a workgroup that has some stuff in it. Note the ID of the workgroup. Click the "Members" tab. Click the checkboxes next to all the names including yours, and click "Remove selected users from group". Verify that the confirmation page warns you that the workgroup is about to be deleted.
Click the "Yes, Delete it" button. Verify that you are taken back to your personal workspace and that the test workgroup does not appear in the list of workgroups in the left-hand sidebar.
Enter a different workgroup (not your personal workspace). Edit the URL in the location bar to change the number of the workgroup back to the number of the one you just deleted. Verify that you get a "Resource not found" site error.
PROPERTIES
Enter a workgroup's Members tab, and click the "(email group)" link next to the heading "Current Group Members". Verify that it at least tries to launch a local mail program, and that the To addresses appear correctly if it does.
Click the "Properties" tab for the workgroup, and enter your email address in the "email" field. Click "Update" and verify that you are taken back to the top level of the workgroup.
Click the "Members" tab and mouse over the "(email group)" link again. Verify that this time the status bar shows "mailto:![your address]".
MEMBERSHIP
Enter or create a workgroup that has multiple members. Click the "Members" tab. Verify that you get the "Members of: [workgroup name]" page.
Move the mouse pointer over the email address listed for one of the members. Verify that the email link is of the form "mailto:![valid email address]" and matches the email address that is displayed.
In the search box, type a relatively uncommon two-letter combination that appears in your name (e.g., "ru" for Drummond) and click "Search". Verify that the search results are limited to people with that letter combination in their names.
Page through the results using the "Next" links and/or the number links, and verify that your name does not appear in the results (since you're already in the workgroup). Report it if searching is unusually slow.
Check at least two of the checkboxes next to users in the search results and click "Add selected users". Verify that the accounts appear in the "Current Group Members" table at the bottom of the page.
Look at the search results and verify that the search term you entered is still in effect, and that the same section of results is still showing, but without the users you just added to the workgroup.
Make a rough mental note of some of the names showing in the search results. Then, in the "Current Group Members" section, check the checkboxes by at least two accounts and click "Remove selected users from group". Verify that the accounts disappear from the table of current members. The set of users showing in the search may shift slightly as the users you removed are added back into the search results.
Click a search-result navigation link [BUG: may try to do another delete and cause a traceback]
LEAVE A WORKGROUP
Enter (or generate) a workgroup that contains both your account and a test account. Log in as the test account, and enter the workgroup in question. Click the "Members" tab to get the membership editing screen. Click the checkbox next to the name of the test account you're logged in as, and click "Remove selected users from group". Verify that you get the "Leave Workgroup: [workgroup name]" page, with a confirmation warning that you won't be able to rejoin the group after you leave.
Click "Yes, Leave". Verify that you are sent to the test account's personal workspace, and that the workgroup you just left no longer appears in the list of workgroups in the left sidebar. Log out of the test account.
Log back in with your own account. Look at your list of workgroups on the right to verify that the workgroup in question still exists.
Click the name of the workgroup, then click the "Members" tab. Verify that the test account is no longer listed as a member.
OBJECT MANAGEMENT
OBJECT LISTING
Enter or create a workgroup with examples of all object types (course, module, file, image). Verify that there are columns for an object's title, ID, size, modification time, and publication state.
Note any ugly or otherwise unfortunate wrapping, crowding, or other usability problems you see.
Verify that there is a size listed for every object type but courses.
Verify that the modification column contains some sort of timestamp, not just a date, and that it's in an understandable format.
Verify that only modules and courses have a state listed.
CREATION
Enter a workgroup and open the dropdown next to the "Create New Item" button. Verify that the options Course, File, Image, and Module appear, in that order.
Without selecting an option, close the dropdown. Click "Create New Item". Verify that you get an "Add New Item" page [BUG: this should match the button, and be titled Create New Item].
Verify that the page lists the four object types in the same order as above, with the appropriate icons and descriptions that more or less make sense. [BUG: the descriptions of the types are awful.]
Click the "Add Item" button next to Course and verify that you get the license approval page. Abort the creation of the course by returning to the workgroup level with one of the workgroup navigation links, and verify that there has not been a new course created.
SORTING
Enter or create a workgroup that contains both modules and courses. Click the "Modified" heading in the table. Verify that the sort order of the items changes, and that the modification times are sorted in ascending order. Verify that a downward-pointing blue triangle appears after the "Modified" title.
Click "Modified" again. Verify that the sort order is reversed and that the blue triangle changes to point up.
CUT/COPY/PASTE/REMOVE
(Keep an eye out for Paste buttons that are colored blue instead of white, and report them if you find them.)
Enter or create a workgroup with examples of all object types (course, module, file, image). Select one file or image, and one module or course. Click "Remove" and verify that both objects disappear.
Click the checkbox next to a file or image to select it, and click "Copy". Verify that the object you copied is still in the list, and that there is now a "Paste" button below the list.
Click "Paste". Verify that a new object is added to the list with a name of "copy_of_[original object name]".
Click the checkboxes next to one file or image and one module or course. Click "Copy" and verify that you get an error saying that some types of objects (modules and courses) can't be copied. [BUG #1475: can copy modules] Select one file and one image instead, and click "Copy". Verify that neither item disappears from the list.
Click the name of a module to enter its file listing. Verify that there is a "Paste" button showing at the bottom of the listing.
Click "Paste" and verify that the file and image appear. Click the name of the image file and verify that it displays properly.
Return to the workgroup level, select one or more files/images and one or more modules, and click "Cut".
Change to a different workgroup and click "Paste". Verify that the objects you cut from the first workgroup appear in the workgroup you've changed into.
Change back to the first workgroup and verify that the cut objects have disappeared. Click on a module title and verify that you get the "Manage Files" page for the module.
Click on the title of another workgroup in the left sidebar. If there is not at least one course and one module present, add or create some. Click the checkboxes next to a module and a course, and click "Copy". Verify that you get an "Item(s) copied" message.
Click "Paste" and verify that you get an error saying that objects cannot be duplicated within a workgroup [BUG #1475: they can] Change to a different workgroup and click "Paste". Verify that the objects appear.
RENAMING
Enter or create a workgroup with examples of all object types (course, module, file, image). Click the checkboxes next to one file object and one image object, and click "Rename". Verify that you get the "Rename item" page.
Click "Rename All" without changing anything. Verify that you are taken back to the main workgroup page [BUG: you are, but it's in contents view. Click the "Files" tab to get back to Item view.] [May not still be true under plone2; is it?] Click the same checkboxes again and click "Rename". Change the actual filename of one or both items, and add a description (title) to one of them. Click "Rename All". Verify that it worked.
FILES
IMAGE/FILE UPLOAD AND EDITING
Log in to the system (http://bokken.cnx.rice.edu/). Enter an existing workgroup you can use for testing. Select "File" from the dropdown, and click "Create New Item". Click "Browse" to choose a file to upload from your local machine or network. Choose a non-web-displayable (e.g., exe, doc, ppt, zip, tar) file to upload. Click "Save" to upload the file. Verify that you get a page accurately listing the name, size and type of the file, with a message that "File changes have been saved."
Click the "Edit" tab. Click "Browse" and choose a file of a different type than the one you just uploaded. Click the "Click here to get the file" link and verify that you are offered a download of the right MIME type.
Return to the workgroup level and upload a text file as a "File" object. When it's uploaded, click the "Click here to get the file" link and verify that the file renders as you would expect over the web (e.g., plain text display, rendered HTML, or styled XML depending on the browser).
Click the "Edit" tab. Verify that the text of the file appears in an editable textarea. Make a change to the text and click "Save". Verify that you are taken back to the "View" page, and that the change you made is visible in the blue text display.
Return to the workgroup level, select "Image" from the dropdown, and upload a web-displayable image.
Return to the workgroup level again. Verify that the files you uploaded appear in the workgroup list with bluish icons, and that the images have yellowish icons. Verify that the metadata showing for the files at the workgroup level is correct.
Choose "Image" from the dropdown again and click "Create New Item". Click "Browse...", and this time try to upload a very large file of any type (over ten megs; a Mozilla installer or other archive works well). Verify that you get a fairly ugly error that "The request or reply is too large."
Return to the workgroup level again, and click the "Members" tab. If no test account to which you have access is listed as a member, search for a test account and add it to the workgroup. Log out of the system, log back in as the test account, and enter the workgroup you've been using.
Click the name of one of the text-based files you uploaded. Verify that you get the file's "View" page, and that the file displays correctly on the page.
Log out of the test account and log in again with your own account. Re-enter the workgroup you've been using. If there is a module there that you can use for testing, click on it, and check it out if necessary. If not, add a test module to the workgroup and click on its title.
On the main "Manage Files" page of the module, click the "Add New Item" button without selecting an object type from the dropdown box. Verify that you get a list of object types (CNXML Document, File, and Image).
Click the "Add" button under "File". Verify that you get the "Edit File" page. Click "Browse" to choose a file to upload, then click "Save".
Return to the module level. Verify that the file you uploaded appears in the files list.
LINKS
AUTHOR LINKS
Enter a checked-out test module to which you can freely submit changes. Click the "Links" tab for the module. At the bottom in the "Add New Link" section, click "Add" without entering anything. Verify that you get an error message explaining what you need to enter.
In the "Add New Link" form, type something like "The Grand Connexions Test Module" in the "Link Name" box. In "Module ID", type "m9003". Leave the type and strength at the defaults and click "Add". Verify that you get the "Link added" message and that the new link appears in editable form under "Existing Links" (with a URL ending in m9003/latest/).
Again in the "New Link" area at the bottom, enter a name of "Old Tutorial Module", a module ID of "m9000", and a version number of "2.21". Make the link type "Prerequisite" and the strength "3". Click "Add". Verify that the URL that appears for the link in the editing area at the top ends in "m9000/2.21".
Add another link, this time with a name of "Rice University", a URL of "www.rice.edu" (no http), link type "Example", and strength "5". Click "Add". Verify that something catches the missing-http problem [BUG #1522: nothing does] Click the "VISIT" link next to the URL of module 9000. Scroll down a screen or two to the section called "name". Verify that the first line contains the phrase "the name of it's parent", which is a typo that has been corrected in the current version. Go "back".
Edit the title and link type of the first link, and the URL and strength of the third link, making a note of what you're changing them to. Check the "delete" box next to the second link. Click "Update Links". Verify that the changes remain, and that the second link has disappeared. Note the new types and strengths.
Submit the module (click the "Publish" link in the sidebar, enter a commit message like "Added links", and click "Publish"). At the module status page, click the module title and verify that the links appear in the "Links" section at the top left of the module. Click on each of them to verify that they work, then go "back".
Check out the module. Click the "Links" tab and verify that the links you entered before are still present. Verify that the link types and strengths are the same as when you submitted the module.
INSTRUCTOR LINKS
Add to a workgroup a course whose modules already contain author links. The CNXML Tutorial course, or some of Kitty Jones's courses, are good examples. Preview the course with the "Online" link in the right-hand sidebar, enter the course, and page through it with the "Next" link until you find a module with at least four links. Briefly note their types and strengths.
Return to the course-editing page by clicking the "Table of Contents" link on the module you're viewing. Click the name of the module you were just on, and click its grey "Links" tab. Verify that there are links there matching the ones in the preview, and that the types and strengths are accurate.
Click the "Delete" box next to a link, make a note of its title, and click "Update Links". Verify that it disappears.
Preview the course with the "Online" link in the right-hand sidebar, and verify that the link you deleted is gone.
OBJECT ROLES
Enter a checked-out object (course or module) you already have at least maintainer access to and can use for testing. Go to the Roles tab and search for the name of the test account you will be using. Click the checkbox next to the name of the test account when it appears, and click "Add people". Verify that the test account appears in a yellow table titled "Roles pending approval".
Click the "(help)" link next to the title "Roles pending approval" and verify that it takes you to a page describing the roles available in Connexions.
In the right-hand sidebar, click "Publish". Type some gibberish into the commit-message textarea and click "Publish". Verify that you are returned to the roles page with a message that you can't submit a object with pending role requests.
In the bottom table, uncheck the "Author" and "Copyright Holder" checkboxes next to the test account so that it is only listed as a maintainer, and click "Update Roles". Verify that the form reloads with only the maintainer box checked.
If you have access to a second browser (not just a second window), open it and log into the system as the test account. If not, log out of the system and log back in as the test account.
As the test account, look at the top of the right-hand sidebar. Verify that you see the "Pending" box, and that it says you have "1 Role Request". Click the "Role Request" link in the "Pending" box in the sidebar. Verify that you are taken to the "Collaboration Requests" page, and that there is a listing under "Requests Awaiting Your Approval".
Click the checkbox next to the role request, then the "I accept the license(s)" checkbox, and click "Accept". Verify that the role-request page reloads without the request showing and that you get an "Accepted roles" message.
Switch back to the browser with your own account (or log out and back in as yourself) and return to the object you're testing with. Click "Publish" in the right-hand sidebar, type a commit message like "Added test account", and click the "Publish" button. View the object and verify that the test account is listed as a maintainer.
MODULE AUTHORING
CREATION (automated!)
DISCARD
Enter a module and make noticeable changes to it, like those described above in requirement "Edit metadata" (changes in text, title, keywords, abstract).
Return to the module level if you haven't already. Click one of the tabs other than "Files". Click the "Discard" link in the sidebar. Verify that you get the discard confirmation screen.
- Click "No, Cancel". Verify that:
You are returned to the tab you just left [BUG: you always get "Files"]
The state of the module (as displayed in the right sidebar) is still "Modified".
Click the "Discard" link again, then click "Yes, Discard" to confirm. Verify that you get a page listing the module's metadata, and that the state of the module in the right-hand sidebar is now "Published", with "Last action" of "discard".
Click the name of the workgroup in the breadcrumb bar to get to the main workgroup page. Choose "Module" from the dropdown and click "Add New Item". Go through the creation process, and at the end, change the title from "(Untitled)" to something else. Then click the "Discard" link in the sidebar. Verify that you get a confirmation screen with three buttons: Discard, Delete, and Cancel.
Click "Cancel" and verify that you are returned to the page you left [BUG], with a module state of "Created" showing in the right-hand sidebar.
Click the "Discard" link again. Click the orange "Discard" button. Verify that you are taken back to the "Manage Files: [module name]" screen, and that the name of the module has reverted to "(Untitled)". Verify that the state is "Created" and the last action "discard".
Click the "Discard" link again. This time, click the "Delete" button. Verify that you are returned to the workgroup's main page and that the module you created does not appear.
EDITING IN INTERFACE
WEB FORM EDITING
Enter a checked-out module, then click the "index.cnxml" link to enter the editing form. Make a textual change to the first paragraph or other tag at the top of the "content" or "document" section. Click "Save". Verify that the change has persisted in the textarea.
Look at the right-hand sidebar and verify that the module's status has changed to "Modified" [BUG: editing text doesn't do this currently] Click the "Preview" tab. Verify that your change appears in the previewed module. Go "back".
DOWNLOAD/UPLOAD EDITING
Enter a checked-out module for editing, then click the "index.cnxml" link. Verify that you have a "Download a copy" link.
Click the "Download a copy" link. Save the index.cnxml file it gives you to a place on your local machine. Open the index.cnxml file in your manual CNXML editor of choice (e.g., emacs or Textpad; don't use XMLSpy?). Verify that the complete file has been loaded (check for opening and closing module or document tags).
Make a change to the text and save the file. Click "Browse..." on the module-editing web page and choose the updated file. Click "Upload". Verify that you get the same web page, and that the text of the module in the textarea reflects the changes you made to the file on your local system.
Click the "Preview" tab and verify that the changes you uploaded appear in the previewed module.
IMPORT/EXPORT EDITING
Bring up the XMLSpy? editing instruction module (http://bokken.cnx.rice.edu/content/m11160/latest/) in a browser. Click the "CNXML Style File" link in the first named section and verify that it is offered to you for download.
Make sure you're on a machine that has some version of XMLSpy? (most of Connexions' shared Windows machines have it). Enter a checked-out module, and click the (import/export) link next to index.cnxml's row. Verify that you get an "Import/Export: index.cnxml" page.
Click the Export button and save the offered file to your local machine. Open it with XMLSpy? or the equivalent. Verify that it opens without errors.
Make some changes to the content of the module. Hints may be found at http://cnx.rice.edu/content/m11160/latest/. Save the file, and return to your browser, which should still be on the import/export page. Click the "Browse..." button, select the edited file from your system, and click "Import" to upload it. Verify that you are returned to the file-editing page, with a successful validation.
Look in the textarea and verify that your changes appear in the cnxml file.
VALIDATION
Bring up a checked-out module in editing view. Verify that there is a light green bar under the "Edit CNXML File: index.cnxml" header that says "Validation results: File OK".
- In the textarea, make a change that invalidates the CNXML. Suggestions:
- Make a change in the spelling of a tag, e.g., </content> to </conten>, OR Remove everything between the opening and closing content tags, OR Delete the DOCTYPE declaration at the top of the file.
Click "Save". Verify that a light red box at the top of the page appears with error text which (more or less) describes the error you introduced.
Uncheck the "Validate during save" checkbox and click "Save". Verify that neither the red box nor the green "OK" bar appear.
Use the textarea to fix the invalidating change you made and click "Save". Verify again that neither the red box nor the green "OK" bar appear.
Recheck the "Validate during save" checkbox and click "Save". Verify that the green bar that says "Validation results: File OK" returns.
Download the file to your local machine by using the "Download a copy" link. Edit it in your manual CNXML editor of choice (e.g., emacs, not XMLSpy?) to introduce a different error. Save the file. Click "Browse..." on the module-editing web page and choose the updated file. Click "Upload". Verify that you get a red validation error.
Use the textarea to undo the change you made. Click "Save". Verify that the red box changes back to the green bar.
METADATA
Enter a checked-out module you can use for testing. Click on the "Metadata" tab. Make obvious changes to the title, keywords, and abstract (e.g., insert the word "TEST" in all caps in the middle of the title and abstract, and add a keyword of "TEST") to verify that all the form fields behave properly.
Click "Save". Verify that you get the metadata-editing screen back, and that the changes have been retained correctly in the form fields.
Click the "Preview" tab, then "Online Preview". Verify that the changes you made to the title and abstract show up.
Click the "More about this content" link on the previewed module, and verify that the keywords are formatted as a tidy string of comma-separated terms.
Return to the author interface, click the "Preview" tab, then the "Print Preview" link. View the PDF. Verify that your changes to the title and abstract appear in the previewed version, and that the new role information is listed accurately under the title. Go "back", or otherwise close the PDF.
Click the "Online" link in the sidebar to make sure you get the same preview. Click the "Print" link in the sidebar to make sure you get the same PDF.
DIFF VIEW
Enter a freshly checked-out module in a workgroup. Click the "Changes" link in the right-hand sidebar, at the bottom under "View". Verify that you get the "Change Set" screen, and that "Changed Files", "Removed Files", and "Added Files" are listed with "None" under each.
Click on the module's title in the breadcrumbs, then click its Metadata tab. Make a change to the title of the module and click "Save".
Go to the module's text-editing page and make a change to the text of the module. Click "Save", then the "Changes" link in the sidebar. Verify that there is now an entry above "Changed Files" for "title" [BUGLET: should be capitalized]. Verify that the old title appears with a minus next to it, and that the new title appears with a plus next to it. Verify also that there is now an entry for "index.cnxml" under "Changed files".
Click the "index.cnxml" link and verify that you get another "Change Set" screen with a subheading of "data". Verify that there is one plus/minus pair for the "name" tag of the module, and one for the "md:revised" tag.
Scroll to the the file's content and look for the lines you changed; verify that they are marked as changes.
Click the "Discard" link in the sidebar under "Actions", then click "Yes, Discard". Verify that the title, abstract, and keyword changes have disappeared from the metadata listing you get. Verify that there is no longer a "Changes" link under "View" in the sidebar.
Click "Checkout", then the "Changes" link. Verify that the changeset is blank again.
SOURCE VIEW
Enter a modified module. In the right-hand sidebar, click the "Source" link after the word "View". Verify that you get a screen showing the CNXML source of the module in a blue box with line numbers. Verify that the changes in the module appear in this version of the source.
Click the "Hide line numbers" link. Verify that the same source text appears without line numbers.
Click the "Show line numbers" link. Verify that the line numbers come back.
Click the "Discard" link in the sidebar. Click "Yes, Discard" to confirm. Click the "Source" link in the sidebar and verify that you get the source of the published module.
PATCHING
Submit a patch to Crouton and have him (it?) accept it.EDIT-IN-PLACE (needs expansion)
%%%%% Do this once in Firefox and once in IE.
Make sure you're logged out of the author interface. View a module that you have permission to edit, and click the sidebar link that says "Edit this module (login required)". Verify that you are taken to the author login.
Log in with your own username and password. Verify that you get the edit-in-place version of the module, which is grey with white boxes around the paragraphs and with a text box at the top in a blue area.
Single-click somewhere in the middle of the text of a paragraph. Verify that the paragraph pops up in a text box surrouded by a blue instruction box with "Preview" and "Revert" buttons, and that the <para> tags appear outside the text box.
Click "Revert". Verify that the original white paragraph comes back.
Click again in the same paragraph. Make a noticeable change to the text, and click "Preview". Verify that the paragraph is rendered with your change, and that it is now light yellow with a red border to indicate that it has been edited.
Click again in the paragraph. Make another noticeable change. This time, click "Revert". Verify that the change is not made, but that the first change, from above, is still there (i.e., that changes from previous edits are not lost on reversion).
Click the "Back" button, and verify that a warning dialog pops up to say that you'll lose your edits if you leave the page.
Click "Cancel" and verify that everything stays just like it was.
Use a bookmark, or the browser's "Home" command. Verify that you get the same dialog.
Click "OK" to abandon your changes. Verify that you go to the web site you requested.
Bring up the same module you were just editing, and verify that nothing has changed.
Click "Edit this module" again. Find a paragraph with a smaller box inside it, e.g., a list or an equation. Click within that box and verify that you get a blue box with the appropriate surrounding tags. Make a structural change inside the box, like adding another list item or another math term. Click "Preview" and verify that the change is made.
Make a change that invalidates the module. Good choices might be: removing the contents of a list, or deleting a large random swath out of a chunk of math. Click "Preview". Verify that a separate window pops up with a message that "The XML you submitted was invalid", with specific errors displayed.
Close the extra window to return to the main one. Click "Revert" to get rid of the invalidating change. Verify that you get the unchanged portion of the module back.
Click the "Publish" button at the top of the page and verify that you get a pop-up box telling you to enter a commit message. Click "OK" to dismiss it.
Type a submit message (like "Testing edit-in-place") in the textarea at the top of the page, and click "Publish". Verify that you are taken immediately to the standard display version of the module.
Inspect the module and look for the changes you made. Verify that they appear in the displayed module.
Click the "More about this content" link for the module. Verify that the version number has increased by 1 (actually, by 0.1) from the one you noted earlier.
Click the "Edit this module" link in the sidebar again. Click a paragraph, make a change, and click "Preview" to save it. Click "Discard" at the top. Verify that you get a confirmation dialog box.
Click "Cancel". Verify that you stay on the edit-in-place page and that your change is still present.
Click "Discard" again. This time, click "OK" in the confirmation dialog. Verify that you are taken to the display view of the module.
Click the "More about this content" link for the module and verify that the version number has not increased from the last time you looked.
View a module that you do not have permission to edit. Click the "Edit this module" link. Verify that you get an "Insufficient Privileges" error.
COURSE AUTHORING
PUBLISHED STATUS PAGE METADATA LAYOUT SECTIONS PMRS NAV TREE OBJECT CUT/COPY/PASTE/REMOVE SEARCHING PARAMETER SELECTION CHECKOUT/PUBLISHING DISCARD
FORKING
MODULES
Fork a module, change its title, and publish it. Check that the original author(s) and "based on" information is correct on the main module view, the metadata page, and the print version.
COURSES
Fork a course, change its title, and publish it. Check that the original author(s) and "based on" information is correct on the table of contents view and on the metadata page.
ANNOTATIONS
STUDENT
Open a copy of Mozilla with the roadmap. View a course (http://bokken.cnx.rice.edu/content/randomContent?portal_type=Collection). Verify that the course table of contents opens in the roadmap sidebar.
Click on one of the course's modules. Make some annotations using the roadmap. Go to another random course, then go to http://bokken.cnx.rice.edu/content/browse_course_titles and return to the one you were on before. Check that your annotations are still there.
INSTRUCTOR
Enter a course you can edit and publish, preferably one that already has some instructor annotations. Fork the CNXML Tutorial if that's the easiest way.
Go to a module with instructor annotations. Click on one and change something about it. Add an annotation elsewhere in the module. If there's another preexisting annotation, delete one.
Publish the course and log out. Go to the course as a student, find the annotated module, and verify that the annotation changes are there.
LICENSING
(basics are covered in object creation)
DOCUMENTATION
Without logging in, follow each link on the main cnx page (http://bokken.cnx.rice.edu) within reason and make sure it goes to the expected place.
ADMINISTRATION
NEW USER ACCOUNT EMAIL
Ask Elvena if she's been getting her new-user-account notification email lately, and report it as a bug if she hasn't. If she's not immediately available, just return this item unchecked, and someone else will do it later.
WEEKLY SUBMISSION REPORT TO CONTENT TEAM
Go to http://bokken.cnx.rice.edu/content/weeklySubmits. Verify that you get a text page with a list of the past week's submission activity.