Baseline Validation

In Seal, automated, baseline validation tests are essential checks are performed daily to ensure the functionality, stability, and reliability of the Seal Platform. These automated tests ensure that it consistently operates as intended and maintains validated status across its life cycle, and must be passed anytime there are any changes made.

Some of Seal's automated tests are listed below. Note that this is not a comprehensive list - for a full list of all tests, please navigate to the Validation tab on your Seal platform.

Document Editor
  • Can edit the document content of records in a multi record step

  • Entity is able to auto-saves

  • Toolbar is rendered when editor text is selected

  • Toolbar not rendered when step is not editable and when document is not editable

Search page
  • Home page navigates to the search page

  • Can searching for entities by various fields

Procedure
  • Can create a new procedure with new and existing steps, and publish it

  • Can add fields to a step

  • Can create a new run from a procedure, and mark it as done

Runs
  • The next step in a run is active when a previous step is marked as done

  • Can mark a run as done if all stages are complete, and vice versa

  • Can mark a stage that is in revision as done, and sends the following stage to in revision if it has been done before

  • Can revise a stage and sends any active stages back to waiting

What do I need to do on my end?

Baseline validation is designed to ensure that the software platform is functioning as intended every day, without requiring any effort or input from the customer. This process is fully automated and handled entirely in Seal.

There is no need for manual intervention or additional validation testing from your team - our internal systems monitor and validate functionality to ensure core functions and configurations are operational and validated.

This approach to baseline validation is part of our commitment to making your validation experience in Seal seamless and reliable without compromising on system integrity.

Last updated