It is appreciated that the terminology used to describe each type of test may differ from one company to another but the more common titles have been used.

a. Skim Test

  • Testing only key functions in areas of change. Only used when very small changes are proposed.

b. Unit Test

  • Testing changes only within the area of functionality affected by the change.

c. Interface / bridge test

  • Testing changes that affect areas of functionality (interpretation rules are consistent either side of the interface, interface control, and bridging software).

d. Functional regression test

  • Testing non-related areas of functionality to ensure they remain unaffected.

e. Business integration test

  • Testing all related areas of functionality including user documentation produced by the system, screen displays, and management information.

f. Data conversion test

  • Test comparison of standing data before and after delivery. Negative testing would be used if no conversion of data is anticipated.

g. Baseline test

  • Tests run against the production system prior to change implementation. Data is stored electronically and compared to a re-run of the test after implementation. This is normally used for retrospective changes.

As a Company standard, tests b, d, and e must be used for all change deliveries.