@VijayR17555451 Pega does not officially certify or support TOSCA, but many clients use it successfully as a third party tool. For Pega 24.2.2 and Constellation, Pega’s guidance is to favor built in testing first, like Pega Unit for rules, Scenario Tests for low code UI flows, and API level testing through DX APIs for end to end paths. If you still choose TOSCA, target stable selectors only, use the Constellation test IDs instead of XPath or CSS classes, avoid fragile DOM positions, and sync on Pega’s busy or network idle states to reduce flakiness. Keep most business assertions at the API or data layer and reserve UI checks for what must be visually verified. For ZATCA use mocked services to validate e invoice signing, QR generation, and submission flows, then run limited UI smoke tests on top. Do not expect Pega Support to troubleshoot TOSCA scripts, but they will address product defects you can reproduce without TOSCA. For robotics or desktop automation, prefer Pega Robot Studio. In summary, use Pega native tests and DX APIs for coverage and treat TOSCA as an optional UI layer with stable test IDs and minimal assertions.