You're viewing old version number 19. - Current version

4 min

Junco end-user testing

Manually testing the Junco Web app.

  • visit "homepage"
    • fix the display issue of this page on IE v8
    • ensure that all footer links and info work properly:
      • about - help - contact - archives - tags - search
      • home page link at bottom
      • current date and time info at bottom
  • (signup - Signup - show_signup_form)
  • click the blue sign-up button.
  • (createnewuser - Signup - create_new_user)
  • enter valid, unique username
  • enter valid, unique e-mail address
  • test entering invalid username and e-mail address:
    • too short (min len?)
    • too long (max len?)
    • unacceptable characters (username only accepts alphanumeric and underscore) verify
    • invalid e-mail syntax
  • after signing-up with valid username and e-mail address, test:
    • sending of e-mail with activation link (enable/add code)
    • clicking the activation link to activate account
    • system automatically creates password for initial account creation, verify password in e-mail.
  • if running in debug mode, the auto-generated password and the activation link are displayed immediately after entering username and e-mail address info. when in debug, a valid, functioning e-mail address is not required. the e-mail still needs to have valid syntax, such as x@x.com and username and e-mail still need to be unique, but the system does not send a message to the e-mail address given.
  • (acct - Signup - activate_account)
  • click activation link, which should display login screen.
  • (login - Login - login)
  • login with e-mail address and the auto-gen password.
  • (loginform - Login - show_login_form)
  • also test logging in via the login form.
  • (user - Profile - show_user)
  • (settings - UserSettings - show_user_settings_form)
  • (changepassword - Password - change_password)
  • after successfully logging in for the first time, change password to something more meaningful and memorable.
    • click on username
    • click "Change your password, e-mail address, or description info"
    • enter old password
    • enter new password twice
    • click the "modify/password" button
  • (logout - Logout - logout)
  • after successfully changing password, logout, and then log back in with the new password.
  • then click "Change your password, e-mail address, or description info"
    • enter incorrect old password
    • enter two new passwords that do not match
    • test invalid passwords (what are the pwd requirements)
  • (customizeuser - UserSettings - customize_user)
  • (savedchanges - UserSettings - show_user_changes)
  • click on "Change your password, e-mail address, or description info"
    • change e-mail address
    • test invalid e-mail syntax
    • enter text in description area
    • when pages have been created, test using the include template function to include info from another page or post that will display on user profile page.
  • logout and then log back in by clicking "save login" checkbox.
  • close browser
  • re-open browser
  • visit website to verify that account is automatically logged into site.
  • (addmicroblog - Microblog - add_microblog)
  • create microblog post
  • (microblogpost - Microblog - show_microblog_post)
  • display microblog post
  • (deletemicroblog - Microblog - delete_microblog)
  • delete microblog post
  • (undeletemicroblog - Microblog - undelete_microblog)
  • undelete microblog post
  • create microblog post with a raw URL
    • URL should automatically be made into a clickable link
  • (tag - Search - tag_search)
  • create a microblog post with one hashtag
    • hashtag should automatically be made into a clickable link, which is a tag search result
  • create a microblog post with 8 hashtags or the max defined in config file.
  • create a microblog post with one-plus the max-allowed hashtags.
    • should receive an error
  • create a microblog post with more than the max-allowed characters.
    • should receive an error
    • example:
      • Error: 352 chars entered. Max is 300.
  • on user profile page, click on links following "Micro Blog posts:"
    • the microblog count link, which displays a stream of the user's microblog posts
    • the rss link for the user's microblog posts
  • when viewing the user's stream of microblog posts, click on "all microblog postings" to show stream of all users' microblog posts if the code is open to multiple authors
  • (blogpostform - BlogAdd - show_blog_post_form)
  • click on "post" link to get the basic textarea box for creating a blog post/article (longform post)
  • add no content and click:
    • preview button
    • post button
  • should receive error:
    • "You must enter content. You must give a title for your article."
  • click the "post" link.
  • enter content in text area box for blog post.
  • click preview button.
  • click post button.
    • the first line to the first hard return should be automatically turned into the title for the post.
  • click the "post" link for a blog post.
  • create a blog post with a lengthy bit of content but with no hard return.
    • if no hard return, the first X-number of characters will automatically be made into the title.
  • click the "post" link.
  • create a long title line with a hard return followed by body text.
    • the first X-number of characters of the title line will automatically be made into the title. (what is max number of title chars?)

#junco - #testing

From JR's : articles
779 words - 5081 chars - 4 min read
created on
updated on - #
source - versions

Related articles
Testing the new insta command - May 17, 2016
Testing fenced code block commands - Sep 23, 2014
This is a test: with the colon punct in the title - Jul 16, 2014
Junco user actions - Nov 01, 2013



A     A     A     A     A

© 2013-2017 JotHut - Online notebook

current date: May 19, 2024 - 3:48 a.m. EDT