Compatibility Test Lists - Concepts

From OPC Labs Knowledge Base
Jump to navigation Jump to search


The Compatibility Test Lists document the test performed with the product with the aim to assure its compatibility widest range of systems it depends on or interoperates with. The documents are updated from time to time, as new tests are being performed.

The documents are grouped by the classes of systems that this product depends on or interoperates with, such as "Platform hardware" or "Operating systems". Each class has a standalone chapter.

The entries in each group are sorted by the columns from left to right, i.e. first by "Other system model", then by "Other system version", and then by "Test date.

Field descriptions

Other system model

"Other system" is the system we are testing the compatibility of this product with. It can be hardware, software, or a combination.

Other system version

This field contains additional details about the other system, typically its versioning information, if available.

Test date

Describes when the test was performed. It can be a specific date, date range, or approximate date such as a month in a year.

Performed by

This field determines the entity (person or organization) that has performed the test.

This product version

This field contains versioning information about this (our) product, typically including the software build and revision numbers, too.

If a test that was otherwise identical in other parameters has been performed with a newer version of this product, and the outcome was the same or better, the old entry in the compatibility test list may be removed for brevity. This is done so because the main purpose of the compatibility test list is to assess the compatibility of the latest available version of this product.

On the other hand, entries for tests performed with earlier versions of this product that were not repeated later are always retained. It can be assumed that later versions of this product continue to operate with at least the same outcome as the version that has been tested.

Test type

  • Alpha test.
  • Basic test.
  • Compliance test.
  • Developer test.
  • Field test.
  • Interoperability workshop.
  • Targeted test.

Test outcome

  • Failed. There is always a Note describing the details.
  • Inconclusive. There is always a Note describing the details.
  • Passed.
  • Warning. There is always a Note describing the details.


This field contains any relevant notes, especially to the test environment, or outcome of the test.