Technical and usability testing

In conjunction with clinical testing, we will conduct a series of technical and usability tests, including:

  • Interface testing: ensures that events, data mapping, translations and filtering rules triggered by business workflows are implemented correctly.
  • Data legacy testing: data legacy access testing involves verifying that legacy data migrated from source systems into CareConnect is viewable via the portlet view in the CST Cerner mPage. Patient migration involves the validation of¬†patients migrated from the EMPI into CST Cerner. Patient migration testing incorporates: EMPI active integration and CST Cerner Integration with the broker. Data legacy is owned and managed by the CST project.
  • Operability testing: validates the operations of the system in the production-ready environment. This includes failover/recovery and performance, including volume, stress, load, network bandwidth usage and latency checks. Performance testing determines how fast various aspects of the system perform under a particular workload. It can also serve to validate and verify other quality attributes of the system, such as scalability, reliability and resource usage.
  • Device testing: checks devices for faulty or missing features, insufficient performance, side effects to other apps on the same device and other product quality characteristics.
  • Usability testing: evaluates the designed workflow to mitigate any usability risks. Representative users from specific functional areas perform certain tasks in an effort to measure usability.

Types of testing

Throughout the different test levels, we will perform the following testing types:

  • Regression testing: checks that existing features and functionality are still working as expected after changes are made in the Cerner application.
  • Sanity (smoke) testing: checks whether a new software version, build iteration or domain is performing well enough to be subject to major testing. If the sanity test results are not satisfactory and the system is not stable, the build iteration is assigned back to the build team.
  • Functional testing: determines whether the software physically works the way it was intended to and all required menu options are present. It also ensures that the software conforms to the industry standards relevant to that environment.
  • Positive testing: checks whether a component or system works as expected, verifies changes or additions to the application and ensures that they operate as outlined in the business requirements and design specifications.
  • Negative testing: confirms that reject or error situations occur as outlined in the business requirements when an invalid value or key is used.
  • Cerner upgrade testing: conducted after a full Cerner code upgrade to verify that the upgrade did not affect the already-completed clinical information system. It also validates newly delivered functionalities.