Manual Functional Testing: Difference between revisions

From GNU MediaGoblin Wiki
Jump to navigation Jump to search
m (New section filler)
Line 174: Line 174:


You can copy-and-paste the test steps to include with the bug report to make things easier to debug.
You can copy-and-paste the test steps to include with the bug report to make things easier to debug.

== Where to run this suite ==
TODO: Fill this out.

Revision as of 04:57, 20 September 2013

Manual testing is a great way to help out MediaGoblin when we're preparing for a new release. It can also help you get familiar with how MediaGoblin works and what it's all about. That is where this functional test suite comes in. Completing the tests from this suite can help us to know that our existing functionality is intact and the perspective of the new testers can help identify potential issues where ones had not previously been identified.

Test template

All the test cases share the following format. If you come up with a new test case to add please use this format.

Test Title

Prerequisites: (This is what a test needs before it runs.) Ex - Image plug-in enabled. Activated user account. An image available for upload

Regression: (Yes if the functionality existed in the previous release otherwise it is set to no. All test cases should eventually be regression tests.) Ex - Yes

Steps: (These don't need to be exactly step-by-step but rather more general) Ex -

  1. Login to MediaGoblin
  2. Click on the Add Media button
  3. Select an image.
  4. Give it a title, description, and appropriate tags. Select a license.
  5. Press submit

Expected results: (This should be more specific than the steps.) Ex -

  • A message telling you the item was submitted.
  • The uploaded item has all of the information from step 4 (title, description, tags, license) and the image from step 3 displayed correctly when clicked on.

Copyable format

==== Title ====
'''Prerequisites:''' 

'''Regression:''' 

'''Steps:''' 
# 
# 

'''Expected results:''' 
* 
*

Test suite

Core

Create Account

Prerequisites: No user account created with selected username.

Regression: Yes

Steps:

  1. Go to Mediagoblin.
  2. Click on the Create account button.
  3. Enter a username.
  4. Enter a password
  5. Enter a valid e-mail address

Expected results:

  • A message telling you that email verification is needed is displayed.
  • If the instance is in debug mode:
    • An e-mail message appears on the console
  • Else:
    • You receive an e-mail

Create a Pre-Existing Account

Prerequisites: A username for an existing account.

Regression: Yes

Steps:

  1. Go to Mediagoblin.
  2. Click on the Create account button.
  3. Enter the username.
  4. Enter a password
  5. Enter a valid e-mail address

Expected results:

  • A message telling you that a user with that name already exists.


Media types

Images

Prerequisites: Activated user account. Image plug-in enabled.

Regression: Yes

Steps:

  1. Login to MediaGoblin
  2. Click on the Add Media button
  3. Select your image file.
  4. Give your media item a title, description, and appropriate tags. Select a license.
  5. Press submit

Expected results:

  • A message telling you the item was submitted.
  • The uploaded item has all of the information from step 4 (title, description, tags, license) and the image from step 3 displayed correctly when clicked on.


WebM Video

Prerequisites: Activated user account. Video plug-in enabled. WebM VP8/Vorbis video available for upload.

Regression: Yes

Steps:

  1. Login to Mediagoblin
  2. Click on the Add Media button
  3. Select your WebM video file
  4. Give your media item a title, description, and appropriate tags. Select a license.
  5. Press submit

Expected results:

  • A message telling you the item was submitted.
  • The uploaded item has all of the information from step 4 (title, description, tags, license) and the image from step 3 displayed correctly when clicked on.
  • The video should not have been transcoded.


Other Video

Prerequisites: Activated user account. Video plug-in enabled. Video available for upload (not WebM format)

Regression: Yes

Steps:

  1. Login to Mediagoblin
  2. Click on the Add Media button
  3. Select your video file
  4. Give your media item a title, description, and appropriate tags. Select a license.
  5. Press submit

Expected results:

  • A message telling you the item was submitted.
  • The uploaded item has all of the information from step 4 (title, description, tags, license) and the image from step 3 displayed correctly when clicked on.
  • The video should have been transcoded to WebM


Ogg Audio

Prerequisites: Activated user account. Audio plug-in enabled. Ogg/Vorbis audio file available for upload.

Regression: Yes

Steps:

  1. Login to Mediagoblin
  2. Click on the Add Media button
  3. Select your Ogg/Vorbis audio file
  4. Give your media item a title, description, and appropriate tags. Select a license.
  5. Press submit

Expected results:

  • A message telling you the item was submitted.
  • The uploaded item has all of the information from step 4 (title, description, tags, license) and the image from step 3 displayed correctly when clicked on.
  • The audio file should not have been transcoded.


Other Audio

Prerequisites: Activated user account. Audio plug-in enabled. Audio file available for upload (not Ogg/Vorbis format)

Regression: Yes

Steps:

  1. Login to Mediagoblin
  2. Click on the Add Media button
  3. Select your audio file
  4. Give your media item a title, description, and appropriate tags. Select a license.
  5. Press submit

Expected results:

  • A message telling you the item was submitted.
  • The uploaded item has all of the information from step 4 (title, description, tags, license) and the image from step 3 displayed correctly when clicked on.
  • The audio file should have been transcoded to Ogg/Vorbis.

Reporting bugs from this test suite

See: File Bugs

Any bugs you find with this test suite should be reported at http://issues.mediagoblin.org.

In addition to following the existing issues guidelines make sure to include the word "testsuite" as a keyword on your bug report. This also will help with the search process since you can search using the keyword "testsuite" to see if your specific issue has already been reported. If it has and you have additional information to provide, leave a comment on the ticket.

You can copy-and-paste the test steps to include with the bug report to make things easier to debug.

Where to run this suite

TODO: Fill this out.