Navigation steps are easy but how automation does validation in BPTs through scripts/components I have seen people doing in many different ways. Wanted to get group's feedback on what is the best way to do validations (actual results match expected results).
Introducing generic validation steps (components) for each verification type like Verify_Image_Appeared, Verify_Records_Displayed, Verify_Heading_Displayed, Verify_Text_As, etc. with a generic text parameter works well with SMEs since they simply insert such validation step/component when constructing BPTs but how automation folks handle such validations is where things get complicated since they might be handling such validations on case-by-case basis which kills the purpose of having reusable components.
Ideally smart components should be there for validations accepting actual and expected values as input parameters but there are so many types/scenarios when it comes to validations. Wanted to get forum's feedback how you guys do validations.