Skip to end of metadata
Go to start of metadata

Introduction

This is parent page for the tDAR functional tests.  After reviewing this page, a good place to start is the "Test Plan Matrix".

Prerequisites

  • All testing should occur on the tDAR staging server
  • While running the tests, it's a good idea to make sure that your browser is set up to show javascript errors (see "configuring a browser to show javascript errors" )
  • In addition to your main tDAR account, you should also create additional "throw away" accounts in order to run tests that involve rights and permissions
    • Mailinator is an awesome for throw-away accounts.  There is no need to "register" an acccount with them – simply start using the email address (aka bobs-editor-account@mailinator.com).  
    • If you ever need to change/reset your tDAR password, you can retrieve it at mailinator by using the convention http://bobs-editor-account@mailinator.ocm)

About the Tests

Stuff To Look For In All Tests

  • (New in Grid) Compatibility warnings. Unless you are using IE6 or IE7, you should not see a banner on the dashboard page warning about compatibility.
  • Font sizes/colors that are too large/small in certain browsers, or look out of place relative to how they appear in other browser versions.
  • Broken links
  • Javascript errors. It is important to report javascript errors even if you are seemingly able to perform the actions in these tests.
  • Broken images
  • Formatting issues
  • Misspellings

Feature Tests (aka "What's New In Grid")

Feature tests only cover the new features in the to-be-released version of tDAR. These require more thorough testing across many browser types. Once the new version of tDAR is deployed, they will be rolled into the existing test suite.

Tests for Grid release:

  • Ability to link dataset records to information resource metadata
  • Profile management  (modify profile information, reset/change password)
  • Instituion, Person record editing
  • Site usage metrics (see "stats" in the admin menu)
  • Improved dataset column mapping UI
  • Persistent ID's (DOI)
  • Improved authority management functionality  
  • Numerous client and server performance improvements

Configuring a Browser To Show Javascript errors:

Chrome / Safari

  • Enable web developer menu with Console
  • (Chrome Only) Install the Javascript Errors Notifier extension.  This is a great way to easily see if a page experiences an error without without taking up a lot of space.

Firefox:

Enable Javascript console

Internet Explorer:

Turn on script error notification : http://www.testingreflections.com/node/view/4009

Labels
  • None