Having a standard pattern to create and identify test data will help us filter them out from day to day live operations and reports.As creating test cases is crucial to our operation for different reasons mentioned above, mixing test data with operation data would result in false outcomes in reports and misunderstanding in processes where browsing through or inquiring about data in overall is necessary. There are other situations where this could cause unintentional misrepresentation. Some examples may include, but are not limited to, auditing and accounting.

This document is created and being reviewed as a live source for testing standards and will be updated as necessary.

Glossary


Admin: Anyone with full privilege when accessing the BB GM system

Application: Grant request that is submitted by the grantee and going through process by grantor’s administration

BB GM: Abbreviation used to refer to Blackbaud Grantmaking software

Request: Grant, Request, Application, Proposal

Standard/ Standard Rule/ Standard Testing Rule: All refer to Standard Testing Rule

Objective

The initiative leading to this document originated from the need for creating more standardized test cases in BB GM live atmosphere. As currently there is no testing setting available to us, creating test cases has to be implemented within the live environment. Test creation can be used for the following reasons:

  • In order to examine different challenges and prospective issues.
  • Re-creating a scenario in order to help resolve a user’s issue.
  • Exploring different opportunities to help our users.
  • Any other situation that needs further investigation.

Testing Template

To record the test cases and the outcomes, a template has been created. It has to be filled and saved in the following location on N drive:

N:\ADMIN\WI Partnership Program\Database & Website\Testing Data

A copy of the template is there and also attached to this Confluence page.

Application Testing Template.docm

After downloading/opening this document, you will need to click the "Enable Content" as well as "Enable Macros" to make the dropdown and date controls available..

Standard Testing Rules

The following is a suggested list that should be followed when creating testing data. The initiative understands that in specific cases, following some of the rules may not be possible in all cases, however, there should be an effort made to apply as many standard rules as possible.

Amount limit standard rule

The testing amount for requested amount and granted amount should be $12.00. If not possible with the scenario, then requested amount and granted amount as well as any one payment or the total of payments as well as any other amount within the application should not exceed 300.00USD. Requested amount and granted amount should have an amount more than 1.00 USD.

Naming Rule

For any Organization Name/Title, Template Name, Request Title, Report Name, Search Name, View Name, Blueprint Field’s Name and any documentor correspondent that will be stored in BB GM or sent out as correspondence or published to the user, prefix the name with the following:

Test –

Also, when naming anything, please search the web and our system to make sure to avoid entering a real name by accident.

Contact Rule

Contacts’ names do not need to be suffixed or follow certain pattern(s). However, for any contact that will receive correspondence, the email of the creating user should be entered except in cases where duplication causes issues. For instance, a reviewer cannot have the same email address as the other contact on the request. In those scenarios, email of another admin will be entered under email address. Also, as a best practice for courtesy, the emailed-to individual, if different than the creating user, needs to be notified to avoid any unnecessary confusion when receiving correspondence. For instance, following the amount limit rule when re-creating a 50,000 Dollars requested grant scenario to help troubleshoot a user’s case may not be reasonable, unless the issue has nothing to do with the amount.

Address Rule

The following address should be used for testing:

750 Highland Avenue, Madison, WI, 53705

The only exception is when the address is being tested.In that case, the creator’s work address would be relevant.

Personal Data Rules

Please avoid entering any real-life sensitive information including (but not limited to):

  • Date of Birth
  • Personal Address
  • Personal email
  • Social media information
  • Personal documents
  • Personal image
  • Company Name (search before to make sure they don’t exist at the time of data creation)
  • SSN/SIN/TIN-Any real tax information
  • ID number of any nature such as driver’s license, passport, SSN/SINcard, employee number, etc.
  • Any real financial information
  • Any other information that would expose real life identity

Hints and Helpful Tips

NOTE: The following hints and tips are referring to creating testing data. For clients’applications, please consult grant officers.

If there is no email address added to the contact, correspondence cannot be sent. Always add your email to the contact that will receive the correspondence.

Add the address when creating an organization and make sure the city and state are entered. Some reports depend on the demographic data and will not generate if this information is missing.

To find your Site DI (SDI) go to Forms Manager > Settings > View My Account URL.

To enter a dummy description or text wherever necessary, lorem ipsum scriptis used in many places. It can be generated by many online tools; as an example, the following link directs to a lorem ipsum generator that can generate a desired length text:

http://www.procato.com/lipsum/

When creating a new request, first search the organization > open it and create the request. This way, necessary links will be automatically created behind the scene.

For an already published requirement, if we update the related Online Requirement Form in Forms Manager, we need to delete and re-publish the requirement that uses that form. For example, if the name of the form is modified, the published requirement needs to be deleted and republished to capture any of the changes made to the form

.If you do not wish to record an activity (that is, leave an audit trail) leave the ‘Create Activity’ checkbox unchecked. Testing activities should not be recorded unless activities are being tested.

To save a view, after running a search, click the grey open folder icon beside the view dropdown below search results and do modifications > click the Apply button > a save icon appears beside the view dropdown > click it > give the view a name and save it (you don’t have to add a search to it -in fact it’s not recommended in most cases).

Clean up

Always cleanup after testing. Either delete the instances created, reverse the changes, or decline the request to avoid any effect on real data.


  • No labels