wrench

Robotic Patch Validation (RPV)


Patch Testing is required for every industry – Doing it manually and correctly can be labor intensive and expensive.

“Patches” differ from “upgrades” in that they don’t generally add new functionality or change a business process. Rather, they provide fixes to bugs or add support for changes in technology infrastructure.

Most organizations endure complex desktop configurations (mainly due to MS-Office extensions) that increase the potential risk for problems when change is introduced. Unfortunately, there can be unintended consequences to many “patches” that can have a significant impact to an organization’s efficiency, ability to perform their critical functions, and/or billable revenue.

 

Testing is key to mitigating these risks.

The organization assures a higher level of quality by identifying and correcting critical issues before deploying changes to their end-users. A focus area of patch testing is the integrations between applications – a recurring pain point and problem area. Patch tests need to be executed at least monthly to keep up with common scheduled security fixes, in addition to execution cycles of the patch tests triggered by upgrades and zero-day type releases, resulting in 15 tests annually.

 

Olenick’s Robotic Patch Validation (RPV)

Olenick has created a solution that can execute automated tests against a client’s desktop environment. The results report any functional breakages, as well as performance metrics for each activity exercised.

 

RPV Benefits:

  • Requires minimal footprint in your environment
  • Provides a robust menu of pre-built automated application scripts
  • Typically executed monthly with ad-hoc executions per request
  • Customized for organization specific extensions

 

RPV leverages Olenick’s expertise in automation scripting and innovative tooling and removes the intensive effort and high cost of automated testing.

 

Related Content