Vendors typically provide the FS. Your job is to document the —the exact settings, parameters, and rules you will apply to the software.

You do not need to retest the vendor’s core code. Rely on the vendor’s own or test reports. Your focus is testing your specific configuration .

| Pitfall | Why it’s risky | Solution | | :--- | :--- | :--- | | | More configuration = more points of failure. | Apply the "Keep it as simple as possible" rule. | | Treating Cat 4 like Cat 3 | Skipping OQ for configurable features leads to undetected errors. | Test every configured rule/workflow. | | Testing vendor features you don’t use | Wastes time and resources. | In the URS and test plans, scope only your configured usage. | | Poor change management | Changing one config setting can break another. | Revalidate (or assess impact of) any configuration change. |