Hi
Narender,
> Can
we test pega-PRPC, (Business process management framework) application
using test complete. [...]
Assuming that your tested application is Windows-based, the answer is "yes, you can".
How this can be done, is another question the answer on which depends on what are your test goals.
The case here is that the 'framework' word is too overloaded nowadays and personally for me it means now practically nothing without further clarification whether we are talking about set of library/reusable functions, approaches, that must be used during development/testing, workflow that must be implemented in the application or something else. Depending on the answer, the use if this or that 'framework' may influence the testing or be absolutely irrelevant.
TestComplete is a test automation tool that can be used for two types of testing: a) the testing that emulates user's work with the application via GUI provided by the latter, and b) application's testing without explicit interaction with its GUI.
In the first case, the major thing that will significantly simplify successful and reliable test automation is the use of GUI controls that can be recognized and operated by TestComplete. Note, that even if controls are not supported by TestComplete, the chances are still high that you will be able to test your application. It might just be less stable and not that easy to be implemented (e.g. instead of direct access to the control it might be required to select it via some keyboard shortcut and copy/paste the data via clipboard instead of accessing them directly).
In the second case, the major requirement is that TestComplete can call tested application's methods and access produced results. The used GUI controls are irrelevant for this type of testing.
Considering the above, I hope that it is evident, that if the 'framework' is a set of GUI controls and you need to automate tests that emulate end-user's work with the application, than it is essential that TestComplete can operate the used GUI controls.
If the 'framework' is a set of rules that developers must follow during the development, than you should check whether these rules simplify or not tests creation for you and influence the used set of rules to make things easier for you.
If the 'framework' is a set of business/security/workflow/etc. requirements, than they are practically irrelevant for you from the point of automation and will require inclusion of corresponding verifications where it is needed.
