Manual Functional Testing

From GNU MediaGoblin Wiki
Revision as of 07:54, 17 September 2013 by LotusEcho (Talk | contribs)

Jump to: navigation, search

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.

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




'''Expected results:''' 

Test suite


Media types

Reporting bugs from this test suite

See: File Bugs

Any bugs you find with this test suite should be reported at [1].

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.

Personal tools