Hi @anusha cherukuri,

It sounds like you're encountering an issue where the additional clipboard data defined in your Test Suite (TS_1) is not being applied to the test cases within it, causing them to fail due to a "page does not exist" error. Let’s break this down and address the problem.

In Pega, when you define additional clipboard data in a Test Suite (on the "Setup & Cleanup" tab under "Before rule execution"), this data is intended to set up the context for all test cases within that suite. Each test case should, in theory, inherit this context and execute within it. However, if the test cases are failing because the expected clipboard page isn’t present, it suggests that the Test Suite’s setup might not be functioning as expected. Here’s why this might be happening and how to resolve it:

Possible Causes

1. Setup Not Executing Properly: The "Additional clipboard data" defined in the Test Suite (e.g., loading an object) might not be executing before the test cases run. This could be due to a misconfiguration in the setup steps.
2. Test Case Independence: Pega Unit test cases are designed to be independent and portable. If the test cases rely on clipboard data but don’t explicitly define or inherit it, they might not see the Test Suite’s context unless it’s correctly propagated.
3. Thread Isolation: Each test case in a Test Suite runs in its own thread. If the clipboard data isn’t being correctly initialized or copied to each thread, the test cases won’t have access to it.
4. Cleanup Interference: If there’s a cleanup step in the Test Suite or test cases that removes the clipboard page prematurely, it could explain the "page does not exist" error.