Life science companies would love to get rid of inefficient and costly validation processes, may it be electronic manual tests or even worst, paper based manual tests. The only answer to this problem is "test automation". But the challenge is that if you use test automation for validation, then you need to keep your test automation infrastructure and processes also in a validated state. But the test automation world is too complex for validation and even more difficult to keep it in a validated state given the nature of frequent changes, upgrades and a myriad of tools used.
A typical test automation environment would have these candidates that need to be in a qualified state:
Framework and Plugins
Test Management Processes
You need a large team of engineers to build and execute IQOQ protocols in order to validate each of these components. At xLM, we have unearthed Model Based Testing (MBT) suite which packages all these components in one framework. This approach results in the MBT Suite as the only candidate that requires validation. Once this framework is validated, we use its inbuilt Development Factory, Code Repository, Integration APIs and Reporting Toolset for our solution building.
Our Test Automation features include:
GUI models that represent the test processes for AUTs/SUTs.
Compact System: Less components to carry throughout the life cycle.
Object oriented architecture that can accommodate frequent changes/upgrades in SUTs with minimal efforts.
One test can be built to automate heterogeneous system components like web interfaces, java apps, interaction with local machines and much more.
Instantaneous compliance reports with test action details, time stamps, requirement coverage, result metrics and screenshots.
Rich integration options using APIs like REST.
Moreover, our solution suite itself is in the cloud. So it knows the DNA of cloud systems it is validating!