AgilePoint is a background process for the main ASP.NET application so customers
usually perform regression and performance testing on the main application
rather than doing a standalone test for AgilePoint. There are a lot of
performance testing tools available like TestPartner, TestComplete, QALoad
etc. for ASP.NET applications. However if they feel that on a particular
screen, some of the AgilePoint related components are not performing properly,
there is a way to troubleshoot using the performance tracing utility on an
AgilePoint Server. This helps to know if the problem is due to AgilePoint code.
For more information, see
Performance Tracing Utility.
In general testing workflows can be done at two levels.
- Apply 'validation' for the process model and unit test each reusable component such as your custom AgileParts.
- Test environments typically include instances of process servers, database servers, email servers, SharePoint servers, etc. Configurations that are different in test environments vs. production environments such as database connection strings, Web Service URL's, etc. can all be configured as a set of environment-specific attributes in AgilePoint Server rather than being hard-coded in process definitions. A test server can define one set of values for these shared attributes while a production server can define another. Process templates simply need to be created and configured to use these named shared attributes rather than hard-coded values. With this type of abstraction, processes can be deployed and tested in a test environment and then deployed to a production environment without changing the process definition. Only the values of the shared process attributes will change.
