Testing as a Service

Some way to test customer customisations, including:

• custom code that uses public APIs

• custom screens with business logic

• baseline test cases that are particular to how the customer uses the product, e.g.

  • edge testing OPC connectivity with 3rd party OPC components

  • unique topologies (FEP, Split RT, etc)

• stretch

  • 3rd party software, like anti-virus

Additional considerations for integrators with add-on or layered applications

• basic sanity checks (no use of un-authorised APIs, no changes outside of the allowed silos, etc.)

• apply realtime schema changes and perform basic smoke test

• compile solutions and execute test cases

• run selected baseline integration smoke tests (replication, failover, start/stop) to ensure no unexpected consequences

Should be cloud-hosted on AVEVA Connect

Shouuld eventually be incorporated into Development Studio and MoC, to get the changes signed and sent to on-prem in a secure and controlled mannor.

Should eventually be incorporated into on-prem lifecycle management.

This would shorten the integration time needed for upgrades, and move towards fewer upgrades, and more frequent updates.

Would shorten update cycles.

Would help customers stay current on the latest version to keep apace with security and other regulations.

Would help regulators be more prepared on launch day.