This document explains the tools and methods for testing and debugging APS applications on the platform, which is the last phase of the integration process.
The tools and recommended steps in this section are for application developers who have completed the previous phases of the integration process and now have the following knowledge and skills.
Since the APS JS SDK is based on the Dojo framework, you should also review the debugging methods contained in the Dojo Debugging Tutorial. Also, the APS 2 Knowledge Base contains many examples on how to identify and fix bugs in APS applications.
When testing the application user interface (UI), you will use various types of user panels:
You will use this panel to deploy and provision the application services. Application specific operations include configuring Application Service Reference resource types.
Testing applications in UX1 is usually one of the most important parts of the project. First, you should create a test customer and customer administrator. Next, log in as the customer administrator from the PCP, or log in to UX1 using the user credentials you have created.
To simplify the login process in your development environment, allow your browser to remember the password or assign a simple password for your test user. For the latter case, change the password quality level on the system:
Do NOT allow simple passwords on a production system.
Log in to UX1 using the user credentials you have created.
The benefit of this way is that you get access directly to UX1 in one step.
If you logged in to PCP as the provider, you can open UX1 on behalf of a customer without entering the customer administrator’s credentials from different places in PCP. This is beneficial since in a production environment, you do not know a customer administrator’s credentials. Also, this enables you to simultaneously access PCP as the provider and UX1 as the customer administrator.
To log in as the customer administrator use one of the following ways: